Question

Difficulty: Very hardApplication Load Balancing and Delivery

A financial services firm is modernizing its payment processing platform by migrating key workloads to Azure. The architecture team is designing a load balancing and traffic delivery solution that must meet the following requirements:

* External client transactions over HTTPS must be routed globally to regional endpoints using path-based rules (e.g., routing `/process` and `/refund` requests to dedicated backend services) with SSL/TLS termination performed at the edge.
* The internal backend database tier, which communicates over TCP port 14331433, must be load-balanced regionally across virtual machines in a virtual network.
* The database virtual machines currently have legacy Basic SKU Public IP addresses assigned for administrative access.
* The solution must support high-availability configurations for all load balancers without validation or deployment failures.

Which architecture configuration should you recommend to meet these requirements?

  1. A
    Deploy Azure Traffic Manager to manage global HTTP/S routing and SSL/TLS termination. Upgrade the public IP addresses of the database virtual machines to Standard SKU, and deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic.
  2. Deploy Azure Front Door to manage global HTTP/S routing and SSL/TLS termination. Upgrade the public IP addresses of the database virtual machines to Standard SKU, and deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic.Answer
  3. C
    Deploy Azure Front Door to manage global HTTP/S routing and SSL/TLS termination. Deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic, keeping the database virtual machines' public IP addresses on the Basic SKU.
  4. D
    Deploy Azure Application Gateway to manage global HTTP/S routing and SSL/TLS termination. Deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic, keeping the database virtual machines' public IP addresses on the Basic SKU.

Answer

Deploy Azure Front Door to manage global HTTP/S routing and SSL/TLS termination. Upgrade the public IP addresses of the database virtual machines to Standard SKU, and deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic.
The correct architecture combines Azure Front Door for global HTTP/S delivery (providing edge SSL/TLS termination and path-based routing) with a Standard Azure Load Balancer to distribute the TCP port 14331433 database traffic within the region. Because Standard Load Balancers require all associated network interfaces and public IP addresses to use the Standard SKU, the legacy Basic SKU public IP addresses on the database virtual machines must be upgraded to Standard SKU to avoid validation failures.

Step-by-Step Solution

1
Analyze global HTTP/S routing requirements.
Identify that Azure Front Door is required for global routing, SSL/TLS termination, and path-based URL matching.
Azure Front Door is a global Layer 7 load balancer designed specifically for HTTP/S web traffic, whereas Traffic Manager only operates at the DNS level (Layer 4) and Application Gateway is regional.
2
Analyze regional database tier load balancing requirements.
Select Azure Load Balancer (Standard SKU) to handle the database traffic on TCP port 14331433.
Azure Load Balancer is a regional Layer 4 load balancer that handles TCP/UDP protocols, making it suitable for SQL Server database traffic.
3
Evaluate VM Public IP SKU compatibility with the selected Load Balancer.
Determine that the database virtual machines' public IP addresses must be upgraded from Basic SKU to Standard SKU.
Standard Load Balancers require all backend resources to use Standard SKU IP configurations. Mixing Basic SKU Public IPs with a Standard Load Balancer will cause a validation error.

Key Concept

Designing a multi-tier load balancing architecture using Azure Front Door and Standard Load Balancer while adhering to SKU alignment rules.
Rate this question