A municipal cloud office already deployed production resources and now needs ongoing visibility and control of Azure spend. Why is the pricing calculator alone insufficient?
Select an answer to reveal the explanation.
Short Explanation
The estimate got you to launch; now you need the dashboard for the road trip. Cost Management watches actual spend, budgets, and trends after resources are live. The calculator alone cannot manage day-to-day costs.
Full Explanation
After production resources are deployed, municipal cloud offices need ongoing visibility and control of actual Azure spend. The pricing calculator alone is insufficient because it estimates configurations; it does not replace Cost Management budgets, cost analysis, alerts, and related controls that operate against real meters. Estimates got the project to launch; day-to-day fiscal governance depends on Cost Management tooling for what is running now and how spend trends against plan. Fundamentals scenarios that say "already deployed" and "ongoing" point to Cost Management rather than calculator-only operations.
The pricing calculator does not automatically optimize running VMs each night. Deployed resources do appear in Microsoft billing and Cost Management—they are not invisible after go-live. Azure Arc is valuable for hybrid management but is not the primary suite for showing and controlling native Azure subscription costs after launch.
Exam caveat: keep using the calculator for future what-if changes, but do not skip Cost Management for production operations—both tools have roles across the lifecycle. Operational check: enable cost analysis reviews on a cadence, set budgets and alerts on production scopes, and compare monthly actuals to the original calculator estimate so configuration drift and unused capacity surface early.