Examkin

Question

Difficulty: HardApplication Load Balancing and Delivery

An enterprise is modernizing a global HR SaaS application. The application consists of two main tiers:

1. A web application tier (HTTP/HTTPS) that requires SSL/TLS termination, URL path-based routing (e.g., routing `/benefits/*` and `/payroll/*` to different backend pools), and global optimization to route users to the closest region (either East US or West Europe).
2. A background data-sync tier that communicates using a custom TCP protocol on port 9090, requiring high-throughput regional layer 4 load balancing in the East US region.

The existing virtual machines for the background data-sync tier in East US are configured with Basic SKU Public IP addresses.

You need to design the application load balancing and delivery solution to meet these requirements while preventing configuration validation errors.

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

  1. Deploy Azure Front Door to route global HTTP/HTTPS traffic, terminate SSL, and perform URL path-based routing for the web application tier.Answer
  2. B
    Deploy Azure Traffic Manager to route global HTTP/HTTPS traffic, terminate SSL, and perform URL path-based routing for the web application tier.
  3. Deploy a Standard Load Balancer to distribute the custom TCP traffic for the background data-sync tier, and upgrade the background VMs' Public IPs to Standard SKU.Answer
  4. D
    Deploy a Standard Load Balancer to distribute the custom TCP traffic for the background data-sync tier, while retaining the existing Basic SKU Public IPs on the background VMs.

Answer

To meet the global routing, path-based routing, and SSL termination requirements for the HTTP/S web application tier, Azure Front Door is the appropriate service. For the regional TCP-based background data-sync tier, a Standard Load Balancer must be used; however, to prevent SKU mismatch validation errors, the associated virtual machines' Public IPs must be upgraded from Basic to Standard SKU.
The correct recommendations are to deploy Azure Front Door for the web tier and deploy a Standard Load Balancer for the background tier while upgrading the background virtual machines' Public IPs to the Standard SKU. Azure Front Door satisfies all global layer 7 requirements, including SSL termination, path-based routing, and global user optimization. The Standard Load Balancer handles regional TCP load balancing on port 9090. Upgrading the virtual machines' Public IPs to Standard SKU is necessary because Standard Load Balancers do not support backend resources with Basic SKU Public IPs, preventing configuration validation failures.

Step-by-Step Solution

1
Analyze the requirements for the global web application tier.
Identify that global load balancing, HTTP/S protocol support, SSL/TLS termination, and URL path-based routing are required.
These layer 7 and global routing requirements point directly to Azure Front Door, as it manages global HTTP/S traffic with path routing and SSL offloading.
2
Analyze the requirements for the regional background data-sync tier.
Identify that regional load balancing on a custom TCP port (9090) is required.
A layer 4 load balancer is needed. Azure Load Balancer (Standard SKU) is the correct choice to handle non-HTTP/S TCP traffic regionally.
3
Evaluate the SKU compatibility for the regional load balancer configuration.
Identify that the existing virtual machines have Basic SKU Public IPs, which cannot be associated with a Standard Load Balancer backend pool.
To avoid a validation error caused by mixing Basic and Standard SKUs, the Public IPs on the background virtual machines must be upgraded to Standard SKU.

Key Concept

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

Topics

Application Load Balancing and Delivery

More questions from this topic