Azure Fundamentals AZ-900 Sign in Try 10 free questions

Azure regions, availability zones and region pairs

The geography vocabulary the AZ-900 tests constantly — regions, zones, region pairs, sovereign clouds and where your data legally lives — 2026 edition.

Here are 7 typical regions-and-zones questions in the exam's own style — free, each answer explained, no sign-up.

Straight to the 7 free questions ↓

Azure’s geographic model is pure AZ-900 territory: no architecture puzzles, just a small stack of terms that the exam tests over and over. Learn four words in the right order — Geography, Region, Availability Zone, Region Pair — and a whole band of questions turns into recognition. The diagram above is the entire model on one canvas; read it left to right and keep it in your head.

The size ladder: geography → region → zone

Start from the biggest unit and work down. A geography is a discrete market — often a country or a continent, such as Europe — that preserves data-residency and compliance boundaries. Inside a geography sit one or more regions; a region is the actual location you choose when you deploy, like West Europe or East US, and it is a set of datacenters grouped within a latency-defined perimeter. Inside a region sit availability zones: each zone is a physically separate datacenter with its own power, cooling and networking. Get the nesting right and most distractors fall away — a resource group is not a place, and a single building is not a whole region.

What each layer protects against

The exam’s favourite move is to test which failure a given layer survives.

  • Availability zones protect against a single datacenter failing inside a region. Spread a workload across zones and one zone can go dark without taking you down — but every zone still lives in that one region, so a region-wide disaster is out of their reach.
  • Region pairs cover exactly that gap. Azure automatically pairs most regions with a second region in the same geography for geo-redundancy and disaster recovery, and platform updates roll across the pair sequentially so both regions are never updated at once. Because the pair stays in one geography, your data can survive a regional disaster and stay inside one legal jurisdiction.

Zonal, zone-redundant, regional

When you place a resource, it relates to zones in one of three ways. Zonal pins it to a single zone you pick. Zone-redundant spreads it across several zones automatically, so one zone failing does not stop it. Regional (non-zonal) places it in the region with no zone guarantee. Add the paired region and you get geo-redundancy — a separate axis from zone redundancy. Keeping these three straight is often a single easy point.

Sovereign clouds and choosing a region

For national-regulation and sovereignty needs, Microsoft runs separate, isolated instances of Azure — sovereign or government clouds such as Azure Government and Azure operated by 21Vianet in China. They are physically and logically distinct from the commercial cloud, not a setting inside it.

Finally, choosing a region is a four-way trade-off: proximity and latency to your users, data-residency law, which services are available there (not every service ships in every region), and price. Treat a legal residency requirement as a hard gate that narrows the eligible geography first, then optimize the rest inside what remains. The real exam mixes multiple-choice, true/false and drag-and-drop; the seven samples above are standard multiple-choice, and every explanation carries a “Why not the others” so the wrong options teach as much as the right one.

A nested diagram of Azure's geographic model drawn left to right. On the left, a large outer box labelled Geography (a regulatory and data-residency boundary such as Europe) contains two regions. The first region is a rounded box holding three separate stacked datacenter tiles labelled Availability Zone 1, Availability Zone 2 and Availability Zone 3, each with its own independent power, cooling and networking, showing that zones are physically separate datacenters inside one region. A curved arrow labelled Region Pair links this first region to a second region inside the same geography, marked for geo-redundant replication and sequential platform updates so both regions of a pair are never updated at once. A caption reads: zones protect against a datacenter failure inside a region; region pairs protect against a whole-region disaster; the geography keeps both regions under the same data-residency laws.

7 free AZ-900 practice questions

Answers and explanations — no email wall
AZ-900 Question 1 of 7

In Microsoft Azure's geographic model, what is a 'region'?

Answer: A — A group of one or more datacenters deployed within a latency-defined perimeter, presented to you as a single location such as West Europe or East US.

A region is the location you actually pick when you deploy — a set of datacenters close enough together to sit inside a defined latency envelope, surfaced under one name like West Europe. Why not the others: a single datacenter building is closer to an availability zone, not a whole region. The broad market boundary (Europe, United States) describes a geography, which contains regions. A container that holds and bills resources is a resource group, an organizational construct, not a physical place. Pro tip: order the units by size — Geography contains Regions, a Region contains Availability Zones. If a question names 'West Europe', that is a region.

AZ-900 Question 2 of 7

A colleague claims that because their virtual machines run in an availability zone, they are protected from a natural disaster that takes out the entire Azure region. Why is that reasoning wrong?

Answer: A — Availability zones are physically separate datacenters within the same region, so they guard against one datacenter failing — not against the whole region going down.

Each availability zone is a physically separate datacenter — its own power, cooling and networking — inside a single region. Spreading across zones survives one datacenter (one zone) failing, but every zone still sits in that one region, so a region-wide disaster can take them all. Why not the others: zones are real physical isolation, not merely a billing label. Zones live inside one region; they do not span regions. Zones do not copy data to another geography on their own — that is what region pairs and geo-redundant storage are for. Pro tip: zone = protection inside a region; surviving the loss of a whole region needs a second region (a region pair).

AZ-900 Question 3 of 7

Your compliance team requires that a copy of critical data survives a disaster affecting an entire Azure region, and they want the replica to stay within the same regulatory boundary. Which Azure concept is designed for exactly this?

Answer: A — Region pairs — each region is paired with a second region in the same geography for geo-redundancy and disaster recovery.

Azure automatically pairs most regions with another region in the same geography. The pairing gives you a distant replica for region-level disaster recovery while keeping data inside the same regulatory boundary, and platform updates roll across the two regions sequentially so both are never taken down at once. Why not the others: availability zones only protect against a datacenter failure inside the one region, not the loss of that whole region. A resource group is an organizational container — it offers no geographic redundancy. Azure Policy governs what is allowed to exist; a deny-delete rule does not create a surviving copy anywhere. Pro tip: 'survive a whole region' plus 'same regulatory area' is the fingerprint of region pairs.

AZ-900 Question 4 of 7

In Azure's model, what is a 'geography', and why does it matter for a customer with strict data-residency requirements?

Answer: A — A discrete market — often a country or continent, such as Europe — that contains one or more regions and preserves data-residency and compliance boundaries.

A geography is the top of Azure's location hierarchy: a discrete market, typically aligned to a country or continent, that groups regions and honours data-residency and compliance boundaries. Because a region's paired region normally lives in the same geography, a customer's data can stay within one legal jurisdiction even during failover. Why not the others: an availability zone is a datacenter inside a region, far smaller than a geography. A geography is a market boundary, not a measured distance between datacenters. It is not a pricing tier — prices vary by region, but a geography is a compliance construct. Pro tip: think Geography = legal boundary, Region = where you deploy, Zone = which datacenter.

AZ-900 Question 5 of 7

A government agency must run workloads in a cloud environment that is physically and logically isolated from the standard commercial Azure cloud to meet national regulatory rules. What is Microsoft's term for such an offering?

Answer: A — A sovereign or government cloud, such as Azure Government or Azure operated by 21Vianet in China — a separate, isolated instance of Azure.

For customers with sovereignty or national-regulation requirements, Microsoft runs separate, isolated instances of Azure — sovereign or government clouds such as Azure Government and Azure operated by 21Vianet in China. They are physically and logically distinct from the commercial cloud. Why not the others: an availability zone is a datacenter inside an ordinary commercial region, not an isolated cloud. A region pair is a disaster-recovery relationship between two commercial regions, not an isolation boundary. A management group only organizes subscriptions for governance; it does not create a separate cloud instance. Pro tip: 'physically isolated / sovereign / government' points to a separate cloud, not a setting inside the commercial one.

AZ-900 Question 6 of 7

When you deploy a resource in Azure, which description matches a 'zone-redundant' resource rather than a 'zonal' or a purely 'regional' one?

Answer: A — The resource is spread automatically across multiple availability zones in the region, so it stays available if one zone fails.

Azure resources relate to zones in three ways. Zone-redundant means Azure automatically distributes the resource across several zones, so a single zone failing does not take it down. Why not the others: a resource pinned to one zone you choose is zonal — no cross-zone protection. A resource with no zone awareness is regional (non-zonal), placed in the region without zone guarantees. Replication to the paired region is region-level (geo) redundancy, a different axis from zone redundancy. Pro tip: zonal = one chosen zone, zone-redundant = spread across zones, regional/non-zonal = no zone guarantee; add the paired region for geo-redundancy.

AZ-900 Question 7 of 7

A retailer's customers are mostly in Brazil, and a local law requires their personal data to stay inside the country. Which factor should weigh most heavily when the team chooses which Azure region to deploy into?

Answer: A — Data-residency law — pick a region inside the geography that keeps the data within the required jurisdiction, then weigh latency, service availability and price.

Region choice balances four factors — proximity/latency to users, data-residency and compliance law, which services are available in the region, and price — but a legal residency requirement is a hard constraint that comes first: it narrows the eligible geography before the others apply. Why not the others: chasing the globally cheapest region can put data outside the required jurisdiction and add latency. Zone count is one input but cannot override a residency law. 'Newest region' is not a rule — not every service is offered in every region, and age does not guarantee availability. Pro tip: treat legal residency as a gate, then optimize latency, service availability and price within the regions that pass it.

That is exactly how every question in the course works — answer, explanation, why-not. The real set continues in the practice player: 10 free questions, no sign-up.

Continue with the 10 free questions →

Those 7 questions were the start.

The exam does not test whether you recognise a term — it tests whether you can rule out three plausible answers under time pressure. That is what the explanations above are for, and there are 300 more questions built exactly like them.

Collecting questions yourself

  • Scattered across forums, of unknown age
  • Answer keys without reasoning
  • No idea which domain you are weak in

Practising with a system

  • 300 questions in 6 full tests, AZ-900 (2026)
  • Every option explained — including the wrong ones
  • Readiness per exam domain, and drills for your weakest
Start free — 10 questions

Straight into the player. No account, no email.

Frequently asked questions

What is the difference between a region, an availability zone and a region pair?
They are three sizes on the same map. A region is the location you deploy into (like West Europe) — a cluster of datacenters within a latency envelope. An availability zone is one physically separate datacenter inside that region, with its own power, cooling and networking, so spreading across zones survives a single datacenter failure. A region pair is two regions linked for geo-redundancy: it protects against an entire region going down and, because the pair sits in the same geography, keeps data within one regulatory boundary. Zones handle a datacenter outage; region pairs handle a whole-region disaster.
Are all Azure services available in every region?
No. Service and feature availability varies by region, and not every region even offers availability zones. This is exactly why region choice on the AZ-900 is framed as a trade-off — you weigh proximity and latency, data-residency law, which services you actually need in that region, and price, rather than assuming any region can do everything.
Are these real AZ-900 exam questions?
No. These are our own questions, written in the style and difficulty of the AZ-900 — never copied from any question bank or the live exam. Reproducing real exam items breaks Microsoft's certification agreement and can cost a candidate their certification, and a crammed answer teaches you nothing about the version you have not seen. The goal here is to learn the vocabulary cold, not to guess at leaked items.

Updated for AZ-900 (July 2026). The sample questions above are our own work in the style of the exam — not real exam items. The exam itself is set and marked by the certification body.