Why High availability design patterns in Azure? - Purpose & Use Cases

The Big Idea

What if your website never went down, even during traffic spikes or failures?

The Scenario

Imagine running a popular online store where your website crashes every time many customers visit at once. You try to fix it by restarting servers manually or adding more machines one by one.

The Problem

This manual approach is slow and stressful. You can't predict when crashes happen, and fixing them takes time. Customers get frustrated and leave, and your business loses money.

The Solution

High availability design patterns help you build systems that keep working even if parts fail. They automatically spread traffic, switch to backups, and recover quickly without downtime.

Before vs After

✗ Before

Single server setup
No failover
Manual restart on failure

✓ After

Load balancer with multiple servers
Automatic failover
Health checks and auto-recovery

What It Enables

You can deliver reliable services that stay online and responsive, making users happy and your business trustworthy.

Real Life Example

A bank uses high availability patterns so customers can always access their accounts, even if one data center goes offline.

Key Takeaways

Manual fixes cause delays and unhappy users.

High availability patterns prevent downtime automatically.

They ensure your service stays up and running smoothly.

Practice

1. Which Azure service is primarily used to distribute incoming traffic across multiple virtual machines to ensure high availability?

easy

A. Azure Functions

B. Azure Blob Storage

C. Azure Load Balancer

D. Azure Cosmos DB

Solution

1. Step 1: Understand the role of Azure Load Balancer

   Azure Load Balancer distributes incoming network traffic across multiple VMs to prevent any single VM from becoming a bottleneck.

2. Step 2: Compare with other services

   Azure Blob Storage stores data, Azure Functions run code, and Cosmos DB is a database service; none distribute traffic.

3. Final Answer:

   Azure Load Balancer -> Option C

4. Quick Check:

   Traffic distribution = Azure Load Balancer [OK]

Hint: Load Balancer spreads traffic to VMs for uptime [OK]

Common Mistakes:

• Confusing storage or compute services with traffic distribution
• Choosing Azure Functions for load balancing
• Selecting database services for availability patterns

2. Which of the following is the correct syntax to create an Azure VM Scale Set using Azure CLI for high availability?

easy

A. az vm create --name MyScaleSet --resource-group MyResourceGroup --image UbuntuLTS --instance-count 3

B. az vm create --name MyScaleSet --resource-group MyResourceGroup --image UbuntuLTS --count 3

C. az vmss deploy --name MyScaleSet --group MyResourceGroup --image UbuntuLTS --instances 3

D. az vmss create --name MyScaleSet --resource-group MyResourceGroup --image UbuntuLTS --instance-count 3

Solution

1. Step 1: Identify the correct Azure CLI command for VM Scale Set creation

   The command to create a VM Scale Set is az vmss create, not az vm create.

2. Step 2: Check the parameters

   Parameters like --name, --resource-group, --image, and --instance-count are correctly used in az vmss create --name MyScaleSet --resource-group MyResourceGroup --image UbuntuLTS --instance-count 3.

3. Final Answer:

   az vmss create --name MyScaleSet --resource-group MyResourceGroup --image UbuntuLTS --instance-count 3 -> Option D

4. Quick Check:

   VM Scale Set creation uses az vmss create [OK]

Hint: Use 'az vmss create' for VM Scale Sets [OK]

Common Mistakes:

• Using 'az vm create' instead of 'az vmss create'
• Incorrect parameter names like --count instead of --instance-count
• Mixing resource group parameter names

3. Consider this Azure Load Balancer configuration snippet:

frontendIPConfiguration:
  name: LoadBalancerFrontEnd
  publicIPAddress:
    id: /subscriptions/xxx/resourceGroups/rg/providers/Microsoft.Network/publicIPAddresses/myPublicIP
backendAddressPools:
  - name: BackendPool
loadBalancingRules:
  - name: HTTPRule
    frontendIPConfiguration: LoadBalancerFrontEnd
    backendAddressPool: BackendPool
    protocol: Tcp
    frontendPort: 80
    backendPort: 80
    enableFloatingIP: false
    idleTimeoutInMinutes: 4
    loadDistribution: Default

What will happen if one VM in the backend pool becomes unhealthy?

medium

A. Traffic will automatically stop going to the unhealthy VM

B. Traffic will continue to be sent to the unhealthy VM

C. Load Balancer will restart the unhealthy VM

D. Load Balancer will redirect traffic to a different port

Solution

1. Step 1: Understand Azure Load Balancer health probe behavior

   Azure Load Balancer requires health probes configured to detect unhealthy VMs and stop sending traffic to them. This snippet does not show health probes configured, but in practice, health probes are necessary for proper load balancing.

2. Step 2: Analyze the effect of missing health probes

   Without health probes, the Load Balancer cannot detect unhealthy VMs, so it continues sending traffic to all VMs in the backend pool. However, best practice is to configure health probes to avoid this.

3. Final Answer:

   Traffic will automatically stop going to the unhealthy VM -> Option A

4. Quick Check:

   Health probes detect unhealthy VMs and stop traffic [OK]

Hint: Configure health probes to avoid sending traffic to bad VMs [OK]

Common Mistakes:

• Assuming Load Balancer auto-detects unhealthy VMs without probes
• Thinking Load Balancer restarts VMs
• Confusing port redirection with load balancing

4. You have configured an Active-Passive high availability setup using Azure Traffic Manager. However, during failover, users experience downtime. What is the most likely cause?

medium

A. Traffic Manager is set to Performance routing with multiple active endpoints

B. Traffic Manager is set to Priority routing but health probes are misconfigured

C. Azure Load Balancer is not configured with a public IP

D. VM Scale Set has only one instance

Solution

1. Step 1: Understand Active-Passive with Traffic Manager Priority routing

   Priority routing sends traffic to the primary endpoint unless it is unhealthy, then fails over to secondary.

2. Step 2: Identify impact of misconfigured health probes

   If health probes are misconfigured, Traffic Manager cannot detect endpoint health and will not failover properly, causing downtime.

3. Final Answer:

   Traffic Manager is set to Priority routing but health probes are misconfigured -> Option B

4. Quick Check:

   Priority routing + bad probes = failover fails [OK]

Hint: Check health probes when failover fails in Priority routing [OK]

Common Mistakes:

• Confusing routing methods in Traffic Manager
• Blaming Load Balancer or VM Scale Set for Traffic Manager failover
• Ignoring health probe configuration

5. You want to design a geo-redundant high availability solution for a web app in Azure that must remain available even if an entire Azure region fails. Which combination of Azure services and design patterns best achieves this?

hard

A. Deploy the app in two regions with Azure Traffic Manager using Performance routing and Azure SQL Geo-Replication

B. Deploy the app in one region with Azure Load Balancer and VM Scale Sets, and use Azure Backup for disaster recovery

C. Deploy the app in two regions with Azure Traffic Manager using Priority routing and VM Scale Sets in each region

D. Deploy the app in one region with Azure Application Gateway and use Azure Blob Storage for static content

Solution

1. Step 1: Understand geo-redundancy requirements

   To survive a full region failure, the app must be deployed in multiple regions with traffic routed between them.

2. Step 2: Evaluate options for traffic routing and data replication

   Performance routing in Traffic Manager directs users to the closest healthy region. Azure SQL Geo-Replication ensures database availability across regions.

3. Step 3: Compare with other options

   Priority routing is for Active-Passive, not best for geo-load balancing. Single region deployments cannot survive region failure. Application Gateway is regional and does not provide geo-failover.

4. Final Answer:

   Deploy the app in two regions with Azure Traffic Manager using Performance routing and Azure SQL Geo-Replication -> Option A

5. Quick Check:

   Geo-redundancy needs multi-region + performance routing + geo-replication [OK]

Hint: Use multi-region + Traffic Manager Performance + Geo-Replication [OK]

Common Mistakes:

• Choosing Priority routing for geo-load balancing
• Relying on single region with backup for high availability
• Confusing Application Gateway with global traffic routing