Examkin

Soru

Zorluk: ZorApplication Load Balancing and Delivery

A logistics enterprise is designing a regional application architecture in the East US region. The system includes two distinct components:
1. A fleet of backend Virtual Machines (VMs) that ingest raw TCP telemetry from package scanners on port 5001. The VMs are currently assigned Basic SKU Public IP addresses.
2. A web management application that requires SSL/TLS termination and URL path-based routing (e.g., routing '/api/*' and '/static/*' to different backend pools).

The enterprise requires a load balancing design that satisfies all protocol and routing requirements while ensuring compatibility with Azure SKU constraints.

Which load balancing architecture should you design for this application?

  1. Upgrade the Public IP addresses of the backend VMs to Standard SKU, deploy an Azure Standard Load Balancer to distribute the TCP telemetry traffic, and deploy an Azure Application Gateway (v2) to manage the web management application traffic.Cevap
  2. B
    Deploy an Azure Standard Load Balancer to distribute the TCP telemetry traffic to the VMs using their existing Basic SKU Public IPs, and deploy an Azure Application Gateway (v2) to manage the web management application traffic.
  3. C
    Upgrade the Public IP addresses of the backend VMs to Standard SKU, deploy an Azure Standard Load Balancer to distribute the TCP telemetry traffic, and deploy an Azure Traffic Manager to manage the SSL/TLS termination and URL path-based routing for the web management application.
  4. D
    Deploy an Azure Standard Load Balancer to distribute the TCP telemetry traffic to the VMs using their existing Basic SKU Public IPs, and deploy an Azure Traffic Manager to manage the SSL/TLS termination and URL path-based routing for the web management application.

Cevap

Upgrade the Public IP addresses of the backend VMs to Standard SKU, deploy an Azure Standard Load Balancer to distribute the TCP telemetry traffic, and deploy an Azure Application Gateway (v2) to manage the web management application traffic.
The correct solution uses an Azure Standard Load Balancer for the Layer 4 TCP telemetry traffic and an Azure Application Gateway for the Layer 7 HTTPS web management traffic. To prevent validation errors, the Basic SKU Public IPs on the backend VMs must be upgraded to Standard SKU because Standard Load Balancers do not support backend VMs with Basic SKU IP configurations.

Adım Adım Çözüm

1
Identify the protocol requirements for both layers of the application.
The telemetry ingestion layer requires Layer 4 TCP load balancing on port 5001. The web management application requires Layer 7 features including SSL/TLS termination and path-based routing.
This establishes which load balancer types (Layer 4 vs Layer 7) are appropriate for each workload.
2
Select the appropriate Azure services for the load balancing requirements.
Azure Standard Load Balancer is selected for the Layer 4 TCP ingestion traffic, and Azure Application Gateway is selected for the regional Layer 7 HTTPS management traffic.
Standard Load Balancer handles high-throughput Layer 4 traffic, while Application Gateway provides the path routing and TLS termination required for the web application.
3
Analyze Azure SKU compatibility rules for the backend pool.
Backend VMs with Basic SKU Public IPs cannot be placed in the backend pool of a Standard Load Balancer.
Azure enforces that all network resources associated with a Standard Load Balancer backend pool must use Standard SKU IP addresses to prevent configuration mismatches.
4
Determine the necessary remediation to satisfy the SKU constraints.
The Public IPs of the backend VMs must be upgraded to Standard SKU to allow successful association with the Standard Load Balancer.
Upgrading the IPs resolves the SKU mismatch validation error.

Anahtar Kavram

Azure load balancing selection based on protocol support and SKU compatibility rules.
Bu soruyu puanla

Konular

Application Load Balancing and Delivery

Bu konudan daha fazla soru