An Azure administrator deploys a set of virtual machines into a resource group named dev-rg. To track expenditures, the administrator applies a tag named Environment: Dev to dev-rg. In Azure Cost Management, they configure a budget alert to trigger when spending associated with the Environment: Dev tag exceeds USD. However, the budget alert fails to trigger even though the actual cost of the virtual machines has exceeded USD. Why did the budget alert fail to trigger?
- AAzure Cost Management budgets only track Capital Expenditure (CapEx) costs, whereas virtual machine usage is billed as Operational Expenditure (OpEx).
- Resource tags applied to a resource group are not inherited by the resources inside that group, so the virtual machines lack the tag required to trigger the budget alert.Answer
- CThe virtual machines automatically inherited the tag, but a ReadOnly lock on the resource group prevented Azure Cost Management from accessing the billing telemetry.
- DResources automatically inherit tags from their resource group, but the budget alert failed to trigger because tag inheritance must be explicitly enabled in the subscription's billing profile.
Answer
Resource tags applied to a resource group are not inherited by the resources inside that group, so the virtual machines lack the tag required to trigger the budget alert.
The correct answer is the option stating that resource tags applied to a resource group are not inherited by the resources within it. In Azure, tags applied to a resource group do not automatically propagate or inherit down to the individual resources inside that group. Because the budget alert is filtered specifically by the tag, the costs incurred by the untagged virtual machines are not associated with the tag, preventing the budget threshold from being reached.
Step-by-Step Solution
Key Concept
Azure resource tags do not inherit from the resource group to individual resources inside it.
Estimated Time:1m 0s