Study guide

13.2 Hybrid Connectivity 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

13.2 Hybrid Connectivity Design

Key Takeaways Explain This Topic AI

VPN Gateway encrypts traffic over the public internet (IPsec/IKE); ExpressRoute is a private, non-internet circuit with higher SLA (99.95%) but no built-in encryption unless you add IPsec or MACsec.

ExpressRoute bandwidth ranges from 50 Mbps to 10 Gbps per circuit; ExpressRoute Direct offers dual 10-Gbps, 100-Gbps, or 400-Gbps ports for the largest enterprises.

ExpressRoute Premium SKU raises the route limit from 4,000 to 10,000 routes and unlocks global connectivity across geopolitical regions — Local and Standard SKUs are region/geography-limited.

Virtual WAN Basic hubs support only Site-to-Site VPN (up to 500 Mbps aggregate); Standard hubs add ExpressRoute, Point-to-Site VPN, VNet-to-VNet transit, Azure Firewall, and up to 20 Gbps per hub.

Standard Virtual WAN hubs are automatically connected in a full mesh over the Microsoft backbone, removing the need to manually configure any-to-any VNet peering or transit routing.

Last updated: July 2026

Why This Topic Matters

"Recommend a connectivity solution that connects Azure resources to on-premises networks" is official Domain 4 bullet #46, and hybrid connectivity design questions are near-guaranteed on AZ-305 because almost every enterprise workload assumes a hybrid footprint. The exam distinguishes candidates who memorize service names from those who can reason about bandwidth, encryption, cost, and blast radius trade-offs across VPN Gateway, ExpressRoute, and Virtual WAN.

VPN Gateway

An Azure VPN Gateway creates an encrypted (IPsec/IKE) tunnel over the public internet between Azure and an on-premises location (Site-to-Site), an individual client (Point-to-Site), or another Azure VNet (VNet-to-VNet). Key design facts:

SKUs span from legacy Basic (avoid — deprecated) through VpnGw1-5 and the zone-redundant VpnGw1AZ-5AZ family, with aggregate throughput benchmarks roughly from 650 Mbps (VpnGw1) up to 10 Gbps (VpnGw5) .

The Az-suffixed SKUs (e.g., VpnGw2AZ) deploy gateway instances across Availability Zones for zone resiliency — always recommend the AZ SKU in a region that supports zones unless the scenario has a specific reason not to.

VPN Gateway traffic traverses the public internet (encrypted), so it inherits internet variability — not ideal for workloads with strict, consistent low-latency requirements.

Active-active gateway configuration (two instances, both active) improves resiliency over active-passive.

ExpressRoute

ExpressRoute provides a private, dedicated connection to Azure through a connectivity provider — traffic never traverses the public internet, which is why ExpressRoute carries a 99.95% SLA (vs. VPN Gateway's lower internet-dependent reliability) and far more predictable latency.

Bandwidth and SKU Tiers

  • Aspect Detail
  • Circuit bandwidth options 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, 5 Gbps, 10 Gbps

ExpressRoute Direct Dual 10-Gbps, 100-Gbps, or 400-Gbps ports (largest enterprises, multiple circuits over one physical connection)

  • Local SKU VNets in the same Azure region as the circuit's peering location only
  • Standard SKU VNets within the same geopolitical region

Premium SKU Global connectivity — a circuit in any region reaches VNets in every region worldwide; also raises route limit from 4,000 to 10,000 routes

Encryption caveat : ExpressRoute private peering is not encrypted by default . If a workload has a compliance requirement for encryption-in-transit over ExpressRoute, the design must add IPsec over ExpressRoute (site-to-site VPN layered on the private peering) or MACsec (link-layer encryption, typically with ExpressRoute Direct). This is a classic AZ-305 trap: candidates assume "private connection" means "encrypted," and the exam will test that assumption directly.

VPN as ExpressRoute Failover

A resilient hybrid design layers a Site-to-Site VPN Gateway as a backup path for ExpressRoute failure — both connect into the same virtual network gateway subnet, and Azure prefers the ExpressRoute route (via BGP) when both are healthy.

Virtual WAN

Virtual WAN is Microsoft's managed hub-and-spoke networking service that consolidates VPN, ExpressRoute, Point-to-Site, and NVA/firewall connectivity into virtual hubs, automatically meshed together.

  • Hub Type Site-to-Site VPN ExpressRoute Point-to-Site VPN VNet-to-VNet Transit Azure Firewall Max Throughput
  • Basic Yes No No No No ~500 Mbps aggregate
  • Standard Yes Yes Yes Yes Yes Up to 20 Gbps per hub

Standard hubs are automatically connected in a full mesh over the Microsoft global backbone, so any spoke VNet or branch site can reach any other spoke or branch without manually configuring peering or transit routes — this is the single biggest operational win over building the same topology manually with VNet peering and route tables. Routing Intent and Routing Policies on a Standard hub can force all internet-bound or private (VPN/ExpressRoute/VNet/NVA) traffic through a security appliance (Azure Firewall, NVA, or partner SaaS) deployed in the hub.

Decision Table

Scenario Recommended Solution

Small number of sites, moderate bandwidth, cost-sensitive, tolerant of internet variability Site-to-Site VPN Gateway (AZ SKU)

Consistent low latency, high bandwidth, mission-critical, predictable performance SLA needed ExpressRoute (Standard or Premium SKU based on region reach)

Dozens to hundreds of branch sites, need centralized any-to-any routing and built-in firewall Virtual WAN Standard hub(s) with VPN + ExpressRoute gateways

Only 1-2 sites, all in one Azure region, low bandwidth (<500 Mbps) Virtual WAN Basic hub (Site-to-Site VPN only)

Regulatory requirement for encryption over a private circuit ExpressRoute + IPsec (or MACsec on ExpressRoute Direct)

Exam Scenario

A logistics company has 60 branch offices across North America and Europe, a headquarters requiring guaranteed low-latency access to Azure SQL Managed Instance, and a security mandate to centrally inspect all branch-to-branch and branch-to-internet traffic. The design: a Virtual WAN with Standard hubs in each major region (any-to-any full mesh over Microsoft's backbone), an ExpressRoute circuit (Standard or Premium SKU depending on regional reach) with Premium SKU if HQ needs cross-geography VNet access connected into the HQ-region hub for the latency-sensitive SQL MI traffic, Site-to-Site VPN gateways in each Standard hub for the 60 branch sites, and Routing Intent configured to force all internet and inter-hub traffic through an Azure Firewall deployed in each hub for centralized inspection.