An enterprise is modernizing a regional application hosted on a backend pool of Azure Virtual Machines in the East US region. The solution requires Layer load balancing for incoming TCP traffic, regional distribution, and high availability across Availability Zones. The design does not require SSL/TLS termination or URL-path-based routing. The virtual machines are currently configured with Basic SKU public IP addresses directly on their network interfaces. You need to recommend a load balancing configuration that meets these requirements. Which configuration should you recommend?
- ADeploy Azure Traffic Manager to route TCP connections directly to the virtual machines' Basic SKU public IP addresses.
- BDeploy an Azure Standard Load Balancer and associate the virtual machines' existing Basic SKU public IP addresses to its backend pool.
- Deploy an Azure Standard Load Balancer and upgrade the virtual machines' public IP addresses to Standard SKU.Answer
- DDeploy an Azure Basic Load Balancer and configure a zone-redundant frontend IP address.
Answer
Deploy an Azure Standard Load Balancer and upgrade the virtual machines' public IP addresses to Standard SKU.
Deploying an Azure Standard Load Balancer meets the requirements because it operates at Layer (TCP/UDP) and supports Availability Zones for high availability. However, to add the virtual machines to its backend pool, any public IP addresses assigned directly to their network interfaces must match the load balancer's SKU. Therefore, upgrading the virtual machines' public IP addresses from Basic to Standard SKU is required to avoid configuration and validation failures.
Step-by-Step Solution
Key Concept
Azure Load Balancer SKU requirements and availability zone support.