Question

Difficulty: HardAzure Resources, Resource Groups, Subscriptions, and Management Groups

An administrator is planning the deployment of a new multi-tier application in Azure and proposes the following resource configuration:

1. Create a parent resource group named RG-Prod in the North Europe region.
2. Create a child resource group named RG-DB nested inside RG-Prod to isolate database resources.
3. Deploy an Azure SQL Database to the West Europe region, but place it within the RG-DB resource group.
4. Apply cost-center tags to RG-DB and rely on the database to automatically inherit these tags.

Which statement correctly identifies the validity of this proposed configuration?

  1. A
    Only the tag inheritance is invalid; resource groups can be nested, and resources can be deployed to a different region than their resource group.
  2. B
    Only the deployment of the SQL database to a different region is invalid because resources must reside in the same region as their resource group; nesting and tag inheritance are fully supported.
  3. Only the deployment of the SQL database to a different region than its resource group is valid; resource groups cannot be nested, and resources do not inherit tags from their resource group.Answer
  4. D
    Only the nesting of resource groups is invalid; the database can reside in a different region than its resource group and it will automatically inherit the tags applied to the resource group.

Answer

Only the deployment of the SQL database to a different region than its resource group is valid; resource groups cannot be nested, and resources do not inherit tags from their resource group.
The correct option is valid because Azure allows resources to reside in a different region than their resource group. Resource group nesting is not supported, and resources do not automatically inherit tags applied to their resource group.

Step-by-Step Solution

1
Evaluate the feasibility of nesting resource groups in Azure.
Creating RG-DB inside RG-Prod is invalid.
Azure does not support hierarchical nesting of resource groups; all resource groups exist flatly under a subscription.
2
Evaluate the geographical region compatibility between a resource and its resource group.
Deploying a SQL database in West Europe inside a resource group in North Europe is valid.
A resource group's location only determines where its metadata is stored, and resources can be deployed to any supported Azure region regardless of their resource group's region.
3
Evaluate the tag inheritance rule between resource groups and resources.
Expecting the SQL database to automatically inherit tags from RG-DB is invalid.
Azure does not support automatic tag inheritance from a resource group to its resources; tags must be applied directly or enforced via Azure Policy.

Key Concept

Azure resource groups are flat, non-nested logical containers that can hold resources from different regions, and they do not automatically propagate tags to the resources they contain.
Rate this question