An administrator is setting up an Azure environment for a new sales application. The administrator creates a resource group named rg-sales-data and sets its location to North Europe. The database for the application must be deployed in West Europe to meet local compliance requirements, while the virtual machine can be deployed in North Europe. Which configuration option should the administrator use to deploy these resources?
- Deploy both the database in West Europe and the virtual machine in North Europe directly within the rg-sales-data resource group.Cevap
- BCreate a nested resource group named rg-nested-db inside rg-sales-data, set its location to West Europe, and deploy the database there.
- CDeploy both resources in North Europe, because all resources in a resource group must reside in the same geographical region as the resource group itself.
- DDeploy the database in West Europe under rg-sales-data only after modifying the resource group's location to West Europe, as resources cannot reside in a different location than their parent resource group.
Cevap
Deploy both the database in West Europe and the virtual machine in North Europe directly within the rg-sales-data resource group.
The correct configuration is to deploy both the database in West Europe and the virtual machine in North Europe directly within the rg-sales-data resource group. Azure resource groups do not restrict the location of the resources they contain. A resource group's location is only used to store its metadata, allowing you to group resources that share a lifecycle even if they are deployed in different regions.
Adım Adım Çözüm
Anahtar Kavram
Azure resource groups act as logical containers for resources, and resources inside a resource group can reside in different regions than the resource group itself. Additionally, resource groups cannot be nested.