AZ-900 Exam Cram: Core Azure Architectural Components

This guide focuses on the foundational physical and logical structures of Microsoft Azure. Understanding the hierarchy and redundancy models is essential for passing the AZ-900 examination.

Topic Weighting

[!IMPORTANT] This topic falls under "Describe Azure Architecture and Services," which accounts for 35–40% of the total exam marks. It is the highest-weighted functional group in the curriculum.

Key Concepts Summary

1. Physical Infrastructure

• Datacenters: The smallest unit; physical buildings containing thousands of servers.
• Availability Zones (AZs): Unique physical locations within a region. Each AZ is made up of one or more datacenters with independent power, cooling, and networking.
• Regions: A set of datacenters deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network.
• Region Pairs: Each Azure region is paired with another region within the same geography (at least 300 miles away) to protect against regional disasters.
• Sovereign Regions: Specialized instances for compliance (e.g., Azure Government for US federal/state/local/tribal entities and Azure China operated by 21Vianet).

2. Management Hierarchy

Azure uses a hierarchical structure to organize resources for billing, access, and compliance.

Visual Anchors

The Azure Physical Relationship

This diagram represents how physical components are nested to provide High Availability (HA).

\begin{tikzpicture}[node distance=2cm] \draw[thick, fill=blue!10] (0,0) rectangle (8,6) node[pos=0.9, left] {\textbf{Azure Region}}; \draw[thick, fill=blue!20] (0.5,0.5) rectangle (3.5,5) node[pos=0.9, left] {\textbf{AZ 1}}; \draw[thick, fill=blue!20] (4.5,0.5) rectangle (7.5,5) node[pos=0.9, left] {\textbf{AZ 2}}; \draw[thick, fill=white] (1,1) rectangle (3,2.5) node[midway] {Datacenter A}; \draw[thick, fill=white] (1,3) rectangle (3,4.5) node[midway] {Datacenter B}; \draw[thick, fill=white] (5,2) rectangle (7,4) node[midway] {Datacenter C}; \end{tikzpicture}

Common Pitfalls

• Resource Group Movement: You can move resources between resource groups, but they can only belong to one group at a time.
• Location Constraints: A Resource Group can contain resources from different regions than the group itself. The group location only specifies where metadata is stored.
• AZ Availability: Not all Azure regions support Availability Zones.
• Region Pairs: You cannot choose your region pair; they are pre-defined by Microsoft.

Mnemonics / Memory Triggers

• The Management Sandwich (Top to Bottom): Many Smart Rabbits Run.
  • Management Groups
  • Subscriptions
  • Resource Groups
  • Resources
• 300 Miles: Think of a "3-0-0" rule for Region Pairs — the minimum distance to ensure that a local disaster (flood/fire) doesn't hit both data centers.

Formula / Equation Sheet

Practice Set

Quick-Fire Questions

1. Which Azure component provides the highest level of scope for managing compliance and policy across multiple subscriptions?
   • Answer: Management Groups.
2. True or False: A resource group can contain resources from multiple different Azure regions.
   • Answer: True.
3. What is the minimum distance recommended between Azure Region Pairs?
   • Answer: 300 miles.
4. Which component represents a physical building containing cooled racks of servers?
   • Answer: Datacenter.
5. If you want to ensure your application survives a complete Datacenter failure but remains in the same Region, what should you use?
   • Answer: Availability Zones (AZs).

Fact Recall Blanks

• Azure __________ are boundaries often defined by country borders to meet data residency requirements. (Geographies)
• A __________ is a logical container for resources deployed on Azure. (Resource Group)
• The __________ is the primary unit for billing in Azure. (Subscription)
• Azure __________ are specialized regions for entities like the US Department of Defense. (Sovereign Regions / Government Regions)