Home › AWS SysOps Associate › cloudcomputing › sysopscostperf › An RDS MySQL primary is read-heavy and CPU-bound…
An RDS MySQL primary is read-heavy and CPU-bound. Which is the SIMPLEST scaling response?
ADisable IAM auth on the database
BAdd RDS read replicas and direct read-only queries to them
CMigrate the entire database to Amazon Glacier
DSwitch the application to flat-file storage on S3
Answer & Solution
Correct answer: B. Add RDS read replicas and direct read-only queries to them
Read replicas offload reads — simplest, no schema changes. The other options destroy the workload or address unrelated concerns.
Related questions
A Lambda function processes S3 events at high frequency. Cost is dominated by execution tiWhich AWS Auto Scaling feature lets a single scaling plan coordinate scaling across EC2, EAn EBS-backed EC2 instance's IOPS is bottlenecked. Which is the appropriate scaling responWhich combination MAXIMISES savings on a stable 24×7 workload running 200 EC2 instances ovWhich combination minimises egress cost when streaming static video to global users?Which AWS service lets engineers receive billing alerts when an account's monthly spend crAn RDS database is over-provisioned for typical workloads but occasionally peaks. Which coWhich AWS recommendation engine flags idle / underutilised EC2 / EBS / RDS resources so ad