AZ-900 Describe Azure management and governance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Management groups

  Why this is correct

  Management groups are the correct answer because they are Azure's enterprise-grade construct for organizing subscriptions into a hierarchy. A management group can contain one or more subscriptions, and management groups themselves can be nested up to six levels deep. This hierarchy enables you to apply Azure Policy and role-based access control (RBAC) at a parent scope, and all child subscriptions and management groups automatically inherit those assignments. Management groups are the only option in this list that explicitly forms a subscription-level hierarchy for policy and billing governance.

• ✗

  Resource groups

  Why it's wrong here

  Resource groups are incorrect because they are logical containers that live within a single subscription. They group related resources such as VMs, databases, and storage accounts, but they cannot contain or organize subscriptions. Since a resource group's scope is confined to the subscription it belongs to, it cannot serve as a mechanism for building a multi-subscription hierarchy or for applying policy across multiple subscriptions at once.

  When this WOULD be correct

  A company needs to organize resources (e.g., VMs, databases) within a single subscription for management and billing purposes. They should create resource groups to logically group related resources.

• ✗

  Policies

  Why it's wrong here

  Azure Policy is incorrect because it is a service for creating, assigning, and managing compliance rules, not a container for organizing subscriptions. Policy definitions can be assigned to a management group, subscription, or even a resource group, but the policy itself is the rule being enforced, not the hierarchy that groups subscriptions. Without a management group or similar scope, a policy has no upper-level container to tie subscriptions together; policies are applied at a scope, they do not create the scope.

  When this WOULD be correct

  A question asking how to enforce tagging rules or restrict resource locations across multiple subscriptions would have policies as the correct answer, as they are applied at management group, subscription, or resource group scope.

• ✗

  Subscriptions

  Why it's wrong here

  Subscriptions are incorrect because each subscription is a flat billing and management boundary that contains resource groups and resources. Subscriptions cannot be nested inside other subscriptions, so they cannot form a hierarchy by themselves. To create a hierarchy, subscriptions must be placed under a management group, which then allows policies and RBAC to be inherited from the parent. Therefore, subscriptions are the units being organized, not the organizational structure itself.

  When this WOULD be correct

  A company needs to create separate billing and access boundaries for different departments, each with its own set of resources. The question would be: 'What is the fundamental unit of management and billing in Azure that contains resources?'

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-900 exam frequently reuses these exact scenarios with slightly different constraints.

Analysis generated from the official AZ-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”