Home › AWS Solutions Architect Associate › cloudcomputing › highperformingarchitectures › An application's RDS for MySQL primary is CPU-bo…
An application's RDS for MySQL primary is CPU-bound under read traffic. Without changing the schema, which is the FASTEST scaling step?
AIncrease the EBS volume size only, leaving instance type unchanged
BSwitch the app to S3 Glacier Deep Archive for reads
CAdd RDS read replicas and route read-only queries to them
DMigrate the entire database to Cloud SQL on GCP
Answer & Solution
Correct answer: C. Add RDS read replicas and route read-only queries to them
Read replicas offload read traffic from the primary — usually a one-click operation in RDS. Migrating clouds, growing the disk only, or storing data in Glacier don't address read CPU.
Related questions
Which AWS service provides a managed, query-on-demand interface to analyse data already siWhich combination most efficiently runs spiky containerised workloads at the lowest operatWhich architecture pattern handles a sudden 10× write burst from millions of IoT devices wA workload needs millisecond reads at any scale on a key-value access pattern with predictAn OLTP workload has a relational schema, needs single-digit-ms latency at the 99th percenWhich AWS service routes user traffic at the IP layer with anycast addressing and Region fWhich combination accelerates static content delivery to global users in front of an origiWhich compute option scales to zero between requests and bills per invocation millisecond,