Examkin

Question

Difficulty: HardApplication Load Balancing and Delivery

A healthcare provider is designing the regional application delivery and load balancing architecture in East US 2 for a new clinical portal. The solution must meet the following requirements:
- The public-facing web application requires SSL/TLS termination and path-based routing (traffic for `/patients/*` and `/staff/*` must be routed to separate backend pools).
- The database synchronization layer requires high-throughput TCP connections on custom port 50005000.
- All database virtual machines currently use Basic SKU Public IP addresses for administration.
- To comply with strict data sovereignty regulations, all load balancing and traffic routing components must reside entirely within the East US 2 region.

Which load balancing configuration should you recommend?

  1. Deploy an Azure Application Gateway (Standard v2) for the web application, deploy an Azure Standard Load Balancer for the database layer, and upgrade the database virtual machines' public IP addresses to the Standard SKU.Answer
  2. B
    Deploy an Azure Application Gateway (Standard v2) for the web application, deploy an Azure Standard Load Balancer for the database layer, and retain the Basic SKU public IP addresses on the database virtual machines.
  3. C
    Deploy an Azure Traffic Manager profile to handle SSL/TLS termination and path-based routing for the web application, and deploy an Azure Standard Load Balancer for the database layer after upgrading the database virtual machines' public IP addresses to the Standard SKU.
  4. D
    Deploy an Azure Front Door Premium profile to manage both the web application and the database layer TCP connections on port 50005000 using path-based routing rules.

Answer

Deploy an Azure Application Gateway (Standard v2) for the web application, deploy an Azure Standard Load Balancer for the database layer, and upgrade the database virtual machines' public IP addresses to the Standard SKU.
The correct configuration uses Azure Application Gateway (Standard v2) to satisfy the layer-7 features (SSL/TLS termination and path-based routing) for the web application. It uses Azure Standard Load Balancer to load balance the custom TCP traffic on port 50005000 for the database layer. Finally, it upgrades the database virtual machines' public IP addresses to the Standard SKU to resolve the SKU mismatch validation error that occurs when mixing Basic SKU public IPs with a Standard Load Balancer.

Step-by-Step Solution

1
Analyze the web application requirements.
The web application requires SSL/TLS termination and regional path-based routing (`/patients/*` and `/staff/*`), which requires a regional layer-7 load balancer like Azure Application Gateway.
Azure Application Gateway operates at layer 7 and supports SSL offloading and URL-based routing rules.
2
Analyze the database synchronization requirements.
The database layer requires high-throughput TCP load balancing on port 50005000, which requires a regional layer-4 load balancer like Azure Standard Load Balancer.
Azure Standard Load Balancer provides low-latency, high-throughput Layer 4 load balancing for TCP/UDP protocols on arbitrary ports.
3
Verify SKU compatibility requirements.
The database virtual machines' public IP addresses must be upgraded from Basic to Standard SKU.
Azure Standard Load Balancer requires all backend network interfaces to have Standard SKU public IPs (or no public IPs). Mixing Basic and Standard SKUs in this load balancer configuration is not supported.

Key Concept

Selecting and configuring regional Azure load balancing services (Application Gateway and Standard Load Balancer) while ensuring SKU compatibility for backend pools.
Rate this question

Topics

Application Load Balancing and Delivery

More questions from this topic