Compute resilience
CoreAzure Availability Zones
Physically separate datacenter groups within supported regions.
Key points
- A zonal design requires redundant instances; placing one instance in a zone does not create application redundancy.
- Redundant instances across zones can tolerate a zonal facility failure.
- Dependent disks, IPs, and load-balancing resources need compatible zonal design.
Best-known use cases
- Place redundant VMs across zone boundaries.
- Align zonal frontends and disks with a resilient deployment.
What candidates often confuse it with
- Availability Zone vs region: isolated datacenter group within one region vs separate geographic Azure area.
- Availability Zone vs availability set: zonal failure boundary vs fault and update domains within a datacenter boundary.
Key takeaway
Use multiple zone-aligned instances when the required failure boundary is an availability zone.
Related services
- Availability sets
- Azure Virtual Machine Scale Sets
Relevant exam tasks
- D3.2.S6 — Deploy virtual machines to availability zones and availability sets
- D3.2.S7 — Deploy and configure an Azure Virtual Machine Scale Sets