The answer is at the RG-Operations resource group scope. This is correct because Azure RBAC role assignments are inherited downward through the hierarchy: from management group to subscription to resource group, and finally to individual resources. By scoping the Virtual Machine Contributor role to the RG-Operations resource group, you grant the contractor start, stop, and read permissions only on VMs within that scope, while the RG-Development resource group remains unaffected since no role assignment exists there. On the AZ-104 exam, this scenario tests your understanding of scope inheritance and the principle of least privilege—a common trap is assigning the role at the subscription level, which would inadvertently grant access to all resource groups, including RG-Development. A reliable memory tip is to think of scope as a spotlight: the narrower the beam (resource group), the fewer resources it illuminates, ensuring you only light up what’s needed.
AZ-104 Manage Azure Identities and Governance Practice Question
This AZ-104 practice question tests your understanding of manage azure identities and governance. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
An organization has one Azure subscription with separate resource groups for Development and Operations. A contractor must start, stop, and read the properties of virtual machines only in RG-Operations. The contractor must not have access to virtual machines in RG-Development. Where should the role assignment be created?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
At the RG-Operations resource group scope
Role assignments in Azure are inherited from higher scopes (management group, subscription, resource group) down to lower scopes. To grant the contractor the Virtual Machine Contributor role (or a custom role with start/stop/read permissions) only on VMs in RG-Operations and explicitly deny access to RG-Development, the assignment must be scoped to the RG-Operations resource group. Assigning at a higher scope (subscription or management group) would grant access to all resource groups, including RG-Development, violating the requirement.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
At the subscription scope
Why it's wrong here
This would grant the contractor access to all matching resources in every resource group in the subscription.
✓
At the RG-Operations resource group scope
Why this is correct
This limits the assignment to only resources inside RG-Operations, which satisfies least privilege.
Related concept
Read the scenario before looking for a memorised answer.
✗
At the management group scope
Why it's wrong here
This would be broader than needed and could affect additional subscriptions beyond the target one.
✗
At an individual virtual machine scope
Why it's wrong here
This would apply to only one VM, not to all VMs in the Operations resource group.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume assigning a role at the subscription scope is simpler and still allows them to control access via resource group membership, but they forget that role assignments at higher scopes are inherited by all child scopes, granting unintended access to resources in other resource groups like RG-Development.
Detailed technical explanation
How to think about this question
Azure RBAC uses a hierarchical inheritance model where permissions flow from higher scopes (management group, subscription, resource group) down to child scopes. When a role is assigned at the resource group scope, it applies to all resources within that group, including VMs, but not to resources in other resource groups. The Virtual Machine Contributor role (built-in) includes Microsoft.Compute/virtualMachines/start/action, Microsoft.Compute/virtualMachines/powerOff/action, and Microsoft.Compute/virtualMachines/read, which satisfy the start, stop, and read properties requirements. Deny assignments (e.g., via Azure Blueprints or custom policies) can further enforce exclusions, but the simplest and most secure approach is to scope the role assignment directly to RG-Operations.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Manage Azure Identities and Governance — This question tests Manage Azure Identities and Governance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: At the RG-Operations resource group scope — Role assignments in Azure are inherited from higher scopes (management group, subscription, resource group) down to lower scopes. To grant the contractor the Virtual Machine Contributor role (or a custom role with start/stop/read permissions) only on VMs in RG-Operations and explicitly deny access to RG-Development, the assignment must be scoped to the RG-Operations resource group. Assigning at a higher scope (subscription or management group) would grant access to all resource groups, including RG-Development, violating the requirement.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.