A healthcare startup is deploying an application in Azure. The compliance team requires that all patient data storage accounts be located in the UK South region. The application's virtual machines must be deployed in the West Europe region. The IT team wants to deploy, manage, and delete all of these resources together as a single logical unit. Which resource organization strategy should the administrator implement to meet these requirements?
- ACreate a parent resource group in West Europe, and nest a child resource group in UK South inside it to separate the regional deployments while preserving the lifecycle.
- BDeploy the virtual machines and the storage accounts into two separate resource groups, because all resources must reside in the same region as their containing resource group.
- Deploy all resources in a single resource group, selecting UK South for the storage accounts and West Europe for the virtual machines during deployment.Answer
- DDeploy the virtual machines and storage accounts under separate Azure subscriptions, because a single resource group cannot hold resources that reside in different regions.
Answer
Deploy all resources in a single resource group, selecting UK South for the storage accounts and West Europe for the virtual machines during deployment.
Deploying all resources in a single resource group with their respective locations is correct because Azure resource groups are logical containers designed to manage the lifecycle of related resources together. A resource group can contain resources from different geographical regions, and resources do not inherit or copy the location of their containing resource group.
Step-by-Step Solution
Key Concept
Azure Resource Groups regional independence and lifecycle management