Practice cloud cost attribution vocabulary: tagging strategies, per-team cost allocation, untagged resource costs, finance reporting requirements, and cost governance.
0 / 5 completed
1 / 5
'___ strategy for cost allocation' — which noun describes labeling cloud resources with owner metadata?
A 'tagging strategy' defines how cloud resources are labeled with metadata (team, environment, service) so costs can be attributed to the right owner in billing dashboards and reports.
2 / 5
'The engineering team ___ 40% of cloud spend.' Which verb describes ownership of costs?
'Owns' is the standard FinOps verb for cost attribution: 'the team owns X% of cloud spend.' It implies accountability — the team is responsible for understanding and optimizing their share.
3 / 5
'___ resources cost $12K/month.' Which adjective describes resources without cost metadata?
'Untagged resources' are cloud resources missing required cost allocation tags. They create a 'dark spend' problem — the finance team can't attribute the $12K/month to any team or project.
4 / 5
'The finance team requires per-___ cost reporting.' Which noun describes the granularity?
'Per-team cost reporting' is a common finance requirement in larger engineering organizations. It enables chargebacks, showbacks, and budget accountability at the team level.
5 / 5
What is 'cost attribution governance' in cloud environments?
Cost attribution governance is the set of policies (required tags, enforcement via SCPs or Azure Policies) and processes (regular audits, tagging compliance reports) that ensure cloud spend is accurately attributed.