Question

Difficulty: MediumApplication Load Balancing and Delivery

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 44 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?

  1. A
    Deploy Azure Traffic Manager to route TCP connections directly to the virtual machines' Basic SKU public IP addresses.
  2. B
    Deploy an Azure Standard Load Balancer and associate the virtual machines' existing Basic SKU public IP addresses to its backend pool.
  3. Deploy an Azure Standard Load Balancer and upgrade the virtual machines' public IP addresses to Standard SKU.Answer
  4. D
    Deploy 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 44 (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

1
Analyze the traffic and routing requirements.
The application requires Layer 44 regional TCP load balancing and Availability Zones support without SSL/TLS termination or HTTP path-based routing.
This identifies Azure Load Balancer as the appropriate service, specifically the Standard SKU since Basic Load Balancer does not support Availability Zones.
2
Evaluate the existing virtual machine configurations.
The virtual machines have Basic SKU public IP addresses assigned to their network interfaces.
Azure Standard Load Balancer requires all public IP addresses associated with backend virtual machines to be of the Standard SKU to avoid configuration mismatch.
3
Formulate the final load balancer and IP address configuration.
An Azure Standard Load Balancer is selected, and the virtual machines' public IPs are upgraded to Standard SKU.
This ensures the configuration passes validation and satisfies the zone-redundancy and SKU compatibility requirements.

Key Concept

Azure Load Balancer SKU requirements and availability zone support.
Rate this question