Study guide

9.1 Compute High Availability: Availability Sets & Availability Zones

Exam AZ-305: Designing Microsoft Azure Infrastructure Solutions Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Orientation

1.1 AZ-305 Current Exam Facts & Format 1.2 Candidate Profile, Prerequisites & the AZ-104 Requirement 1.3 Skills Outline, Domain Weights & How to Use This Guide

2 Chapter 2: Logging, Monitoring & Diagnostics Design

2.1 Logging Solution Design 2.2 Log Routing Design 2.3 Azure Monitor Metrics & Alerting Design 2.4 Application Insights & Diagnostic Monitoring Design

3 Chapter 3: Authentication & Authorization Design

3.1 Authentication Solution Design 3.2 Identity Management Design 3.3 Authorization for Azure Resources 3.4 Authorization for On-Premises Resources 3.5 Secrets, Certificates & Key Management Design

4 Chapter 4: Governance, Compliance & Identity Governance Design

4.1 Management Group & Subscription Hierarchy Design 4.2 Resource Group Organization & Tagging Strategy Design 4.3 Compliance Management Design 4.4 Identity Governance Design

5 Chapter 5: Relational Data Storage Design

5.1 Relational Data Storage Selection 5.2 Database Service & Compute Tier Design 5.3 Database Scalability Design 5.4 Relational Data Protection Design

6 Chapter 6: Semi-Structured & Unstructured Data Storage Design

6.1 Semi-Structured Data Storage Design 6.2 Unstructured Data Storage Design 6.3 Storage Tier & Cost-Performance Trade-off Design 6.4 Unstructured Data Protection & Durability Design

7 Chapter 7: Data Integration & Analytics Design

7.1 Data Integration Pipeline Design 7.2 Event-Based & Real-Time Data Integration Design 7.3 Data Analytics Platform Design

8 Chapter 8: Backup & Disaster Recovery Design

8.1 Recovery Objectives Design: Calculating and Meeting RTO/RPO 8.2 Azure Site Recovery Architecture for Hybrid Workloads 8.3 Compute Backup & Recovery Design 8.4 Database Backup & Recovery Design 8.5 Unstructured Data Backup & Recovery Design

9 Chapter 9: High Availability Design

9.1 Compute High Availability: Availability Sets & Availability Zones 9.2 Compute High Availability: Load Balancing & VM Scale Set Design 9.3 Relational Data High Availability Design 9.4 Semi-Structured & Unstructured Data High Availability Design

10 Chapter 10: Compute Solution Design

10.1 Compute Requirements Analysis & Virtual Machine-Based Solution Design 10.2 Container-Based Solution Design (AKS, Container Apps, Azure Container Instances) 10.3 Serverless-Based Solution Design (Azure Functions, Logic Apps) 10.4 Batch Processing Solution Design (Azure Batch, HPC Workloads)

11 Chapter 11: Application Architecture Design

11.1 Messaging Architecture Design (Service Bus, Queue Storage) 11.2 Event-Driven Architecture Design (Event Grid, Event Hub) 11.3 API Integration & Application Caching Design (API Management, Azure Cache for Redis, CDN) 11.4 Application Configuration Management & Automated Deployment Design (App Configuration, DevOps Pipelines, Deployment Slots)

12 Chapter 12: Migration Design

12.1 Migration Assessment: Cloud Adoption Framework & On-Premises Evaluation 12.2 IaaS & PaaS Workload Migration Design 12.3 Database Migration Design (Data Migration Service, Database Migration Assistant) 12.4 Unstructured Data Migration Design (AzCopy, Data Box, Storage Migration Service)

13 Chapter 13: Network Solution Design

13.1 Internet Connectivity Design 13.2 Hybrid Connectivity Design 13.3 Network Security Optimization Design 13.4 Network Performance Optimization & Load-Balancing/Routing Design

14 Chapter 14: Final Review, Exam Strategy & Career Path

14.1 Cross-Domain Scenario Practice: Combining Identity, Data, Continuity & Infrastructure Decisions 14.2 Common AZ-305 Decision Traps 14.3 Final Study Plan & Practice Assessment Strategy 14.4 After AZ-305: Retake Policy, Renewal & Career Path

9.1 Compute High Availability: Availability Sets & Availability Zones

Key Takeaways Explain This Topic AI

An Availability Set spreads VMs across up to 3 fault domains (shared power/network switch) and up to 20 update domains (planned-maintenance groups); 2+ VMs in a set meet the 99.95% VM SLA.

Availability Zones are physically separate datacenter groups within a region (3 zones in every AZ-enabled region), connected by a sub-2ms network and typically within ~100 km of each other.

Deploying 2+ VM instances across 2 or more Availability Zones raises the SLA to 99.99% — a single VM pinned to one zone gets no extra protection from the zone feature by itself.

Availability Sets are a regional (non-AZ) fallback: use them only in regions that don't yet support Availability Zones, since zones give a materially better SLA at similar cost.

A VM is a zonal resource — you must explicitly deploy separate VM instances into different zones yourself; Azure does not automatically spread a single VM's redundancy across zones.

Last updated: July 2026

Why This Topic Matters

Domain 3 (Design business continuity solutions, 15-20% of AZ-305) devotes an entire official subgroup to high availability , and compute HA is the subgroup's first and most heavily tested cluster. Nearly every AZ-305 scenario question about VM resilience reduces to one design decision: Availability Set or Availability Zone — and how many instances, in how many zones? Getting the underlying mechanics wrong (fault domain vs. update domain, which SLA applies, whether a single VM is protected) is one of the most common ways candidates lose points on otherwise-straightforward infrastructure questions.

Core Terms and Rules

An Availability Set is a logical grouping of VMs that Azure spreads across isolated physical infrastructure within a single datacenter. Each set has two independent dimensions:

Fault domains (FDs) — groups of VMs that share a common power source and network switch. Each Availability Set can have up to 3 fault domains (exact max varies slightly by region). Placing VMs across fault domains means a rack-level power or network failure doesn't take down every instance at once. VMs are also aligned to disk fault domains (2 or 3 per region, depending on the region) so a VM's attached managed disks fail over consistently with its compute.

Update domains (UDs) — groups of VMs and underlying hardware that Azure can reboot together during planned maintenance. Each Availability Set can have up to 20 update domains . Azure only restarts one update domain at a time, and a restarted update domain gets 30 minutes to recover before the next one starts. If you have more VMs than update domains (e.g., 7 VMs in a 5-UD set), Azure wraps around — the 6th VM shares a UD with the 1st, the 7th with the 2nd, and so on.

Using 2 or more VMs in an Availability Set is what qualifies you for the 99.95% Azure SLA for VM availability — a single VM in a set (or with no redundancy construct at all, just on premium SSD) does not reach that bar.

An Availability Zone is a physically separate group of one or more datacenters within an Azure region, each with its own independent power, cooling, and network. Every region that supports zones has 3 Availability Zones . Zones are usually within about 100 km of each other , and Microsoft targets less than 2 milliseconds round-trip latency on the inter-zone network — close enough that most workloads see no meaningful performance penalty from spreading across zones, but far enough apart that a single flood, fire, or power-grid event is very unlikely to take out more than one zone.

Critically, a VM is what Microsoft calls a zonal resource : when you deploy a VM into a zone, that one instance lives in that one zone only. Azure does not automatically replicate a single VM's redundancy across zones for you. To get zone protection you must deploy separate VM instances into 2 or more different zones yourself (typically behind a Standard Load Balancer) — this combination is called being zone-resilient . Do that, and your VM tier qualifies for the 99.99% SLA , the highest availability tier Microsoft publishes for IaaS compute.

Comparing the Two Options

Attribute Availability Set Availability Zones

Fault isolation Up to 3 fault domains (rack-level: power + network switch) Up to 3 zones per region (datacenter-level: independent power, cooling, network)

Planned maintenance Up to 20 update domains, one at a time, 30-min recovery window Azure sequences updates zone-by-zone; workload must already span zones to benefit

  • SLA (2+ instances) 99.95% 99.99%
  • VM-to-VM latency Lower (physically closer) Slightly higher (~2 ms target, still low)
  • Protects against Rack/power/network/host failure Entire datacenter loss (fire, flood, power-grid failure)

Cost No extra charge for the construct itself No extra charge for the construct itself; cross-zone data transfer is also free

  • Region requirement Works in any region Only in regions with Availability Zone support
  • Exam Scenarios

Scenario 1: A company deploys a two-tier application to East US 2 (an Availability-Zone region) and needs the highest published Azure SLA for its web tier VMs at no extra licensing cost. Design decision : deploy at least 2 VM instances, one per zone, across 2 or 3 zones, behind a Standard Load Balancer — this reaches 99.99%, not 99.95%.

Scenario 2: The same company must also deploy to a region that does not support Availability Zones. Design decision : fall back to an Availability Set with 2+ VMs spread across the maximum fault domains — this is the only way to reach an SLA above the single-instance baseline in that region.

Scenario 3: A candidate deploys a single VM into "Zone 1" and assumes it is now protected against a regional datacenter outage. Trap : a lone zonal VM is exactly as exposed as before — zone resiliency requires multiple instances across multiple zones, not just placement in a zone.

Takeaways

Fault domains isolate shared hardware (power/network); update domains isolate planned maintenance timing — they solve different problems and both apply only within Availability Sets.

Memorize the SLA pairing: 99.95% for 2+ VMs in an Availability Set (or across fault domains generally), 99.99% for 2+ VMs across Availability Zones.

Availability Zones are the default recommendation whenever the target region supports them; reach for Availability Sets only as the regional fallback.

A single VM instance, regardless of which construct it sits in, never independently reaches the multi-instance SLA — AZ-305 scenario questions frequently test whether you notice a "single VM" detail that breaks an otherwise-plausible answer.