Home › AWS SysOps Associate › cloudcomputing › sysopscostperf › An RDS database is over-provisioned for typical …
An RDS database is over-provisioned for typical workloads but occasionally peaks. Which combination MINIMISES cost while keeping headroom?
AReplace RDS with manual EC2 + MySQL deployments
BDisable monitoring to save cost
CPermanently provision the largest instance and never change it
DRight-size to a smaller instance class and enable RDS auto-scaling for storage; consider Aurora Serverless for spiky workloads
Answer & Solution
Correct answer: D. Right-size to a smaller instance class and enable RDS auto-scaling for storage; consider Aurora Serverless for spiky workloads
Right-sizing + auto-scaling storage + Aurora Serverless for spiky workloads is the standard cost-perf optimisation. Permanent over-provisioning, manual EC2 + MySQL, or disabling monitoring all add cost or risk.
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 ovAn RDS MySQL primary is read-heavy and CPU-bound. Which is the SIMPLEST scaling response?Which 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 crWhich AWS recommendation engine flags idle / underutilised EC2 / EBS / RDS resources so ad