AZ-900 Practice Question 18: Tag Inheritance
Microsoft Azure Fundamentals (AZ-900) · Test 2 · question 8 of 10
An administrator applies the tag CostCenter = Finance to a resource group holding ten virtual machines, then filters Microsoft Cost Management by that tag and sees almost no spend. The virtual machines are definitely running and generating charges. What is the most likely reason?
Show answer and explanation
Answer:
This is the single most commonly misremembered fact about tags: resources don't inherit the tags you apply to a resource group or a subscription. The tag sits on the resource group object alone, so a cost filter on CostCenter = Finance matches nothing the VMs emit. The supported fix is to tag the resources themselves, and to keep them tagged by assigning one of the built-in tag policy definitions that appends or modifies the tag on resources in scope.
Option A gets the rule backwards: tag *names* are case-insensitive for operations, while tag *values* are case-sensitive, and in any case the administrator applied and filtered on the same string. Option B is simply false; tags are designed for exactly this, and the documentation describes using them to group billing data by cost center or environment. Option D is false too; resource tags support all cost-accruing services, and virtual machines are the canonical example in the docs.
Reference: Use tags to organize your Azure resources and management hierarchy