An organization is designing a high-availability infrastructure in a single Azure region for a suite of services hosted on Azure Virtual Machines. The VMs currently utilize Standard SKU public IP addresses. The infrastructure must meet the following requirements:
- Handle web application traffic (HTTPS) with support for URL-path routing and SSL/TLS termination.
- Load balance incoming custom TCP traffic on port 9500 to a separate backend pool of virtual machines.
- Avoid mixing Basic and Standard SKU resources to prevent validation errors.
Which two load balancing services should you include in the design?
- Azure Application Gateway (Standard v2 SKU)Answer
- Azure Load Balancer (Standard SKU)Answer
- CAzure Load Balancer (Basic SKU)
- DAzure Traffic Manager
Answer
The load balancing design should include Azure Application Gateway (Standard v2 SKU) for Layer 7 web traffic and Azure Load Balancer (Standard SKU) for Layer 4 TCP traffic.
Azure Application Gateway (Standard v2 SKU) is correct because it operates at Layer 7, providing the required SSL/TLS termination and URL-path routing for HTTPS traffic. Azure Load Balancer (Standard SKU) is correct because it operates at Layer 4, providing high-throughput load balancing for custom TCP traffic on port 9500. Additionally, since the backend VMs use Standard SKU public IP addresses, using the Standard SKU Load Balancer avoids validation errors associated with mixing Basic and Standard SKUs.
Step-by-Step Solution
Key Concept
Selecting and combining Azure load balancing services based on layer features (Layer 4 vs Layer 7) and SKU compatibility requirements.