Examkin

Question

Difficulty: Very hardApplication Load Balancing and Delivery

A logistics corporation is migrating a core ERP and dispatch system to Azure. The system has two distinct components:
1. An HTTP/HTTPS web application that requires cookie-based session affinity, SSL/TLS termination at the load balancer, and routing traffic to different backend pools based on the URL path.
2. A high-throughput database replication service that communicates over a custom TCP port 1445 and requires regional high availability.

All backend virtual machines (VMs) for both components are deployed within a single virtual network in the North Europe region. The VMs are currently associated with Basic SKU Public IP addresses. The entire load balancing architecture must support availability zones for zone redundancy and must not trigger deployment validation failures.

Which configuration should you recommend to meet these requirements?

  1. A
    Deploy an Azure Traffic Manager profile to handle routing, SSL termination, and session affinity for the web application, and deploy a Standard Load Balancer for the database replication service. Retain the existing Basic SKU Public IP addresses on the virtual machines.
  2. Deploy a Standard v2 Application Gateway for the web application, and deploy a Standard Load Balancer for the database replication service. Upgrade the existing Basic SKU Public IP addresses on the virtual machines to Standard SKU Public IP addresses.Answer
  3. C
    Deploy a Standard v2 Application Gateway for the web application, and deploy a Standard Load Balancer for the database replication service. Retain the existing Basic SKU Public IP addresses on the virtual machines.
  4. D
    Deploy a Standard v2 Application Gateway for the web application, and deploy a Basic Load Balancer for the database replication service. Retain the existing Basic SKU Public IP addresses on the virtual machines.

Answer

Deploy a Standard v2 Application Gateway for the web application, and deploy a Standard Load Balancer for the database replication service. Upgrade the existing Basic SKU Public IP addresses on the virtual machines to Standard SKU Public IP addresses.
The correct architecture uses a Standard v2 Application Gateway to satisfy the Layer 7 requirements (cookie affinity, SSL termination, path-based routing) and a Standard Load Balancer for the custom TCP port 1445 traffic. Both services support availability zones. To avoid validation failures, the existing Basic SKU Public IPs on the backend VMs must be upgraded to Standard SKU to match the Standard Load Balancer requirement.

Step-by-Step Solution

1
Analyze the web application requirements.
Identify that cookie-based session affinity, SSL/TLS termination, and path-based routing require a Layer 7 load balancer. In Azure, this is addressed by Azure Application Gateway.
Layer 4 balancers cannot read HTTP headers, cookies, or URL paths.
2
Analyze the database replication service requirements.
Identify that custom TCP port 1445 load balancing requires a Layer 4 load balancer, which is addressed by Azure Load Balancer.
Application Gateway only supports HTTP, HTTPS, HTTP/2, and WebSocket protocols, not raw custom TCP ports.
3
Evaluate the resiliency and SKU constraint requirements.
To support Availability Zones, Standard v2 Application Gateway and Standard Load Balancer must be selected. Basic SKUs do not support zonal redundancy.
Zonal and zone-redundant deployments are exclusive features of Standard SKU load balancing resources.
4
Check VM IP configurations for SKU compatibility.
Note that backend VMs associated with a Standard Load Balancer backend pool must use Standard SKU Public IPs or no Public IPs. Thus, the Basic SKU Public IPs on the VMs must be upgraded to Standard SKU.
Mixing Basic and Standard SKUs in a Load Balancer backend pool triggers a validation failure.

Key Concept

Azure Load Balancer and Application Gateway SKU integration constraints
Estimated Time:3m 0s
Rate this question

Topics

Application Load Balancing and Delivery

More questions from this topic