A public-safety department has a fixed monthly AWS compute allotment and needs early warning before overruns. Which service configuration supports that guardrail?
Select an answer to reveal the explanation.
Short Explanation
Budgets is the smoke alarm for the department's AWS wallet—set the allotment, get pinged before the month goes sideways, and stop discovering overruns at council time.
Full Explanation
AWS Budgets alerts (optionally with actions) when forecasted or actual compute spend exceeds the department threshold is the correct guardrail for a public-safety department with a fixed monthly AWS compute allotment that needs early warning before overruns. Budgets turns an allotment into an operational smoke alarm before council discovers the miss. Amazon Macie auto-remediation of EC2 instance types fails because Macie focuses on sensitive data discovery in data stores, not EC2 rightsizing or budget thresholds. AWS Shield Standard monthly invoice forgiveness fails conceptually: Shield Standard is DDoS protection included with AWS, not a billing-forgiveness or departmental allotment control. Amazon Inspector to block Cost Explorer fails because Inspector finds vulnerabilities; it does not implement spend guardrails and blocking Cost Explorer harms financial visibility. Exam caveat: use AWS Budgets for allotment alerts/actions; do not confuse Macie, Shield, or Inspector with cost governance. Operational check: create a Budgets threshold matching the public-safety compute allotment; alert on actual and forecast; optionally attach actions; route notifications to finance and ops; and review mid-month so corrective rightsizing happens before month-end overrun.