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?
- The deployment fails because Azure Resource Manager does not support nesting resource groups inside other resource groups.Answer
- BThe deployment succeeds because ARM templates automatically create and nest resource groups to organize resources hierarchically.
- CThe deployment succeeds only if the template includes imperative commands that specify the exact step-by-step order for nesting the resource groups.
- DThe 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
Key Concept
Azure Resource Group Boundaries and ARM Template Capabilities