Question

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

An administrator manages an Azure subscription and is planning the following deployment activities:

1. Create an Azure resource group named `App-RG` in the `North Europe` region, and then create a nested resource group named `DB-RG` inside `App-RG` to store database resources.
2. Deploy an Azure Virtual Machine named `Web-VM` to the `West Europe` region, and place it inside the `App-RG` resource group.

Which of the planned deployment activities can be successfully completed?

  1. Only activity 2Answer
  2. B
    Only activity 1
  3. C
    Both activity 1 and activity 2
  4. D
    Neither activity 1 nor activity 2

Answer

Only activity 2
In Azure, resource groups are flat namespaces and cannot be nested inside one another, which makes activity 1 impossible. However, resources do not inherit or depend on the region of their resource group. A resource group in one region can contain resources located in completely different regions, which makes activity 2 valid.

Step-by-Step Solution

1
Evaluate the first activity regarding nested resource groups.
Activity 1 fails.
Azure Resource Manager does not support nesting resource groups. All resource groups exist directly under an Azure subscription.
2
Evaluate the second activity regarding resource and resource group region mismatch.
Activity 2 succeeds.
The location of a resource group defines where its deployment metadata is stored. Individual resources within the resource group can be deployed in any supported region, regardless of the resource group's location.
3
Combine the evaluations to select the correct choice.
Only activity 2 can be successfully completed.
Combining the failure of activity 1 and success of activity 2 leaves 'Only activity 2' as the only valid outcome.

Key Concept

Azure Resource Group limitations (no nesting) and resource region independence.
Rate this question