Veridian Manufacturing manages its Azure resources using the following Management Group (MG) hierarchy:
* Tenant Root Group (Policy assigned: Audit public IP addresses)
* Infrastructure-MG (User1 assigned Reader role)
* Security-MG
* Subscription-A
* Core-Services-MG
* Operations-MG
* Subscription-B
An administrator relocates Subscription-A from Security-MG to Operations-MG.
What is the status of User1's RBAC role assignment and the audit policy for resources inside Subscription-A after the move?
- User1 loses the Reader role for Subscription-A, and the audit policy remains active.Cevap
- BUser1 retains the Reader role for Subscription-A, and the audit policy remains active.
- CUser1 loses the Reader role for Subscription-A, and the audit policy is no longer active.
- DUser1 retains the Reader role for Subscription-A, and the audit policy is no longer active.
Cevap
User1 loses the Reader role for Subscription-A, and the audit policy remains active.
The correct answer is that User1 loses the Reader role for Subscription-A, and the audit policy remains active. In Azure, both RBAC role assignments and Azure Policies inherit down the management group hierarchy. When Subscription-A is relocated, any inherited RBAC permissions originating from Infrastructure-MG are lost because the subscription's new path (Tenant Root Group -> Core-Services-MG -> Operations-MG) no longer includes Infrastructure-MG. However, since the audit policy is assigned at the Tenant Root Group, which remains the root ancestor of the subscription, the policy continues to inherit and apply to resources inside Subscription-A.
Adım Adım Çözüm
Anahtar Kavram
Azure Policy and RBAC inheritance behavior during subscription relocation within a Management Group hierarchy.