Management Groups, Resource Locks and Governance Hierarchy
This topic covers management groups, subscription hierarchy, governance inheritance, lock levels, policy effects, resource organization, and operational boundaries.
How to study for AZ-104
Treat each AZ-104 item as an admin workflow: identify the scope, resource type, access boundary, deployment method, monitoring signal, or recovery requirement.
Core concepts
Concept 1
Management Groups, Resource Locks and Governance Hierarchy questions reward operational Azure administration judgment rather than simple service-name recall.
Exam cue: Identify the Azure scope: tenant, management group, subscription, resource group, resource, subnet, or identity.
Concept 2
The best answer identifies the scope, resource type, access path, deployment method, monitoring signal, and recovery requirement.
Exam cue: Match the tool to the administrative task: manage access, deploy, secure, monitor, back up, or troubleshoot.
Concept 3
Eliminate answers that confuse RBAC with policy, public access with private access, monitoring with backup, or templates with manual changes.
Exam cue: Prefer least privilege, repeatable deployment, protected storage, private networking, and validated recovery.
Risk pitfalls and guardrails
Using Azure Policy when the question asks who is allowed to perform an action.
Guardrail: Avoid answers that confuse RBAC with Policy, tags with network controls, dashboards with backup, or public exposure with secure private access.
Opening public access when private endpoints, service endpoints, or NSGs meet the requirement.
Guardrail: Avoid answers that confuse RBAC with Policy, tags with network controls, dashboards with backup, or public exposure with secure private access.
Assuming backup exists before checking vault, policy, retention, and restore validation.
Guardrail: Avoid answers that confuse RBAC with Policy, tags with network controls, dashboards with backup, or public exposure with secure private access.
Memory anchors
Management Group
A management group organizes subscriptions for governance at scale.
Hierarchy
Azure management hierarchy commonly flows from management groups to subscriptions to resource groups to resources.
Inheritance
Assignments at higher scopes can affect child scopes.
CanNotDelete Lock
A CanNotDelete lock prevents deletion but can allow modification.
ReadOnly Lock
A ReadOnly lock prevents changes and can affect control plane operations.
Policy Effect
Policy effects can audit, deny, modify, append, or deploy related resources.
Management Boundary
A management boundary limits where administrative control applies.
Resource Move
Moving resources can be constrained by resource type, dependencies, locks, and permissions.
Naming Standard
Naming standards improve organization, search, automation, and operations.
Governance Review
Governance review checks compliance, cost, ownership, and risk controls.
Checkpoint rule
Do the check-up only after you can summarize each concept in one sentence and identify one dangerous pitfall from memory.
Knowledge Check (after reading)
Short check-up to confirm understanding of this module.
Check-up Questions
An enterprise has 80 subscriptions and wants one policy assignment to govern all production subscriptions without affecting development subscriptions. Which hierarchy is best?
A role is assigned at a management group that contains five subscriptions. What is the normal effect?
Answer all questions to submit.
Next step personalized recommendations
Continue learning
Move forward only after this module is stable.
What is Pass Harbor?
Completely free exam prep for 317 U.S. exams.
- Practice questions
- Flashcards
- Study guides
- Mock exams
- No registration
- No paywall
- Start instantly
“No more expensive exam prep. Quality study tools should be accessible to everyone.”