AZ-104 Manage Azure Identities and Governance Practice Question
A security team needs to grant and remove RBAC access for a set of operators on resources in one resource group, but those operators must not create, modify, or delete the resources themselves. Which built-in role should be assigned?
⚠ Common exam trap
Watch out — candidates often confuse the Contributor role (which can manage resources but not role assignments) with the User Access Administrator role, or mistakenly think the Reader role is sufficient for managing access, when in fact only roles with Microsoft.Authorization/roleAssignments/write can grant or remove RBAC assignments.
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
✓
User Access Administrator at the resource group scope.
The User Access Administrator role at the resource group scope grants the ability to manage RBAC role assignments for other users on resources within that resource group, but it does not grant permissions to create, modify, or delete the resources themselves. This meets the security team's requirement to grant and remove access without allowing resource management.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Reader, because it is the most restrictive role available.
Why it's wrong here
Reader is the most restrictive built-in role, but it is too restrictive for this task because it only grants read permissions to resources and does not include any Microsoft.Authorization actions. Without Microsoft.Authorization/roleAssignments/write, the security team cannot create new role assignments, and without the delete counterpart they cannot remove existing ones. Moreover, a Reader cannot even modify its own role assignment to gain more permissions, because the write action is not allowed. Delegating access management requires a role that includes authorization-write capabilities, which Reader explicitly lacks.
When this WOULD be correct
A question where the requirement is to allow operators to view resources and their configurations in a resource group without making any changes, and no role management is needed.
- ✗
Contributor, because it can manage resources and role assignments together.
Why it's wrong here
Contributor has full management permissions over all resources in the resource group, including the ability to create, modify, and delete resources, but it deliberately excludes the Microsoft.Authorization/* operations. This means Contributor cannot assign or remove RBAC role assignments, so the security team would still be unable to perform the required access changes. In addition, assigning Contributor would provide far broader rights than needed, allowing the team to directly manipulate workloads—a clear violation of least privilege. To delegate only access administration, you need a role that includes Microsoft.Authorization/roleAssignments/write without the broader resource-management actions.
When this WOULD be correct
A question where operators need to manage resources (create, modify, delete) but not manage access, and the scope is a resource group. For example: 'Which role allows a team to deploy and manage VMs and storage accounts in a resource group?'
- ✓
User Access Administrator at the resource group scope.
Why this is correct
User Access Administrator is the built-in role designed for managing access permissions without granting broad resource management rights. At the resource group scope, it lets the security team add and remove RBAC assignments for that group while avoiding direct control over the workload resources themselves. This matches least privilege much better than Owner or Contributor.
- ✗
Tag Contributor, because role management and tagging are both governance tasks.
Why it's wrong here
Tag Contributor is a built-in Azure role that only grants permission to read resources and modify resource tags. It does not include the Microsoft.Authorization/roleAssignments/write action, which is required to create role assignments, nor does it include delete permissions necessary to remove access. Tagging and RBAC administration are separate control-plane operations; having a governance-focused role does not imply the ability to delegate other governance-related permissions. Therefore, the security team could only change metadata, not manage who has access.
When this WOULD be correct
A question that asks which role allows operators to manage resource tags (e.g., add, modify, or delete tags) but not create, modify, or delete the resources themselves. The Tag Contributor role would be correct for that scenario.
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.
✓User Access Administrator at the resource group scope.Correct answer▾
Why this is correct
User Access Administrator is the built-in role designed for managing access permissions without granting broad resource management rights. At the resource group scope, it lets the security team add and remove RBAC assignments for that group while avoiding direct control over the workload resources themselves. This matches least privilege much better than Owner or Contributor.
✗Reader, because it is the most restrictive role available.Wrong answer — click to see why▾
Why this is wrong here
The Reader role only allows read access to resources, not the ability to grant or remove RBAC roles, which is required by the question.
★ When this WOULD be the correct answer
A question where the requirement is to allow operators to view resources and their configurations in a resource group without making any changes, and no role management is needed.
Why candidates choose this
Candidates may think Reader is the most restrictive role and assume it can be combined with other permissions, but it lacks the role management capability needed for granting and removing RBAC access.
✗Contributor, because it can manage resources and role assignments together.Wrong answer — click to see why▾
Why this is wrong here
The Contributor role allows operators to create, modify, and delete resources, which violates the requirement that operators must not perform these actions. It also does not grant permission to manage role assignments.
★ When this WOULD be the correct answer
A question where operators need to manage resources (create, modify, delete) but not manage access, and the scope is a resource group. For example: 'Which role allows a team to deploy and manage VMs and storage accounts in a resource group?'
Why candidates choose this
Candidates may confuse Contributor with a role that can manage both resources and access, or they may think Contributor is the default role for operational tasks without reading the restriction carefully.
✗Tag Contributor, because role management and tagging are both governance tasks.Wrong answer — click to see why▾
Why this is wrong here
The Tag Contributor role allows managing tags on resources but does not include the 'Microsoft.Authorization/roleAssignments/write' permission needed to grant or remove RBAC role assignments, which is the core requirement.
★ When this WOULD be the correct answer
A question that asks which role allows operators to manage resource tags (e.g., add, modify, or delete tags) but not create, modify, or delete the resources themselves. The Tag Contributor role would be correct for that scenario.
Why candidates choose this
Candidates may associate 'governance tasks' with both tagging and role management, incorrectly assuming that a role focused on tagging also includes permissions for managing RBAC assignments.
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?”
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
Learn chapter
Privileged Identity Management (PIM)
Key term
Resource group
A logical container in Microsoft Azure that holds related resources for an application or solution, enabling unified management, security, and billing.
Key term
Security
Security in IT is the practice of protecting systems, networks, and data from unauthorized access, damage, or theft.
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.