A company plans to deploy a multi-tier web application in Azure. The deployment architecture requires resources to be distributed across different geographical locations for high availability, while keeping billing and administrative access segregated for different departments.
Which two configuration guidelines are valid when designing the Azure resource hierarchy? (Select two)
- Deploying resources in different Azure regions than the region of the resource group they belong toAnswer
- BNesting database resource groups inside web application resource groups to inherit permission and lock configurations
- Using separate subscriptions to enforce distinct billing boundaries and access control limits across departmentsAnswer
- DConfiguring resources to inherit their geographical location automatically from the resource group in which they are placed
Answer
Deploying resources in different Azure regions than the region of the resource group they belong to, and using separate subscriptions to enforce distinct billing boundaries and access control limits across departments.
Deploying resources in different regions than their resource groups is valid because a resource group's location only determines where its metadata is stored. Additionally, using separate subscriptions is a valid configuration as subscriptions represent a billing and access management boundary in Azure.
Step-by-Step Solution
Key Concept
Azure resource groups hold metadata and have no region restrictions on resources, while subscriptions establish logical boundaries for billing and access control.