Question

Difficulty: EasyAzure Cost Management, Billing, and Resource Tags

A development team creates an Azure resource group and applies a tag named `Department` with a value of `Marketing` directly to the resource group. A developer then deploys a web app inside this resource group. What is the status of the `Department` tag on the newly deployed web app?

  1. The web app does not have the tag because Azure resources do not inherit tags applied to their resource group.Answer
  2. B
    The web app automatically inherits the tag from the resource group.
  3. C
    The web app inherits the tag and automatically classifies its running costs as Capital Expenditure (CapEx).
  4. D
    The web app does not have the tag initially, but any new Azure Policy created later will retroactively apply the tag to the web app.

Answer

The web app does not have the tag because Azure resources do not inherit tags applied to their resource group.
The correct answer states that the web app does not have the tag because Azure resources do not inherit tags applied to their resource group. In Azure, tag inheritance is not automatic. While you can apply tags at the subscription or resource group level, these tags do not cascade down to the resources within them.

Step-by-Step Solution

1
Analyze the scope of the applied tag.
The tag is applied to the resource group, not the web app.
We need to determine if tag inheritance applies down to individual resources.
2
Determine Azure tag inheritance rules.
Azure resources do not automatically inherit tags from their parent resource groups or subscriptions.
This is a fundamental behavior of Azure Resource Manager governance.

Key Concept

Azure Resource Tag Inheritance
Rate this question