Azure AZ-900 Core Architecture Guide

This lesson is about Azure’s structural hierarchy. AZ-900 wants you to know where workloads live, how Azure organizes them, and how governance scope climbs from resources up to management groups.

Resource group: Logical container for Azure resources that share a lifecycle or management context.

Subscription: Azure billing and management boundary that groups resources and helps organize access and cost.

Hierarchy map

    flowchart TD
	  MG["Management group"] --> SUB["Subscription"]
	  SUB --> RG["Resource group"]
	  RG --> RES["Resource"]

The exam often turns on these boundaries:

• resource group is a lifecycle and organization container
• subscription is a billing and management boundary
• management group sits above subscriptions for broader governance

Geographic components

What each geography term is really answering

Common traps

• treating a resource group like a billing boundary
• treating a subscription like a folder instead of a billing and management scope
• confusing availability zones with region pairs
• forgetting that sovereign regions solve compliance-boundary questions, not ordinary performance questions

Decision order that usually wins

1. Decide whether the stem is about hierarchy, geography, or resilience scope.
2. Keep resource groups, subscriptions, and management groups in separate lanes.
3. Separate region, zone, region pair, and sovereign-region meanings.
4. Use the smallest scope term that actually matches the requirement.
5. Avoid mixing governance boundaries with geography boundaries.

Quiz