A healthcare provider, MedPulse Dynamics, organizes its subscriptions using the following Management Group hierarchy:
- Tenant Root Group
- Clinical-MG
- Subscription 1 (Clinical Apps)
- Resource Group A
- Billing-MG
- Subscription 2 (Billing Portal)
An administrator assigns the Reader role to a user at the Clinical-MG level. What is the user's access level to Resource Group A?
- The user has Reader access to Resource Group A because the role is inherited down the hierarchy.Cevap
- BThe user has Reader access to Resource Group A, but this permission can be blocked by creating a custom Deny Reader role assignment directly on Resource Group A.
- CThe user has no access to Resource Group A because applying a ReadOnly resource lock at the Clinical-MG level blocks all RBAC role inheritance.
- DThe user has Reader access to Resource Group A, but only if a policy is assigned to the Tenant Root Group that explicitly enables RBAC role inheritance.
Cevap
The user has Reader access to Resource Group A because the role is inherited down the hierarchy.
The correct answer is correct because Azure RBAC role assignments inherit down the resource hierarchy. Since the Reader role is assigned at the Clinical-MG level, any child resources—including Subscription 1 and Resource Group A—will inherit this assignment, granting the user Reader access.
Adım Adım Çözüm
Anahtar Kavram
Azure RBAC inheritance flows down the Management Group hierarchy to child subscriptions and resources, and cannot be blocked by user-defined deny assignments or resource locks.