Examkin

Question

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

An IT administrator is designing an Azure deployment strategy for a new application. The architecture requires deploying virtual machines in the North Europe region and storage accounts in the West Europe region. The administrator wants to manage the lifecycle of all these resources together as a single unit and minimize administrative overhead. Which configuration represents a valid deployment topology in Azure?

  1. Deploy all virtual machines and storage accounts into a single resource group located in North Europe.Answer
  2. B
    Nest a resource group dedicated to West Europe resources inside a parent resource group dedicated to North Europe resources.
  3. C
    Deploy the virtual machines in a North Europe resource group, and deploy the storage accounts in a separate West Europe resource group because resources must reside in the same region as their resource group.
  4. D
    Deploy all resources in a single resource group, but migrate the storage accounts to North Europe since all resources must match the resource group's location.

Answer

Deploy all virtual machines and storage accounts into a single resource group located in North Europe.
The correct option is to deploy all virtual machines and storage accounts into a single resource group in North Europe. Azure allows resources from different regions (such as North Europe and West Europe) to be placed in the same resource group. The location of the resource group determines where its metadata is stored, but does not restrict the location of the resources it contains.

Step-by-Step Solution

1
Analyze the deployment requirements for virtual machines (North Europe) and storage accounts (West Europe) under a single lifecycle management boundary.
Since they share a lifecycle and need minimized administrative overhead, placing them in a single resource group is the recommended practice.
A resource group acts as a logical container for resources that share the same lifecycle.
2
Evaluate region constraints for resources within a resource group.
Resources do not have to match the region of the resource group.
The resource group location only dictates where the group's metadata is stored.
3
Verify resource group nesting rules.
Resource groups cannot be nested.
Azure architecture only supports a flat structure for resource groups under a subscription.

Key Concept

Resource group location and nesting rules
Rate this question

Topics

Azure Resources, Resource Groups, Subscriptions, and Management Groups