A sandbox data-science OU suddenly generated a large GPU EC2 bill after a notebook instance type was misconfigured. The FinOps team wants faster detection next time. Which improvement best strengthens cost management alerting?
Select an answer to reveal the explanation.
Short Explanation
A mis-sized GPU notebook can torch a sandbox budget overnight. Cost Anomaly Detection plus Budgets is how you get the text message while it’s still a fire drill, not a council scandal. Annual hearings are too late.
Full Explanation
AWS Cost Anomaly Detection and AWS Budgets provide near-term alerting on unusual spend, including sudden GPU costs in sandbox OUs. That improves cost management and reporting compared with waiting for annual reviews. Disabling all sandbox EC2 or relocating GPUs into production to dodge monitors are governance failures, not alerting strategies.