Question

Difficulty: MediumApplication Load Balancing and Delivery

An enterprise is designing a regional application architecture in West US 2. The solution requires hosting two distinct workloads on Azure Virtual Machines:

1. A web application backend that requires SSL/TLS termination, URL-path-based routing, and cookie-based session affinity.
2. A high-throughput legacy database backend that communicates over a custom TCP port and requires layer 4 load balancing.

The virtual machines for both workloads will be deployed across multiple Availability Zones. Currently, the legacy database virtual machines have Basic SKU Public IP addresses assigned to their network interfaces.

You need to design a load balancing solution that meets these requirements while ensuring successful deployment validation.

Which of the following actions should you perform? (Select TWO.)

  1. Deploy Azure Application Gateway Standard v2 to route traffic to the web application backend.Answer
  2. Deploy a Standard SKU Azure Load Balancer for the legacy database backend, and either upgrade the database virtual machines' Public IP addresses to Standard SKU or remove them.Answer
  3. C
    Deploy Azure Traffic Manager to manage URL-path-based routing and SSL/TLS termination for the web application backend.
  4. D
    Deploy a Basic SKU Azure Load Balancer to load balance the legacy database backend to support the existing Basic SKU Public IP addresses.

Answer

Deploy Azure Application Gateway Standard v2 to route traffic to the web application backend, and deploy a Standard SKU Azure Load Balancer for the legacy database backend while either upgrading the database virtual machines' Public IP addresses to Standard SKU or removing them.
To satisfy the layer 7 HTTP/HTTPS features (SSL/TLS termination, path-routing, session affinity) and high availability across Availability Zones, Azure Application Gateway Standard v2 is the correct choice. For the layer 4 TCP database traffic requiring Availability Zones, a Standard SKU Azure Load Balancer is needed. However, because the backend VMs currently have Basic SKU Public IP addresses, those IP addresses must be upgraded to Standard SKU or disassociated to avoid validation errors when adding the VMs to the Standard Load Balancer backend pool.

Step-by-Step Solution

1
Analyze the requirements for the web application backend.
Identify that SSL/TLS termination, URL-path-based routing, and cookie-based affinity are layer 7 HTTP/HTTPS features, which are natively supported by Azure Application Gateway Standard v2.
This determines the correct load balancer type for the first workload.
2
Analyze the requirements for the legacy database backend.
Identify that layer 4 TCP load balancing and Availability Zone support are required, which points to a Standard SKU Azure Load Balancer.
This determines the correct load balancer type for the second workload.
3
Check compatibility between the existing virtual machine configurations and the selected load balancer SKU.
Recognize that the legacy database virtual machines currently use Basic SKU Public IPs, which cannot be mixed with a Standard SKU Load Balancer.
To prevent validation failures, the Public IPs on the virtual machines' network interfaces must be upgraded to Standard SKU or disassociated.

Key Concept

Selecting the appropriate Azure load balancing services based on layer, protocol, and SKU compatibility constraints.
Rate this question