Question

Difficulty: MediumApplication Load Balancing and Delivery

An organization is designing a regional load balancing solution for a web application in the West US 2 region. The application runs on Azure Virtual Machines that require direct inbound Internet access for administrative tasks and are configured with Basic SKU public IP addresses. The new load balancer must meet the following requirements:
- Distribute traffic within the West US 2 region only.
- Support SSL/TLS termination at the load balancer level.
- Route requests to different backend pools based on the URL path.
- Avoid configuration or validation errors when integrating with the existing virtual machines.

Which load balancing solution should you design?

  1. Azure Application Gateway (Standard v2) configured to target the backend virtual machines using their private IP addresses.Answer
  2. B
    Azure Standard Load Balancer configured with backend pools containing the virtual machines.
  3. C
    Azure Traffic Manager configured to route traffic based on the URL path to the virtual machines.
  4. D
    Azure Application Gateway (Standard v2) configured with a Basic SKU public IP address as its frontend.

Answer

Azure Application Gateway (Standard v2) configured to target the backend virtual machines using their private IP addresses.
Azure Application Gateway (Standard v2) is a regional Layer 7 load balancer that supports SSL/TLS termination and URL path-based routing. By configuring the backend pool to target the virtual machines' private IP addresses, the application gateway bypasses any configuration or validation conflicts related to the Basic SKU public IP addresses on the virtual machines' network interfaces.

Step-by-Step Solution

1
Analyze the protocol and routing requirements.
The solution requires Layer 7 capabilities (SSL/TLS termination and URL path-based routing). This rules out Layer 4 load balancers (Azure Load Balancer) and DNS-based routing (Azure Traffic Manager).
SSL/TLS termination and URL-based routing are application-layer features.
2
Analyze the regional and SKU constraints.
The solution must be regional, which points to Azure Application Gateway. The backend VMs have Basic SKU public IPs. To avoid SKU mismatch validation errors, the load balancer should communicate with the VMs using their private IP addresses.
Standard SKU load balancing resources cannot be associated directly with Basic SKU public IP resources on the same network interfaces.
3
Select the compliant Azure load balancing service and configuration.
Configure Azure Application Gateway (Standard v2) with a Standard SKU public IP for its frontend and reference the backend VMs using their private IP addresses.
This configuration satisfies all Layer 7 requirements, regional scope, and avoids SKU mismatch conflicts.

Key Concept

Selecting the appropriate regional Layer 7 load balancer (Application Gateway) and avoiding SKU mismatches by utilizing private IP backend routing.
Rate this question