Question

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

A logistics company is setting up a new supply chain tracking application in Azure. The application requires virtual machines to be deployed in the West Europe region for low-latency access by local users. However, the company's resource group for the project, named rg-supplychain, is created in the North Europe region due to compliance storage guidelines for metadata. Which of the following describes a valid deployment and organization scenario for this application?

  1. The virtual machines can be deployed in the West Europe region while residing inside the rg-supplychain resource group located in the North Europe region.Answer
  2. B
    The virtual machines must be deployed in the North Europe region to match the geographical location of the containing resource group.
  3. C
    The virtual machines must be placed inside a separate resource group that is nested inside the rg-supplychain resource group.
  4. D
    The virtual machines will automatically inherit all resource tags applied to the rg-supplychain resource group.

Answer

The virtual machines can be deployed in the West Europe region while residing inside the rg-supplychain resource group located in the North Europe region.
The correct option states that the virtual machines can be deployed in the West Europe region while residing inside the resource group located in North Europe. Azure resource groups act as logical containers, and their location only determines where the resource group's metadata is stored. Resources within a resource group can be located in different regions than the resource group itself.

Step-by-Step Solution

1
Analyze the relationship between resource locations and resource group locations.
Identify that Azure allows resources to be in a different region than their containing resource group.
The resource group location is where the resource group's deployment metadata is stored, not a constraint on the resources themselves.
2
Evaluate the possibility of nesting resource groups.
Determine that resource groups cannot contain other resource groups.
Azure Resource Manager uses a flat structure for resource groups within a subscription.
3
Evaluate resource tag inheritance.
Determine that resources do not automatically inherit tags from their resource groups.
Tags must be applied directly to resources or handled via Azure Policy, as inheritance is not automatic.

Key Concept

Azure resource groups act as logical containers for resources, but resources can reside in different physical regions than the resource group itself, and resource groups cannot be nested.
Rate this question