Examkin

Question

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

An organization is planning to deploy a new application in Azure. The administrator proposes a design that includes the following details:

1. A resource group named rg-app is created in the East US region.
2. A virtual machine is deployed in the East US region within rg-app.
3. A storage account is deployed in the West US region within rg-app to store regional backup data.
4. A resource group named rg-app-db is created inside rg-app as a nested resource group to isolate database resources and their access permissions.

Which statement correctly evaluates this proposed design?

  1. A
    The design is not supported because a storage account located in the West US region cannot reside in a resource group located in the East US region.
  2. The design is not supported because Azure does not allow nesting one resource group inside another.Answer
  3. C
    The design is fully supported because Azure allows resource group nesting and supports placing resources in different regions than their resource group.
  4. D
    The design is not supported because all resources placed inside rg-app must be deployed in the East US region to match the resource group's location.

Answer

The design is not supported because Azure does not allow nesting one resource group inside another.
The correct design evaluation is that Azure does not support nesting resource groups. While resources can be deployed in a different region than their containing resource group (e.g., a West US storage account in an East US resource group), the proposal to create a resource group inside another resource group is invalid.

Step-by-Step Solution

1
Analyze the location constraint: the resource group is in East US, but a storage account is in West US.
This configuration is valid because Azure resources can be in a different region than their parent resource group.
A resource group's location specifies where its metadata is stored, but does not restrict resource placement.
2
Analyze the nesting constraint: creating a resource group inside another resource group.
This configuration is invalid because Azure does not support nested resource groups.
Resource groups are flat logical containers; they cannot be nested inside one another.
3
Combine the evaluations to determine the overall feasibility of the design.
The design is not supported due to the nested resource group requirement.
Since one part of the proposed design is invalid (nesting), the entire design is not supported, and the correct statement must identify the nesting limitation as the blocker.

Key Concept

Azure resource group limitations: nesting is unsupported, but cross-region resource placement is supported.
Rate this question

Topics

Azure Resources, Resource Groups, Subscriptions, and Management Groups