An alerts-only budget and a workload left running
A fictional team sets an alerts-only monthly cloud budget of one thousand currency units. The setting sends notifications but has no automated enforcement action attached. A test workload is then left running after a demonstration. In the supplied simplified invoice it consumes nine hundred in compute charges, two hundred in storage and one hundred in transfer charges, all within the same monthly budget scope. The email notification reaches a shared mailbox that nobody checks during the weekend. The project owner believed the budget would necessarily stop the workload before the total exceeded one thousand. The team must calculate the supplied total, explain the control gap and choose a response that accounts for service impact. No live vendor prices, free-tier entitlement or guarantee about notification timing is implied.
1. Calculate the supplied total and explain why the budget did not necessarily stop it.
Read the worked answer
Total cost is 900 +200 +100 =1,200, exceeding the budget by 200. The scenario explicitly uses alerts-only behavior, so notification alone is not an enforced spending cap or a command to stop resources.
2. Identify improvements without blindly stopping every service.
Read the worked answer
Assign an accountable notification route, use suitable resource limits and lifecycle cleanup, review remaining storage/transfer charges, and evaluate any authorized enforcement automation against service-critical dependencies. Verify the actual product’s available controls rather than assuming every budget type behaves the same.