Study guide

6.3 Load Balancing Decision Matrix & Multi-Tier Design

Designing and Implementing Microsoft Azure Networking Solutions AZ-700

Track your progress as you read

Finished sections get a check mark.

1 Introduction & AZ-700 Exam Overview

0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured

2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture

1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)

3 Chapter 2: Azure Name Resolution & Core Routing

2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange

4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway

3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter

5 Chapter 4: Azure ExpressRoute & Virtual WAN

4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting

6 Chapter 5: Regional Load Balancing & Application Gateway

5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design

7 Chapter 6: Global Traffic Management & Azure Front Door

6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door

8 Chapter 7: Azure Private Link & Service Endpoints

7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions

9 Chapter 8: Network Security Groups & Azure Bastion

8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules

10 Chapter 9: Azure Firewall & Security Policies

9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection

11 Chapter 10: Azure Network Observability & Troubleshooting

10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture

6.3 Load Balancing Decision Matrix & Multi-Tier Design

Key Takeaways Explain This Topic AI

Azure offers four distinct load balancing services differentiated across two primary dimensions: Scope (Global vs. Regional) and OSI Layer (Layer 4 transport vs. Layer 7 application).

Azure Front Door is the premier Global Layer 7 service for HTTP/HTTPS workloads requiring edge WAF, caching, and SSL termination; Traffic Manager is the Global DNS/Layer 4 service for non-HTTP protocols and direct IP connectivity.

Application Gateway provides Regional Layer 7 load balancing with deep URL path-based routing, cookie session affinity, and regional WAF; Azure Load Balancer provides ultra-low latency Regional Layer 4 load balancing across TCP/UDP ports.

Enterprise multi-tier architectures combine Front Door at the global edge with regional Application Gateways and internal Standard Load Balancers for secure, highly available end-to-end delivery.

Origins behind Front Door must be locked down using X-Azure-FDID header validation and Network Security Groups restricted to the AzureFrontDoor.Backend service tag or Private Link.

Last updated: August 2026

Load Balancing Decision Matrix & Multi-Tier Design

Designing enterprise network architectures in Azure requires selecting the right load balancing technology—or combination of technologies—to satisfy performance, protocol, security, and geographic requirements. Microsoft Azure provides four distinct load balancing services:

  • Azure Front Door (AFD): Global Layer 7 Reverse Proxy & CDN
  • Azure Traffic Manager (ATM): Global DNS-Based Traffic Director
  • Azure Application Gateway (AppGW): Regional Layer 7 Application Load Balancer
  • Azure Load Balancer (ALB): Regional Layer 4 Network Load Balancer
  • 1. The Azure Load Balancing Decision Matrix

The fundamental decision framework categorizes these four services along two core architectural axes: Scope (Global vs. Regional) and OSI Layer (Layer 4 vs. Layer 7). +-----------------------------------------------------------------------------+

  • | AZURE LOAD BALANCING 2x2 ARCHITECTURAL MATRIX |
  • | |
  • | GLOBAL SCOPE REGIONAL SCOPE |
  • | +---------------------------+---------------------------+ |
  • | | | | |
  • | LAYER 7 | AZURE FRONT DOOR | AZURE APPLICATION GATEWAY | |
  • | (HTTP/HTTPS)| - Anycast Edge Reverse | - Regional Layer 7 Proxy | |
  • | (App Layer) | Proxy & CDN | - URL Path / Host Routing | |
  • | | - Global WAF & Bot Defense| - Regional WAF (CRS 3.2+) | |
  • | | - SSL Offload & Caching | - Private VNet Deployment | |
  • | | | | |
  • | +---------------------------+---------------------------+ |
  • | | | | |
  • | LAYER 4 | AZURE TRAFFIC MANAGER | AZURE LOAD BALANCER | |
  • | (TCP/UDP) | - Global DNS-Based Router | - Ultra-Low Latency L4 | |
  • | (Transport) | - Protocol-Agnostic | - Millions of Flows/Sec | |
  • | | - Direct Client-to-Origin | - Internal & Public SKUs | |
  • | | Data Path (No Proxy) | - Zone-Redundant Data | |
  • | | | | |
  • | +---------------------------+---------------------------+ |
  • +-----------------------------------------------------------------------------+
  • Comprehensive Service Comparison Matrix

Architectural Feature Azure Front Door Azure Traffic Manager Azure Application Gateway Azure Load Balancer (Standard)

  • OSI Layer Layer 7 (HTTP/HTTPS) DNS Layer (Any L4/L7) Layer 7 (HTTP/HTTPS/HTTP2/WebSocket) Layer 4 (TCP/UDP)
  • Geographic Scope Global (Anycast Edge) Global (DNS Servers) Regional (VNet Subnet) Regional (VNet Subnet)
  • Data Path Role Active Reverse Proxy Control Plane Only (DNS) Active Reverse Proxy In-line SDN Packet Forwarder

SSL/TLS Termination Yes (Edge PoP Offload) No (Client negotiates with Origin) Yes (Gateway Offload) No (Pass-through only)

  • WAF Integration Yes (Global WAF + Bot Def) No Yes (Regional WAF SKU) No
  • Static Content Caching Yes (Built-in CDN) No No No

Private VNet Backends Yes (via Private Link in Premium) Yes (Private IPs via DNS resolution) Yes (Direct Subnet NICs/IPs) Yes (Direct Subnet NICs/IPs)

Non-HTTP Protocol Support No (HTTP/HTTPS only) Yes (Any TCP/UDP/IP) No (HTTP/HTTPS/WS only) Yes (Any TCP/UDP)

Client IP Preservation Injected in X-Forwarded-For Preserved natively Injected in X-Forwarded-For Preserved natively in IP packet

2. Decision Tree: Choosing the Right Solution

When evaluating exam scenarios or enterprise requirements, follow this systematic decision tree: +-----------------------------------------------------------------------------+

  • | LOAD BALANCER SELECTION DECISION TREE |
  • | |
  • | [Incoming Application Traffic Requirement] |
  • | | |
  • | v |
  • | Is the traffic HTTP/HTTPS? |
  • | |-- NO (e.g., Gaming UDP, SQL TCP, Custom L4) |
  • | | |-- Is global multi-region routing required? |
  • | | | |-- YES ==> Use AZURE TRAFFIC MANAGER + AZURE LOAD BALANCER |
  • | | | +-- NO ==> Use AZURE LOAD BALANCER (Standard L4) |
  • | | |
  • | +-- YES (Web, REST API, Microservices) |
  • | |-- Is global multi-region acceleration/WAF required? |
  • | | |-- YES ==> Use AZURE FRONT DOOR (Standard/Premium) |
  • | | +-- NO (Single Region / Dedicated VNet Gateway) |
  • | | |-- Is Layer 7 routing (URL path/cookie affinity/WAF) |
  • | | | required within the region? |
  • | | | |-- YES ==> Use AZURE APPLICATION GATEWAY (v2) |
  • | | | +-- NO ==> Use AZURE LOAD BALANCER (Standard) |
  • +-----------------------------------------------------------------------------+
  • 3. Multi-Tier Enterprise Design Patterns

Enterprise architectures rarely rely on a single load balancer. High-scale, defense-in-depth cloud applications combine multiple services into a coordinated Multi-Tier Load Balancing Architecture .

Pattern 1: Global Edge + Regional Layer 7 + Internal Layer 4 (Edge-to-Core)

This is the premier reference architecture for global enterprise web applications.

Tier 1 (Global Edge): Azure Front Door Premium terminates client Anycast connections worldwide, applies global WAF rules and Bot Defense, caches static assets, and accelerates dynamic traffic over the Microsoft dark fiber backbone.

Tier 2 (Regional Ingress): Azure Application Gateway v2 deployed inside a private subnet in each region receives traffic from Front Door, performs microservice URL path routing (e.g., /orders/* -> Order Pods, /users/* -> User Pods), and enforces regional security policies.

Tier 3 (Internal Microservices & Data Tier): Internal Azure Load Balancer (Standard) load balances internal TCP/UDP traffic across backend database replicas, message brokers, or legacy internal services.

Pattern 2: Global Hybrid Gaming / Non-HTTP Services

Global Layer: Azure Traffic Manager uses Performance or Multivalue routing to direct players to the closest regional public IP.

Regional Layer: Standard Public Load Balancers distribute UDP game server packets across virtual machine scale sets with ultra-low latency and zero packet inspection overhead.

Loading diagram... Multi-Tier Enterprise Architecture: Front Door to Regional App Gateway to Internal Load Balancer

4. Origin Security & Header Validation ( X-Azure-FDID )

When deploying Azure Front Door in front of regional web servers or Application Gateways, you must prevent attackers from bypassing Front Door and sending malicious traffic directly to the backend origin public IP. +-----------------------------------------------------------------------------+

  • | FRONT DOOR ORIGIN LOCKDOWN MECHANISMS |
  • | |
  • | ATTACK VECTOR: Malicious Actor bypasses AFD WAF and attacks Origin direct! |
  • | [Attacker] =============== DIRECT ATTACK ATTEMPT ==============> [Origin] |
  • | | |
  • | DEFENSE-IN-DEPTH CONTROLS: | |
  • | 1. Network Security Group (NSG): Restrict inbound 443 to | |
  • | Service Tag: 'AzureFrontDoor.Backend' (Blocks public scans) | |
  • | 2. Header Validation: Inspect HTTP Header: | |
  • | 'X-Azure-FDID' == '<Unique Front Door Profile GUID>' | |
  • | (Drops requests from other Azure tenants using Front Door!) | |
  • | 3. Private Link (Premium SKU): Zero public IP address exposure! | |
  • +-----------------------------------------------------------------------------+

The Three Layers of Origin Defense:

Azure Private Link (Front Door Premium): The most secure approach. Eliminates public IP addresses entirely from the origin, routing traffic through private endpoints.

Network Security Group (NSG) with Service Tags: If using public endpoints, restrict inbound port 80/443 traffic on the backend subnet to the AzureFrontDoor.Backend service tag and Azure platform infrastructure ( AzurePlatformLKM ).

X-Azure-FDID Header Inspection: Because all Front Door profiles in all Azure subscriptions share the AzureFrontDoor.Backend IP range, an NSG alone does not prevent another tenant from configuring their Front Door to point to your origin. Front Door injects a unique header containing your profile's GUID:

Header Name: X-Azure-FDID

Origin Action: The backend Application Gateway, Nginx, IIS, or web application must inspect this header and reject any request where X-Azure-FDID does not match your specific Front Door resource ID.

Client IP Preservation Headers

Because Layer 7 reverse proxies terminate client TCP connections, the origin sees Front Door's internal IP as the socket source. Front Door injects standard forwarding headers:

X-Forwarded-For : Contains the original client public IPv4/IPv6 address (e.g., 203.0.113.195 ).

X-Forwarded-Host : Contains the original Host header sent by the client browser (e.g., www.contoso.com ).

X-Forwarded-Proto : Indicates the protocol used by the client ( http or https ).

X-Azure-ClientIP : Dedicated Microsoft header containing the client IP address as detected by the edge PoP.