Study guide

9.2 Compute High Availability: Load Balancing & VM Scale Set Design

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.2 Compute High Availability: Load Balancing & VM Scale Set Design

Key Takeaways Explain This Topic AI

Azure Load Balancer is a regional, Layer 4 (TCP/UDP) service; the Standard SKU is the only one that integrates with Availability Zones and is the one AZ-305 expects in new designs.

Virtual Machine Scale Sets (VMSS) come in two orchestration modes — Flexible (Microsoft's current recommendation) and Uniform (legacy, still required for AKS and Service Fabric).

Flexible orchestration manages standard Azure IaaS VMs directly, supports up to 1,000 instances, mixes VM sizes/OS/Spot+on-demand in one scale set, and spreads instances across zones or fault domains automatically.

Uniform orchestration manages scale-set-specific VM objects, supports Automatic OS Upgrade and Service Fabric/AKS integration that Flexible does not, but is less flexible for mixed workloads.

The same SLA pairing applies to scale sets as to plain VMs: 99.95% when spread across fault domains only, 99.99% when spread across 2+ Availability Zones — in either orchestration mode.

Last updated: July 2026

Why This Topic Matters

Availability Sets and Zones (9.1) protect individual VM instances from physical failure, but they don't route traffic or add capacity on their own. AZ-305's compute-HA subgroup also tests whether you can design the layer that sits on top: Load Balancer to distribute traffic across healthy instances, and Virtual Machine Scale Sets (VMSS) to manage the fleet of instances as a single elastic unit. Microsoft has been steering all new designs toward Flexible orchestration for scale sets, and AZ-305 questions increasingly assume that as the default unless a scenario detail (Service Fabric, AKS, Automatic OS Upgrade) forces Uniform instead.

Core Terms and Rules

Azure Load Balancer operates at Layer 4 and distributes inbound TCP/UDP traffic across a backend pool of VM instances based on health probes. It comes in two SKUs:

Standard SKU — zone-redundant or zonal, integrates with Availability Zones, secure by default (closed unless an NSG allows traffic), and is what Microsoft recommends for all new deployments.

Basic SKU — regional only, no Availability Zone integration, being retired; do not select it in a design question unless the scenario explicitly forbids Standard-tier cost.

A Virtual Machine Scale Set is a group of load-balanced, identically (or flexibly) configured VMs that Azure can scale in or out automatically based on metrics, a schedule, or manual triggers. There is no extra charge for the scale set construct itself — you pay only for the underlying VM instances.

Flexible vs. Uniform Orchestration

  • Attribute Flexible orchestration (recommended) Uniform orchestration (legacy)
  • VM type managed Standard Azure IaaS VMs (full VM API) Scale-set-specific VM objects (limited API)
  • Max instances (with fault-domain guarantee) 1,000 100 (up to 3,000 without the guarantee)
  • Mix OS, VM size, Spot + on-demand Yes No (must be uniform)
  • Availability SLA 99.95% (fault domains) / 99.99% (2+ zones) 99.95% (fault domains) / 99.99% (2+ zones)
  • Update domains Deprecated — maintenance proceeds fault domain by fault domain Up to 5 update domains
  • Azure Backup / Site Recovery Yes No
  • Automatic OS Image Upgrade No Yes
  • Service Fabric / AKS backing No Yes
  • Standard Azure VM APIs, RBAC, tagging Full support Limited (scale-set VM API only)

The practical exam rule: default to Flexible for any new, generic "highly available, auto-scaling web/app tier" scenario. Switch to Uniform only when the scenario names a dependency that requires it — Service Fabric , Azure Kubernetes Service (AKS) node pools, or a hard requirement for Automatic OS Image Upgrade that Flexible doesn't offer.

Combining the Pieces

A typical AZ-305-tested compute-HA design layers three things:

A VMSS in Flexible mode , configured to spread instances across 2 or 3 Availability Zones (or, in a non-AZ region, across fault domains), with autoscale rules on CPU or queue depth.

A Standard Load Balancer in front, health-probing each instance and routing only to healthy backends.

An Application Health Extension installed on the instances (required for Flexible orchestration to detect unhealthy VMs and trigger automatic instance repair — Uniform can alternatively use the Load Balancer's own health probe for this).

Autoscale rules for either orchestration mode can trigger on a metric (CPU percentage, queue length, custom Application Insights metric), a schedule (scale up before a known traffic peak), or manual capacity changes . Because scale sets bill only for the underlying VM instances, a well-designed autoscale profile is also a cost lever — scaling in aggressively overnight lowers spend without touching the HA guarantees, since the remaining instances still satisfy the fault-domain or zone-spread requirement as long as the minimum instance count stays at 2 or more.

Exam Scenarios

Scenario 1: An e-commerce front end needs to auto-scale between 3 and 50 identical web servers, mixing Spot instances for cost savings with on-demand instances for baseline capacity, and must tolerate the loss of an entire datacenter. Design decision : VMSS in Flexible orchestration (only Flexible mixes Spot and on-demand in the same set) spread across 3 Availability Zones, fronted by a Standard Load Balancer — reaching the 99.99% SLA.

Scenario 2: A team is migrating an on-premises Service Fabric cluster to Azure VMs and needs the scale set to back the cluster directly. Design decision : Uniform orchestration — Flexible does not support Service Fabric.

Scenario 3: A design calls for the lowest-cost load-balancing tier and does not need Availability Zone awareness. Trap : candidates sometimes pick Basic Load Balancer for cost, but Microsoft is retiring Basic and AZ-305 (current blueprint) expects Standard to be the default recommendation regardless, since Basic cannot be zone-redundant and lacks the security-by-default posture Microsoft now requires in reference architectures.

Takeaways

Load Balancer is Layer 4/regional; reserve Layer 7/global routing decisions (Front Door, Application Gateway, Traffic Manager) for the networking chapter — but know that Load Balancer is what actually sits in front of a VMSS backend pool.

Flexible orchestration is the default answer on the current exam; Uniform is the answer only when Service Fabric, AKS, or Automatic OS Image Upgrade is explicitly in play.

The SLA math for a scale set mirrors plain VMs: instance count and zone spread — not the orchestration mode — determine whether you hit 99.95% or 99.99%.

Application Health Extension (Flexible) vs. Load Balancer health probe (Uniform, optional) is a subtle distinction the exam can test directly.