A rightsizing workshop finds idle extra-large EC2 instances that monitoring shows should be medium. What action matches rightsizing best?
Select an answer to reveal the explanation.
Short Explanation
Finding idle XLs that should be mediums is like noticing you rented a banquet hall for a desk for one. Rightsizing fixes the size to the need — it is not “buy Reserved first and think later.” Look, then fit, then commit if it still makes sense.
Full Explanation
Resize or replace oversized idle instances to a size that fits measured need rather than buying Reserved capacity blindly without review—that is the rightsizing action when a workshop finds idle extra-large EC2 instances that should be medium. Commitments come after shape matches reality, not before.
Purchasing the largest Reserved Instances without checking utilization locks in waste. Doubling every instance size to hide idle capacity worsens spend. Disabling monitoring so idle XL instances cannot be flagged again destroys FinOps feedback.
Exam caveat: Rightsizing precedes commitment purchases; RIs/Savings Plans amplify good sizing, they do not fix bad sizing. Operational check: downsize a non-production idle XL to medium using monitoring evidence, validate performance, then evaluate commitments only on the rightsized footprint.
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.