AZ-104 Manage Azure Identities and Governance Practice Question
The service desk needs to add and remove users from a support group that grants access to an internal application, but the service desk must not receive Azure subscription permissions. Which two actions should you take? Select two.
⚠ Common exam trap
Many exam-takers confuse Azure RBAC roles (like Contributor) with Microsoft Entra ID directory roles or group ownership, mistakenly thinking that managing group membership requires subscription-level permissions.
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
✓
Create a security group in Microsoft Entra ID for the application access.
Creating a security group in Microsoft Entra ID (formerly Azure AD) allows you to manage access to the internal application without granting any Azure subscription permissions. The service desk can then add or remove users from this group, and the application's access control can be configured to rely on group membership, ensuring the service desk staff never receive Azure RBAC roles.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a security group in Microsoft Entra ID for the application access.
Why this is correct
Security groups are the standard Entra ID container for access management. They let you grant permissions once and control membership centrally, which is ideal for a support team that will add and remove users often.
- ✓
Add the service desk staff as owners of that group.
Why this is correct
Adding the service desk staff as owners of the Entra ID security group grants them delegated permission to manage group membership without conferring any of the group's Azure resource access rights. Ownership is a directory-level admin capability that allows adding or removing members, but it does not inherit the entitlements of the group itself, so the support team can administer the group without being able to use the application — a clean separation that satisfies the least-privilege principle and supports frequent membership changes.
- ✗
Assign the service desk staff Contributor on the subscription.
Why it's wrong here
Assigning the service desk staff the Contributor role on the subscription grants them broad Azure resource management rights — such as creating or deleting resources, configuring storage, and managing virtual machines — which far exceeds the narrow need to administer a group's membership. Additionally, Contributor is an Azure RBAC role that applies only to Azure control-plane resources; it has no authority in Microsoft Entra ID and cannot touch security groups. This approach would expose the whole subscription to unnecessary risk while still not enabling the required identity-management task.
When this WOULD be correct
If the question required granting a team full management rights to all resources in a subscription (e.g., to deploy and manage infrastructure), then assigning Contributor on the subscription would be correct.
- ✗
Convert the service desk staff into guest users in the tenant.
Why it's wrong here
Converting the service desk staff to guest users would change their identity type in the tenant, which can invalidate existing directory assignments and introduce unnecessary complexity for an internal support function. Guest accounts have no more group-management ability than members unless explicitly granted an ownership or administrative role, so simply converting them does not delegate anything. Moreover, guest status can cause access issues with internal resources, making this both an ineffective and a disruptive solution.
- ✗
Add the service desk staff as members only, without ownership.
Why it's wrong here
Adding the service desk staff as members only allows them to use the application access granted by the group, but they will have no capability to manage its membership. In Microsoft Entra ID, group membership control is restricted to group owners or delegated directory admins; regular members have no built-in permission to add or remove others. Thus, this arrangement fails to satisfy the requirement for the service desk to maintain user access, because they can only consume the access and cannot delegate it.
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.
✓Create a security group in Microsoft Entra ID for the application access.Correct answer▾
Why this is correct
Security groups are the standard Entra ID container for access management. They let you grant permissions once and control membership centrally, which is ideal for a support team that will add and remove users often.
✗Assign the service desk staff Contributor on the subscription.Wrong answer — click to see why▾
Why this is wrong here
Assigning Contributor on the subscription grants the service desk broad Azure resource permissions, which violates the requirement that they must not receive Azure subscription permissions.
★ When this WOULD be the correct answer
If the question required granting a team full management rights to all resources in a subscription (e.g., to deploy and manage infrastructure), then assigning Contributor on the subscription would be correct.
Why candidates choose this
Candidates may think Contributor is a standard role for managing access, but overlook that it grants excessive permissions beyond just managing group membership.
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
Dynamic Membership Groups
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.
Key term
Group
A group is a collection of users, devices, or other objects that are assigned permissions and policies together for simplified management in identity and governance systems like Microsoft Entra ID.
About these practice questions
Courseiva writes every AZ-104 question from scratch — 1,049 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.