Weeks of Enhanced Monitoring and Performance Insights show a municipal permitting RDS instance consistently under 20% CPU and memory with no storage throughput saturation. Which continuous-improvement action best rightsizes based on that evidence?
Select an answer to reveal the explanation.
Short Explanation
If permitting’s RDS has been coasting under 20% for weeks, it’s wearing a jacket two sizes too big. Downsize with evidence, then watch the meters. Extra Multi-AZ Regions and random replicas aren’t rightsizing.
Full Explanation
Rightsizing uses utilization telemetry—CPU, memory, and I/O—to select a smaller RDS instance class that still satisfies headroom and SLA needs. Multi-AZ everywhere, speculative cross-Region replicas, or abandoning RDS for self-managed EC2 do not follow utilization-driven rightsizing for an already underloaded municipal database.