An organization manages an Azure environment with a subscription named Sub-ECommerce. The subscription contains a resource group named rg-payment.
A user named User1 is assigned the following roles:
- The Reader role at the Sub-ECommerce subscription scope
- The Contributor role at the rg-payment resource group scope
- The Global Reader role in Microsoft Entra ID
User1 attempts to create a new storage account inside the rg-payment resource group.
What is the outcome of User1's attempt?
- The storage account is created successfully, because Azure RBAC roles are additive and the Contributor role at the resource group level grants the required permissions.Answer
- BThe creation fails, because the Reader role assigned at the subscription level is more restrictive and inherits down to override the Contributor role at the resource group level.
- CThe creation fails, because the Microsoft Entra ID Global Reader role is a directory-level role that enforces read-only access on all Azure resources across the tenant.
- DThe creation fails, because User1 must be assigned a role within an Administrative Unit that contains the rg-payment resource group.
Answer
The storage account is created successfully, because Azure RBAC roles are additive and the Contributor role at the resource group level grants the required permissions.
The correct answer is correct because Azure Role-Based Access Control (RBAC) is additive. When a user has multiple role assignments, the effective permission is the sum of those role assignments. In this scenario, the Reader role at the subscription level provides read access, while the Contributor role at the resource group level provides read/write access. Since the permissions are additive, the Contributor permissions apply to the resource group, allowing the user to create the storage account. The Microsoft Entra ID Global Reader role operates in the directory plane and does not restrict Azure resource access.
Step-by-Step Solution
Key Concept
Azure RBAC roles are additive. Scope-specific assignments grant permissions that are not blocked by inherited roles at a higher scope.