Examkin

Question

Difficulty: HardApplication Load Balancing and Delivery

An IoT manufacturing enterprise is deploying a regional telematics processing solution in Azure. The architecture contains two main services:

1. An HTTP/HTTPS dashboard API that requires path-based routing (routing `/telemetry/*` to a hot-path processing pool and `/reports/*` to a cold-path pool) and SSL/TLS termination at the gateway.
2. A raw TCP receiver service running on port 5001 that processes stream data directly from hardware sensors.

The design requires zone-redundancy and high availability across three Availability Zones. The virtual machines hosting the TCP receiver service currently use Basic SKU Public IP addresses to support direct remote debugging over the internet.

Which load balancing configuration should you recommend to meet these requirements?

  1. Deploy an Azure Application Gateway Standard v2 for the HTTP/HTTPS dashboard API. Upgrade the public IP addresses of the TCP receiver virtual machines to Standard SKU, and deploy a Standard Load Balancer to distribute the TCP traffic.Answer
  2. B
    Deploy an Azure Application Gateway Standard v2 for the HTTP/HTTPS dashboard API. Deploy a Standard Load Balancer to distribute the TCP traffic to the receiver virtual machines, retaining their existing Basic SKU Public IP addresses.
  3. C
    Deploy Azure Traffic Manager to manage SSL/TLS termination and path-based routing for the HTTP/HTTPS dashboard API. Upgrade the public IP addresses of the TCP receiver virtual machines to Standard SKU, and deploy a Standard Load Balancer to distribute the TCP traffic.
  4. D
    Deploy an Azure Application Gateway Standard v2 for the HTTP/HTTPS dashboard API. Deploy a Standard Load Balancer to distribute the TCP traffic, but locate all TCP receiver virtual machines within a single Availability Zone to bypass public IP SKU limitations.

Answer

Deploy an Azure Application Gateway Standard v2 for the HTTP/HTTPS dashboard API, upgrade the public IP addresses of the TCP receiver virtual machines to Standard SKU, and deploy a Standard Load Balancer to distribute the TCP traffic.
The recommended design uses Azure Application Gateway Standard v2 for the regional HTTP/HTTPS path-based routing and SSL/TLS termination, and a Standard Load Balancer for the Layer 4 TCP receiver service. To prevent validation failures, the virtual machines' public IPs must be upgraded to Standard SKU because Standard Load Balancer backend pools do not support Basic SKU public IPs.

Step-by-Step Solution

1
Select the load balancer for the Layer 7 web traffic.
Azure Application Gateway Standard v2 is chosen because it supports regional zone redundancy, path-based routing, and SSL/TLS termination.
The dashboard API requires path-based routing (/telemetry/* and /reports/*) and SSL termination at the gateway level.
2
Select the load balancer for the Layer 4 TCP receiver traffic.
Standard Load Balancer is chosen over Basic Load Balancer.
The TCP service must support high availability across three Availability Zones, which requires a Standard SKU Load Balancer since Basic Load Balancer does not support zone-redundancy.
3
Address backend SKU compatibility requirements.
All VM instance-level Public IPs in the backend pool must be upgraded to Standard SKU.
Standard Load Balancers fail validation if associated with virtual machines that have Basic SKU Public IP addresses.

Key Concept

Designing a co-existing Layer 7 (Application Gateway) and Layer 4 (Standard Load Balancer) regional solution with proper SKU alignment for public-facing virtual machines across Availability Zones.
Rate this question

Topics

Application Load Balancing and Delivery

More questions from this topic