AZ-104 Manage Azure Identities and Governance Practice Question
An administrator assigns Contributor at the RG-Apps resource group scope and Reader at the subscription scope. A developer opens a VM inside RG-Apps and can change its settings, but a different VM in RG-Shared is read-only. Which statement best explains this behavior?
⚠ Common exam trap
It's easy for candidates to confuse inheritance with direct assignments, thinking that a role at a higher scope (subscription) always overrides a role at a lower scope (resource group), when in fact RBAC combines permissions additively and the most permissive role at the most specific scope wins.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The VM in RG-Apps inherited Contributor from the resource group, while RG-Shared only inherits Reader.
Role assignments in Azure are inherited from higher scopes (subscription, management group) down to lower scopes (resource group, resource). The developer has Reader at the subscription scope, which is inherited by all resource groups, including RG-Shared. However, the Contributor assignment at the RG-Apps resource group scope overrides the inherited Reader for that specific resource group, granting write access to VMs within RG-Apps. RG-Shared has no direct role assignment, so it only inherits the subscription-level Reader, making its VMs read-only.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The VM in RG-Apps has a direct Contributor assignment that does not apply elsewhere.
Why it's wrong here
The scenario specifically says the Contributor role was assigned at the RG-Apps resource group scope, not directly on the VM. A direct assignment would be listed on the VM's Access control (IAM) blade as a direct role assignment, while an inherited assignment appears as inherited or effective. Because the assignment is at the resource group level, the VM inherits it; it is not a separate direct assignment.
When this WOULD be correct
If a user is directly assigned the Contributor role on a specific VM resource (not at the resource group scope), and no other roles apply, then that direct assignment would grant write access only to that VM and not to others in the same resource group.
- ✓
The VM in RG-Apps inherited Contributor from the resource group, while RG-Shared only inherits Reader.
Why this is correct
RBAC permissions are inherited from higher scopes to lower scopes. When Contributor is assigned to the RG-Apps resource group, all resources within, including the VM, inherit that role at that scope. RG-Shared, being outside that scope, only gets the subscription-level Reader assignment, so its resources don't receive Contributor. This additive inheritance explains why the VM has Contributor effective access.
- ✗
Reader always overrides Contributor when both roles exist in the same subscription.
Why it's wrong here
RBAC authorization is cumulative, not override-based. If the same principal holds both Reader and Contributor at overlapping scopes, the effective permissions are the union of both roles, so the Reader role does not negate any of Contributor's write actions. Only an explicit Deny assignment can block permissions, and a lower-privileged role like Reader cannot override a higher-privileged one.
When this WOULD be correct
This option would be correct if the question described a scenario where a user has both a deny assignment and a role assignment, and the deny assignment explicitly overrides the role. For example, if a custom role with 'NotActions' or a deny assignment is applied at a higher scope that blocks write access even if Contributor is assigned at a lower scope.
- ✗
Azure Policy is granting write access only inside RG-Apps because the subscription has no policy.
Why it's wrong here
Azure Policy is a compliance and governance service that evaluates resources against rules, using deny, audit, or deploy effects. It does not grant RBAC permissions; write access comes solely from role assignments like Contributor. Even without a subscription policy, Policy cannot create access rights—it can only block or modify configuration for non-compliance, not assign Contributor.
When this WOULD be correct
A question where a VM in RG-Apps can be modified but a VM in RG-Shared cannot, and the subscription has a policy that denies write access to all resources except those in RG-Apps. The policy would be the reason for the difference.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓The VM in RG-Apps inherited Contributor from the resource group, while RG-Shared only inherits Reader.Correct answer▾
Why this is correct
RBAC permissions are inherited from higher scopes to lower scopes. When Contributor is assigned to the RG-Apps resource group, all resources within, including the VM, inherit that role at that scope. RG-Shared, being outside that scope, only gets the subscription-level Reader assignment, so its resources don't receive Contributor. This additive inheritance explains why the VM has Contributor effective access.
✗The VM in RG-Apps has a direct Contributor assignment that does not apply elsewhere.Wrong answer — click to see why▾
Why this is wrong here
The VM in RG-Apps does not have a direct Contributor assignment; it inherits Contributor from the resource group scope. The behavior is explained by inheritance, not direct assignment.
★ When this WOULD be the correct answer
If a user is directly assigned the Contributor role on a specific VM resource (not at the resource group scope), and no other roles apply, then that direct assignment would grant write access only to that VM and not to others in the same resource group.
Why candidates choose this
Candidates may confuse direct role assignments with inherited ones, thinking that a role applied at a resource group is the same as a direct assignment on each resource.
✗Reader always overrides Contributor when both roles exist in the same subscription.Wrong answer — click to see why▾
Why this is wrong here
In Azure RBAC, roles are additive and inherited; Reader at subscription scope does not override Contributor at resource group scope. The VM in RG-Shared is read-only because it only inherits Reader from the subscription, not because Reader overrides Contributor.
★ When this WOULD be the correct answer
This option would be correct if the question described a scenario where a user has both a deny assignment and a role assignment, and the deny assignment explicitly overrides the role. For example, if a custom role with 'NotActions' or a deny assignment is applied at a higher scope that blocks write access even if Contributor is assigned at a lower scope.
Why candidates choose this
Candidates may mistakenly think that higher-scope roles always override lower-scope roles, or that Reader is a 'stronger' role that cancels out Contributor, when in fact RBAC permissions are cumulative and additive.
✗Azure Policy is granting write access only inside RG-Apps because the subscription has no policy.Wrong answer — click to see why▾
Why this is wrong here
Azure Policy does not grant write access; it enforces rules (e.g., tagging, locations). The developer's ability to change settings in RG-Apps is due to RBAC role inheritance, not policy.
★ When this WOULD be the correct answer
A question where a VM in RG-Apps can be modified but a VM in RG-Shared cannot, and the subscription has a policy that denies write access to all resources except those in RG-Apps. The policy would be the reason for the difference.
Why candidates choose this
Candidates may confuse Azure Policy with RBAC, thinking policies can grant permissions, or they may overestimate the role of policies in access control scenarios.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
Learn chapter
Dynamic Membership Groups
Key term
Scope
In IT, scope defines the boundaries, goals, and deliverables of a project, assessment, or engagement, specifying what is included and what is excluded.
Key term
Subscription
A subscription is a payment model where you pay a recurring fee to access a product or service instead of buying it once and owning it forever.
About these practice questions
This AZ-104 question is part of Courseiva's 1,049-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.