- A
Assign the 'Network Contributor' role at the scope of each existing subscription individually, and remember to assign it to new subscriptions manually.
Why wrong: This approach is inefficient and error-prone because it requires manual effort for each subscription and does not automatically apply to new subscriptions, increasing administrative overhead and risk of omissions.
- B
Assign the 'Network Contributor' role to the security group at the 'Production' management group scope.
Role assignments at the management group scope are inherited by all subscriptions within that management group. This single assignment covers all current subscriptions and automatically applies to any new subscriptions added under the 'Production' management group, making it the most efficient method.
- C
Create an Azure Policy that assigns the 'Network Contributor' role to the security group for all subscriptions under 'Production'.
Why wrong: Azure Policy is used to enforce compliance rules (e.g., allowed resource types) and can deploy resources via 'deployIfNotExists' effects, but it cannot directly assign RBAC roles to a security group. RBAC role assignments must be made through Azure RBAC, not Azure Policy.
- D
Assign the 'Network Contributor' role to the security group at the root management group scope.
Why wrong: Assigning at the root management group scope would grant the 'Network Contributor' role across all subscriptions in the entire tenant, including non-production subscriptions. This violates the principle of least privilege and grants broader access than required.
Quick Answer
The answer is to assign the Network Contributor role to the security group at the Production management group scope. This is the most efficient method because Azure RBAC role assignments at a management group scope are inherited by all child subscriptions, including any new subscriptions added later, ensuring consistent access without manual per-subscription configuration. On the AZ-900 exam, this scenario tests your understanding of management group hierarchy and role inheritance, often appearing as a trap where candidates mistakenly assign the role at the subscription level or to individual users instead of a group. Remember the key principle: management groups are containers for policy and access inheritance, so assigning at the highest necessary scope reduces administrative overhead. A helpful memory tip is "assign once at the group, inherit down the scope"—if you need access across multiple subscriptions, always look to the management group first.
AZ-900 Describe Azure management and governance Practice Question
This AZ-900 practice question tests your understanding of describe azure management 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.
A company has an Azure tenant with a management group hierarchy. The 'Production' management group contains five subscriptions used by the operations team. The IT security team wants to grant the 'Network Contributor' role to a group of network administrators for all subscriptions under the 'Production' management group. The role assignment must automatically apply to any new subscription added under the 'Production' management group in the future. The network administrators already exist as a security group in Azure AD. What is the most efficient way to achieve this?
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
Assign the 'Network Contributor' role to the security group at the 'Production' management group scope.
Assigning the 'Network Contributor' role at the 'Production' management group scope is the most efficient method because management groups provide a hierarchical scope that automatically inherits role assignments to all child subscriptions, including any new subscriptions added in the future. This eliminates the need for manual assignments per subscription and ensures consistent access control across the entire management group hierarchy.
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.
- ✗
Assign the 'Network Contributor' role at the scope of each existing subscription individually, and remember to assign it to new subscriptions manually.
Why it's wrong here
This approach is inefficient and error-prone because it requires manual effort for each subscription and does not automatically apply to new subscriptions, increasing administrative overhead and risk of omissions.
- ✓
Assign the 'Network Contributor' role to the security group at the 'Production' management group scope.
Why this is correct
Role assignments at the management group scope are inherited by all subscriptions within that management group. This single assignment covers all current subscriptions and automatically applies to any new subscriptions added under the 'Production' management group, making it the most efficient method.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Create an Azure Policy that assigns the 'Network Contributor' role to the security group for all subscriptions under 'Production'.
Why it's wrong here
Azure Policy is used to enforce compliance rules (e.g., allowed resource types) and can deploy resources via 'deployIfNotExists' effects, but it cannot directly assign RBAC roles to a security group. RBAC role assignments must be made through Azure RBAC, not Azure Policy.
- ✗
Assign the 'Network Contributor' role to the security group at the root management group scope.
Why it's wrong here
Assigning at the root management group scope would grant the 'Network Contributor' role across all subscriptions in the entire tenant, including non-production subscriptions. This violates the principle of least privilege and grants broader access than required.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse Azure Policy with Azure RBAC, thinking Policy can assign roles, when in fact Policy only evaluates and enforces compliance rules, while role assignments must be done through Azure RBAC at the appropriate scope.
Detailed technical explanation
How to think about this question
Azure RBAC role assignments at a management group scope are inherited by all child subscriptions and resource groups, leveraging the hierarchical structure of management groups. When a new subscription is added under the 'Production' management group, it automatically receives the inherited role assignment without any additional configuration, as Azure RBAC evaluates the effective permissions by traversing the hierarchy from root to resource. This behavior is governed by Azure's role-based access control model, which supports inheritance at management group, subscription, resource group, and resource scopes.
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.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Describe Azure management and governance — study guide chapter
Learn the concepts, then practise the questions
- →
Describe Azure management and governance practice questions
Targeted practice on this topic area only
- →
All AZ-900 questions
1,031 questions across all exam domains
- →
Microsoft Azure Fundamentals AZ-900 study guide
Full concept coverage aligned to exam objectives
- →
AZ-900 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-900 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Describe cloud concepts practice questions
Practise AZ-900 questions linked to Describe cloud concepts.
Describe Azure architecture and services practice questions
Practise AZ-900 questions linked to Describe Azure architecture and services.
Describe Azure management and governance practice questions
Practise AZ-900 questions linked to Describe Azure management and governance.
AZ-900 Azure services practice questions
Practise AZ-900 questions linked to AZ-900 Azure services.
AZ-900 pricing and support practice questions
Practise AZ-900 questions linked to AZ-900 pricing and support.
AZ-900 security and compliance practice questions
Practise AZ-900 questions linked to AZ-900 security and compliance.
AZ-900 governance practice questions
Practise AZ-900 questions linked to AZ-900 governance.
Practice this exam
Start a free AZ-900 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-900 question test?
Describe Azure management and governance — This question tests Describe Azure management and governance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Assign the 'Network Contributor' role to the security group at the 'Production' management group scope. — Assigning the 'Network Contributor' role at the 'Production' management group scope is the most efficient method because management groups provide a hierarchical scope that automatically inherits role assignments to all child subscriptions, including any new subscriptions added in the future. This eliminates the need for manual assignments per subscription and ensures consistent access control across the entire management group hierarchy.
What should I do if I get this AZ-900 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 →
Same concept, more angles
1 more ways this is tested on AZ-900
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company has multiple Azure subscriptions organized under a management group hierarchy. They need to assign the 'Contributor' role to a security team for all subscriptions under the 'Production' management group. They also want new subscriptions added later to automatically inherit this role assignment. What should they do?
medium- A.Assign the role at the tenant root management group level
- ✓ B.Assign the role at the management group level
- C.Assign the role at each subscription individually
- D.Use an Azure Blueprint to assign the role
Why B: Assigning the 'Contributor' role at the management group level ensures that all subscriptions under that management group inherit the role assignment. When new subscriptions are added to the 'Production' management group, they automatically inherit the role assignment because Azure RBAC supports inheritance down the management group hierarchy. This meets both requirements: immediate coverage and automatic inheritance for future subscriptions.
Last reviewed: Jun 11, 2026
This AZ-900 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-900 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.