Study guide

5.4 Availability Zones, Sets, and VM Scale Sets

AZ-104 Microsoft Azure Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Orientation and Microsoft Learn Source Control

1.1 Current AZ-104 Exam Facts 1.2 Administrator Role and Candidate Profile 1.3 Skills Outline and Weighted Study Map 1.4 Exam Duration, Question Types, Labs, and Learn Access 1.5 Scoring, Retakes, Renewal, and Account Choice 1.6 Using the Practice Bank, Labs, and Error Log

2 Chapter 2: Identity, RBAC, and Governance Foundations

2.1 Microsoft Entra Users, Groups, and Properties 2.2 Licenses, External Users, and SSPR 2.3 Azure RBAC Built-In Roles and Scopes 2.4 Role Assignment Interpretation and Deny Effects 2.5 Management Groups, Subscriptions, and Resource Groups 2.6 Azure Policy, Locks, Tags, and Governance Controls 2.7 Identity and Governance Case Lab

3 Chapter 3: Subscriptions, Policy, Costs, and Resource Organization

3.1 Subscription Design and Management Groups 3.2 Resource Groups, Lifecycle, and Move Operations 3.3 Tagging Strategy and Cost Allocation 3.4 Budgets, Alerts, and Azure Advisor Cost Recommendations 3.5 Policy, Initiative, Assignment, and Remediation 3.6 Resource Locks, RBAC, Policy, and Tags Combined 3.7 Governance and Cost Case Lab

4 Chapter 4: Storage Accounts, Access, and Data Protection

4.1 Storage Account Design, Redundancy, and Encryption 4.2 Storage Firewalls, Private Access, and Network Rules 4.3 SAS Tokens, Stored Access Policies, and Access Keys 4.4 Identity-Based Access for Azure Files 4.5 Blob Tiers, Lifecycle, Soft Delete, and Versioning 4.6 Azure Files, Snapshots, File Sync, and AzCopy 4.7 Storage Case Lab

5 Chapter 5: Compute, Virtual Machines, Scale Sets, and Bicep

5.1 ARM Templates, Bicep, and Deployment Workflow 5.2 Create, Configure, and Manage Virtual Machines 5.3 VM Disks, Sizes, Encryption, and Host Settings 5.4 Availability Zones, Sets, and VM Scale Sets 5.5 Move VMs Across Resource Groups, Subscriptions, and Regions 5.6 Backup, Restore, and Operational Maintenance for VMs 5.7 VM Compute Case Lab

6 Chapter 6: Containers, App Service, and Platform Compute

6.1 Azure Container Registry and Image Workflow 6.2 Azure Container Instances and Container Apps 6.3 Container Sizing, Scaling, and Environment Choices 6.4 App Service Plan, Apps, and Runtime Configuration 6.5 App Service Certificates, TLS, Custom Domains, and Networking 6.6 App Service Backups, Deployment Slots, and Scaling 6.7 Platform Compute Case Lab

7 Chapter 7: Virtual Networking, Routing, and Secure Access

7.1 VNet, Subnet, and Address Space Design 7.2 VNet Peering and Cross-Network Connectivity 7.3 Public IP Addresses and NAT Patterns 7.4 User-Defined Routes and Effective Routes 7.5 NSGs, ASGs, and Effective Security Rules 7.6 Azure Bastion, Service Endpoints, and Private Endpoints 7.7 Secure Networking Case Lab

8 Chapter 8: Name Resolution, Load Balancing, and Connectivity Troubleshooting

8.1 Azure DNS, Private DNS, and Name Resolution 8.2 Public and Internal Load Balancer Design 8.3 Backend Pools, Health Probes, and Load Balancing Rules 8.4 Load Balancing Troubleshooting Workflow 8.5 Network Watcher: IP Flow, Next Hop, and Connection Troubleshoot 8.6 Hybrid Connectivity, VPN, ExpressRoute, and DNS Considerations 8.7 Connectivity Troubleshooting Case Lab

9 Chapter 9: Monitoring, Alerting, Backup, and Site Recovery

9.1 Azure Monitor Metrics, Logs, and Diagnostic Settings 9.2 Log Analytics, KQL, and Operational Queries 9.3 Alert Rules, Action Groups, and Alert Processing Rules 9.4 VM, Storage, and Network Insights 9.5 Recovery Services Vault, Backup Vault, and Backup Policies 9.6 Azure Site Recovery, Failover, and Replication 9.7 Monitoring and Recovery Case Lab

10 Chapter 10: AZ-104 Integration and Troubleshooting Case Labs

10.1 Domain Weight Triage and Study Prioritization 10.2 Identity, Storage, and Compute Integrated Cases 10.3 Networking, Monitoring, and Security Integrated Cases 10.4 Migration, Move, Backup, and Recovery Cases 10.5 Permissions, Network, and Storage Troubleshooting Chain 10.6 Microsoft Learn Lookup Strategy Under Time Pressure 10.7 Full-Domain Case Lab

11 Chapter 11: Final Review, Exam Experience, Renewal, and Career Path

11.1 Final Two-Week Study Plan 11.2 Hands-On Lab Checklist and Command Review 11.3 Exam Day, Pearson VUE, Breaks, and Learn Access 11.4 Retake Plan, Score Report, and Weak-Domain Repair 11.5 Renewal Assessment and Annual Certification Maintenance 11.6 After AZ-104: AZ-305, AZ-400, SC-500, and Job Paths

5.4 Availability Zones, Sets, and VM Scale Sets

Key Takeaways Explain This Topic AI

Availability zones protect against datacenter-level failure within a region, while availability sets spread VMs across fault and update domains inside a datacenter placement model.

VM Scale Sets provide a managed group of VM instances with uniform or flexible orchestration, autoscale, load balancing, and rolling upgrade patterns.

High availability design must include compute placement, load balancing, health probes, application state, data tier resilience, and operational update strategy.

Troubleshooting scale sets often involves instance health, autoscale rules, image or extension failures, quota, load balancer backend membership, and upgrade policy.

Last updated: May 2026

Availability Building Blocks

A single VM has planned and unplanned downtime risk. Azure provides several compute placement options to reduce that risk, but each solves a different problem. Availability zones are physically separate datacenter locations inside a supported region. Zone-redundant designs can survive a zone failure if the application, network path, and data tier are also resilient. Availability sets spread VMs across fault domains and update domains to reduce correlated host and maintenance impact. VM Scale Sets manage multiple VM instances as a group and are commonly used for stateless application tiers.

Option Protects against Best fit Key limitation

Availability zone Datacenter or zone failure Regional HA for supported services Not every region or SKU supports every zone

Availability set Host rack and planned update grouping Legacy or non-zonal multi-VM apps Must be chosen at VM creation

  • VM Scale Set Instance failure and elastic demand Horizontal app tiers App should tolerate instance replacement
  • Azure Site Recovery Regional disaster recovery DR to another region Failover design and testing required

An availability set cannot be added to an existing VM after creation. To use one, deploy the VMs into the set at creation or rebuild the architecture. Zones are also selected at creation for zonal VMs. Moving a VM into a different zone is not a simple property edit.

Availability Zones

Zones are useful when the question mentions datacenter-level isolation, zone-redundant architecture, or high availability within a region. A zonal VM is pinned to one zone. A resilient application normally deploys multiple VMs across zones and places a zone-redundant load balancer, application gateway, or other traffic manager in front where appropriate. The storage design must also match the availability goal. Managed disks can use locally redundant or zone-redundant options depending on disk type and support.

  • Example CLI pattern: az vm create \
  • -resource-group rg-prod-web \
  • -name vm-web-z1 \
  • -image Ubuntu2204 \
  • -zone 1 \
  • -size Standard_D2s_v5 \
  • -vnet-name vnet-prod \
  • -subnet snet-web \
  • -admin-username azureadmin \
  • -ssh-key-values ~/.ssh/id_rsa.pub

If a deployment fails in a zone, check SKU availability in that zone, zonal quota, unsupported disk settings, and capacity constraints. A VM size might be available in the region but not in the requested zone.

Availability Sets

Availability sets use fault domains and update domains. Fault domains represent groups of hardware that share power and network infrastructure. Update domains represent groups that can be rebooted during planned maintenance. Azure distributes VMs in an availability set across these domains. The design reduces the chance that one host failure or maintenance wave affects all instances.

Availability sets are not a scaling feature. They do not create new VMs, balance traffic, or repair unhealthy apps. You still need a load balancer or application-level traffic distribution, and you need at least two VMs. Managed disks are recommended because Azure aligns disk placement with VM fault domains for managed availability sets.

  • Bicep example: resource avset 'Microsoft.Compute/availabilitySets@2024-07-01' = {
  • name: 'avset-web-prod'
  • location: location
  • sku: {
  • name: 'Aligned'
  • }
  • properties: {
  • platformFaultDomainCount: 2
  • platformUpdateDomainCount: 5
  • }
  • }
  • resource vm 'Microsoft.Compute/virtualMachines@2024-07-01' = {
  • name: vmName
  • location: location
  • properties: {
  • availabilitySet: {
  • id: avset.id
  • }
  • hardwareProfile: {
  • vmSize: 'Standard_D2s_v5'
  • }
  • storageProfile: storageProfile
  • osProfile: osProfile
  • networkProfile: networkProfile
  • }
  • }
  • VM Scale Sets

A VM Scale Set is a group of VM instances managed together. Scale sets can use uniform orchestration, where instances are more identical and managed as a set, or flexible orchestration, which supports a more VM-like model and broader high availability patterns. Scale sets can integrate with Azure Load Balancer or Application Gateway. They can use autoscale rules based on metrics such as CPU, queue length, or custom signals.

Scale sets work best for stateless workloads or workloads that externalize state to databases, storage, queues, or caches. Instance replacement is normal. If the app stores unique state on the local OS disk, scale-in or repair can cause data loss. Use custom images, cloud-init, extensions, or configuration management to make instances reproducible.

  • CLI example: az vmss create \
  • -resource-group rg-prod-web \
  • -name vmss-web-prod \
  • -image Ubuntu2204 \
  • -instance-count 3 \
  • -vm-sku Standard_D2s_v5 \
  • -upgrade-policy-mode automatic \
  • -lb lb-web-prod \
  • -backend-pool-name bepool-web
  • az monitor autoscale create \
  • -resource-group rg-prod-web \
  • -resource vmss-web-prod \
  • -resource-type Microsoft.Compute/virtualMachineScaleSets \
  • -name autoscale-web \
  • -min-count 2 --max-count 10 --count 3
  • az monitor autoscale rule create \
  • -resource-group rg-prod-web \
  • -autoscale-name autoscale-web \
  • -condition "Percentage CPU > 70 avg 10m" \
  • -scale out 1
  • Upgrade and Health Strategy

Scale set upgrade policy controls how model changes reach instances. Manual means you update instances yourself. Automatic applies changes without as much staged control. Rolling upgrades update batches and can use health probes to pause when instances become unhealthy. Automatic instance repair can replace unhealthy instances when health signals are configured.

  • Requirement Recommended feature
  • Add instances during high CPU Autoscale rule
  • Replace unhealthy scale set instances Automatic repairs with health signal
  • Safely roll image updates Rolling upgrade policy
  • Spread instances across zones Zone-aware scale set design
  • Put instances behind one frontend IP Azure Load Balancer backend pool
  • Troubleshooting Scenarios

Scenario 1: Autoscale did not add instances. Check the autoscale setting target resource, metric namespace, time aggregation, operator, duration, cooldown, minimum and maximum limits, and whether the scale set already reached max count. Also check quota. Autoscale cannot create instances if the subscription lacks regional family quota.

Scenario 2: Instances are created but do not receive traffic. Check backend pool membership, load balancer rule, health probe path and port, NSG effective rules, guest firewall, and whether the app is listening. A failed health probe keeps the instance out of rotation even if the VM is running.

Scenario 3: Rolling upgrade stops. Check instance health, extension status, application health extension, boot diagnostics, and model differences. A bad custom script can make every new instance unhealthy. Fix the model, then update or reimage affected instances.

Exam Design Logic

Choose availability zones when the question requires protection from datacenter failure in the same region. Choose availability sets when the question describes two or more traditional VMs that must be isolated across fault and update domains and zones are not the focus. Choose VM Scale Sets when the requirement is many similar instances, autoscaling, automatic repair, or consistent rolling deployment. Choose Azure Site Recovery when the requirement is regional disaster recovery for VMs.