The budget office asks which AWS Well-Architected pillar specifically drives rightsizing workloads and eliminating unused resources. Which pillar should finance cite?
Select an answer to reveal the explanation.
Short Explanation
Rightsizing is like canceling the unused gym membership and swapping the oversized truck for one that fits the job. Cost Optimization is the pillar that pushes teams to remove unused spend and match capacity to need. Reliability keeps things available, Operational Excellence improves how you run them, and Security protects them — none of those is the rightsizing-and-waste pillar.
Full Explanation
Cost Optimization is the Well-Architected pillar that specifically drives rightsizing workloads and eliminating unused resources—exactly what a municipal budget office should cite. Finance can point teams to continual cost awareness, measuring efficiency, and retiring idle capacity so taxpayer spend tracks actual demand.
Reliability focuses on recovery and availability, not rightsizing as its primary mandate. Operational Excellence focuses on runbooks and improvement of operations. Security focuses on protecting assets and data. Citing those pillars for a rightsizing/unused-resource agenda mislabels the concern.
Exam caveat: Rightsizing and unused resources are classic Cost Optimization cues. Operational check: enable Cost Explorer and budgets, produce a monthly rightsizing report for always-on municipal fleets, stop or downsize idle non-production resources, and show finance the delta.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.