Question

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

A company plans to deploy a multi-tier application consisting of a virtual machine and a storage account. The administrator creates a resource group named rg-app-prod in the North Europe region. Which of the following configurations is supported when deploying these resources?

  1. Deploying the virtual machine to the West Europe region and the storage account to the North Europe region, both inside rg-app-prod.Answer
  2. B
    Creating a nested resource group named rg-app-storage inside rg-app-prod to isolate the storage account.
  3. C
    Deploying the virtual machine to the West Europe region only after changing the location of rg-app-prod to West Europe, as resources must match their resource group's location.
  4. D
    Deploying the virtual machine to North Europe and having it automatically inherit all tags applied to the parent resource group.

Answer

Deploying the virtual machine to the West Europe region and the storage account to the North Europe region, both inside rg-app-prod.
Deploying the virtual machine to the West Europe region and the storage account to the North Europe region, both inside the resource group, is fully supported. Resources do not need to be in the same location as the resource group that contains them. The resource group's location only determines where its own metadata is stored.

Step-by-Step Solution

1
Analyze the relationship between resource groups and resource locations.
Azure resources do not inherit their location from the resource group they reside in, allowing a resource group to contain resources from multiple different regions.
This flexibility allows logically related resources to be managed together even if they are physically deployed in different regions for latency or residency reasons.
2
Evaluate the rules concerning resource group structure.
Resource groups cannot be nested inside other resource groups.
Azure Resource Manager uses a flat hierarchy structure under each subscription for resource groups.
3
Verify tag inheritance behavior.
Resource tags applied at the resource group level are not inherited by the resources inside that resource group automatically.
Understanding governance behavior ensures that administrators correctly plan their tagging strategy using Azure Policy if inheritance is required.

Key Concept

Azure resource group boundaries, location independence, and flat hierarchy rules
Estimated Time:1m 0s
Rate this question