You configure the Azure resource hierarchy for a business unit. The hierarchy includes a Management Group named Global-MG, an Azure subscription named Sub-Finance, and two resource groups named RG-Core and RG-Sandbox.
You assign the 'Allowed locations' Azure Policy definition to Sub-Finance. The policy definition is configured to permit resource creation only in the East US or West US regions. You add RG-Sandbox to the exclusion list (Not Scopes) of this policy assignment.
What is the result when an administrator attempts to deploy a new storage account in the West Europe region within RG-Sandbox?
- The storage account is successfully created in West Europe.Cevap
- BThe deployment is blocked because the subscription-level policy assignment inherits to all resource groups.
- CThe storage account is successfully created in West Europe but is automatically deleted by Azure Policy after the next compliance scan.
- DThe deployment is redirected, and the storage account is created in East US to comply with the allowed locations list.
Cevap
The storage account is successfully created in West Europe.
The correct answer is that the storage account is successfully created in West Europe. When a resource group is added to the exclusion list (Not Scopes) of a policy assignment, the policy is completely bypassed for any resources created within that resource group. Therefore, the restriction to East US or West US does not apply to RG-Sandbox.
Adım Adım Çözüm
Anahtar Kavram
Azure Policy exclusions (Not Scopes) prevent the policies assigned at higher scopes from being applied to the excluded resource groups or resources.