Examkin

Question

Difficulty: Very hardApplication Load Balancing and Delivery

An enterprise is designing a regional load balancing and traffic delivery solution in Azure. The design must satisfy the following requirements:
1. Incoming public HTTP/S traffic must be routed based on the URL path: requests to `/search/*` must be forwarded to a Virtual Machine Scale Set, while requests to `/checkout/*` must be forwarded to a group of Dedicated Hosts.
2. SSL/TLS termination must be performed at the application routing boundary to decrypt traffic before reaching the backend VMs.
3. Internal database replication traffic on TCP port 6379 must be load-balanced across database virtual machines distributed across multiple Availability Zones for high availability.
4. The database virtual machines are currently configured with Basic SKU Public IP addresses for legacy remote access.

Which configuration should you select to satisfy all requirements and ensure successful deployment validation?

  1. Deploy an Azure Application Gateway for the HTTP/S traffic, and deploy a Standard Azure Load Balancer for the internal TCP traffic after upgrading the database virtual machines' Public IPs to the Standard SKU.Answer
  2. B
    Deploy an Azure Traffic Manager for the HTTP/S traffic, and deploy a Standard Azure Load Balancer for the internal TCP traffic while keeping the database virtual machines' Public IPs on the Basic SKU.
  3. C
    Deploy an Azure Application Gateway for the HTTP/S traffic, and deploy a Basic Azure Load Balancer for the internal TCP traffic to maintain compatibility with the database virtual machines' Basic SKU Public IPs.
  4. D
    Deploy an Azure Front Door for the HTTP/S traffic, and deploy a Standard Azure Load Balancer for the internal TCP traffic while keeping the database virtual machines' Public IPs on the Basic SKU.

Answer

Deploy an Azure Application Gateway for the HTTP/S traffic, and deploy a Standard Azure Load Balancer for the internal TCP traffic after upgrading the database virtual machines' Public IPs to the Standard SKU.
The correct configuration uses Azure Application Gateway for regional Layer 7 routing and SSL/TLS termination, combined with a Standard Azure Load Balancer to distribute internal database replication traffic across Availability Zones. To resolve the SKU mismatch validation error, the database virtual machines' Public IP addresses must be upgraded to the Standard SKU because Standard Load Balancer backend pools do not support virtual machines associated with Basic SKU Public IPs.

Step-by-Step Solution

1
Evaluate HTTP/S routing and decryption requirements.
The requirements for path-based routing (/search/* and /checkout/*) and SSL/TLS termination at the boundary dictate a Layer 7 load balancer. For regional workloads, Azure Application Gateway is the correct resource choice.
Layer 4 load balancers cannot inspect HTTP paths or terminate SSL sessions, and Azure Traffic Manager operates purely at the DNS level.
2
Evaluate internal database TCP load balancing and Availability Zone requirements.
The requirements specify load balancing of TCP port 6379 across Availability Zones. This requires a Standard Azure Load Balancer.
The Basic SKU Azure Load Balancer does not support Availability Zones, making the Standard SKU mandatory to fulfill the high availability requirement.
3
Address the deployment validation failure due to SKU mismatch.
Identify that the database virtual machines have Basic SKU Public IPs, which cannot coexist with a Standard Load Balancer's backend pool. The public IPs must be upgraded to the Standard SKU.
Azure prevents the mixing of Basic and Standard SKUs on resources connected to the same virtual machine network interfaces associated with a Load Balancer backend pool.

Key Concept

Integrating Azure Application Gateway and Standard Load Balancer while avoiding SKU mismatch validation errors
Rate this question

Topics

Application Load Balancing and Delivery

More questions from this topic