Question

Difficulty: MediumAzure Resource Manager (ARM) and ARM Templates/Bicep

A company is designing an Azure Resource Manager (ARM) template to deploy a multi-tier application. The development team proposes a template structure where a web app and database are deployed inside a primary resource group, and a secondary resource group is nested inside the primary resource group to hold the storage account. How does Azure Resource Manager (ARM) handle this proposed deployment?

  1. The deployment fails because Azure Resource Manager does not support nesting resource groups inside other resource groups.Answer
  2. B
    The deployment succeeds because ARM templates automatically create and nest resource groups to organize resources hierarchically.
  3. C
    The deployment succeeds only if the template includes imperative commands that specify the exact step-by-step order for nesting the resource groups.
  4. D
    The deployment fails because all resources defined within a single template are restricted to the physical location of the primary resource group.

Answer

The deployment fails because Azure Resource Manager does not support nesting resource groups inside other resource groups.
The correct answer is that the deployment will fail because Azure Resource Manager (ARM) does not support nesting resource groups inside other resource groups. All resource groups in Azure exist as flat, top-level logical boundaries directly under an Azure subscription.

Step-by-Step Solution

1
Analyze the proposed structure of the template deployment.
The proposal calls for a secondary resource group to be nested inside a primary resource group.
Understanding the containment structure of the resources helps identify architectural violations.
2
Evaluate the architectural constraints of Azure Resource Groups.
Azure Resource Groups are top-level logical containers under an Azure subscription and do not support hierarchical nesting.
This determines if the proposed structure is valid under Azure Resource Manager constraints.
3
Confirm the behavior of ARM template deployment with resource location and syntax rules.
Because nesting is inherently unsupported, the template deployment will fail. ARM templates are declarative and cannot override resource containment rules, nor are resources restricted to the location of the resource group they reside in.
This eliminates the distractors that suggest successful deployment under certain conditions or fail for incorrect reasons.

Key Concept

Azure Resource Group Boundaries and ARM Template Capabilities
Rate this question