Without consistent resource tags, a city’s parks and police AWS spend is mixed on one bill and hard to split. What practice restores departmental visibility?
Select an answer to reveal the explanation.
Short Explanation
If parks and police share a bill with no labels, nobody knows who spent what. Tag resources by department and activate those tags for cost allocation.
Full Explanation
Without consistent resource tags, a city's parks and police AWS spend mixes on one bill and becomes hard to split. Applying and activating cost allocation tags restores departmental visibility so each department's resources can be filtered in cost reports. Tags are the metadata backbone of municipal showback: without them, even perfect Organizations structure cannot explain which agency drove which line items inside shared accounts.
Deleting all IAM roles does not make billing separate by agency and would break access control. Turning off multi-factor authentication does not clarify cost reports and harms security. Using Amazon Polly to read the invoice aloud does not allocate spend by department. Absurd operational and security regressions are not FinOps solutions.
Exam caveat: Apply tags + activate for cost allocation. Governance should treat Department (or CostCenter) as mandatory. Pair with SCPs/automation to reduce untagged launches.
Operational check: mandate Department tags on launch, activate keys in billing, build Cost Explorer reports for parks versus police, chase untagged spend weekly, and present separated charts to budget hearings so agencies cannot claim the shared cloud bill is inexplicable.