Question 170
A finance analyst needs monthly Azure spending grouped by Project tags across eligible resources. How should the team prepare the tagging data for Cost Management?
Explanation
Correct Answer
Azure Cost Management can use resource tag metadata for supported cost allocation and grouping. To obtain meaningful project totals, administrators should standardize the Project tag key, define consistent allowed values, and apply those values to cost-accruing resources. They must also account for services that do not emit all tag dimensions in billing data and use supported cost inheritance features where appropriate. Grouping by a reliable Project tag is more meaningful than inferring project ownership from arbitrary VM display names.
Incorrect Answers
VM names do not consistently represent project ownership across different Azure resource families or shared workloads. Cost reports may also include disks, networking, and services without matching naming conventions. Standardized Project tags and supported Cost Management grouping provide a more systematic metadata-based cost classification.
Azure RBAC Owner grants broad infrastructure and access management permissions, not a standardized project cost dimension. It would create unnecessary privilege while leaving inconsistent tags unresolved. Finance needs permitted cost-report access and reliable resource metadata, which should be managed separately from subscription ownership.
Management locks protect control-plane resource operations and do not provide a Project dimension for cost allocation. Removing tags would make the desired grouping harder, not easier. Standardize and retain relevant resource tags, then use supported Cost Management reporting views and filters.