A SysOps administrator notices that an Amazon RDS DB instance is running at 10% CPU utilization consistently. The instance has 8 vCPUs and 32 GB RAM. The application's performance is adequate. Which action will reduce costs without affecting performance?
Selecting a smaller instance type reduces the hourly compute cost. Since current utilization is low, a smaller instance will still provide adequate performance.
Why this answer
The DB instance is over-provisioned for the current workload, as evidenced by the consistently low CPU utilization (10%) and adequate application performance. By changing to a smaller instance type, you reduce compute costs directly while maintaining sufficient capacity for the workload. This is the most straightforward cost optimization action when performance requirements are already met.
Exam trap
The trap here is that candidates may confuse cost optimization with performance improvement or high availability, leading them to select Multi-AZ or IOPS changes, which increase costs rather than reduce them.
How to eliminate wrong answers
Option A is wrong because enabling Multi-AZ deployment increases costs by provisioning a standby replica in a different Availability Zone and does not reduce costs; it improves availability and fault tolerance. Option C is wrong because changing storage type from gp2 to gp3 may reduce storage costs but does not address the over-provisioned compute resources (vCPUs and RAM) that are the primary cost driver here. Option D is wrong because increasing provisioned IOPS increases costs and is unnecessary when performance is already adequate and CPU utilization is low.