Examkin

Soru

Zorluk: ZorApplication Load Balancing and Delivery

An enterprise is modernizing a media streaming platform in Azure. The system consists of two primary endpoints:

1. A management API endpoint that receives HTTP/HTTPS control messages on port 443. The API requires URL path-based routing (e.g., `/stream/start` vs `/stream/stop`) and SSL/TLS termination.
2. A real-time video stream ingestion endpoint that receives continuous UDP traffic on port 8080.

The backend virtual machines (VMs) processing both workloads are deployed within a Virtual Machine Scale Set (VMSS) across multiple Availability Zones for high availability. To reduce costs, the networking team proposes deploying:

* An Azure Application Gateway (Standard v2) to load balance the HTTP/HTTPS management API.
* A Basic SKU Azure Load Balancer to load balance the UDP streaming traffic.

Why will the proposed load balancing configuration fail to deploy?

  1. A
    The proposed design must replace the Application Gateway with Azure Traffic Manager to perform the URL path-based routing and SSL/TLS termination at the global level.
  2. The virtual machine scale set instances cannot be associated with both the Standard SKU Application Gateway and the Basic SKU Load Balancer backend pools simultaneously, as mixing Basic and Standard SKU load balancing resources on the same network interfaces is not supported.Cevap
  3. C
    The backend virtual machine scale set instances must be consolidated into a single Availability Zone because Application Gateway Standard v2 cannot distribute traffic to zone-redundant backend pools.
  4. D
    The configuration requires a custom User Defined Route (UDR) to redirect the UDP traffic through the Application Gateway subnet, which will override default system routes and cause a network routing loop.

Cevap

The virtual machine scale set instances cannot be associated with both the Standard SKU Application Gateway and the Basic SKU Load Balancer backend pools simultaneously, as mixing Basic and Standard SKU load balancing resources on the same network interfaces is not supported.
The correct answer states that the virtual machine scale set instances cannot belong to both a Standard SKU resource (Application Gateway v2) and a Basic SKU Load Balancer backend pool at the same time. Azure enforces strict SKU isolation at the network interface (NIC) level, meaning all load balancers or application gateways attached to a VM's NIC must share the same SKU level (Standard or Basic). Mixing SKUs results in deployment validation failures.

Adım Adım Çözüm

1
Analyze the protocol and routing requirements for both endpoints.
The management API requires Layer 7 routing (HTTP/HTTPS, path-based routing, SSL termination), making Azure Application Gateway appropriate. The streaming ingest requires Layer 4 routing (UDP on port 8080), which requires Azure Load Balancer.
Application Gateway does not support UDP traffic, necessitating a separate Layer 4 load balancer.
2
Assess the SKU compatibility rules for Azure Load Balancer and Application Gateway.
Application Gateway Standard v2 functions as a Standard SKU resource. The proposed Load Balancer is a Basic SKU resource. Registering the same virtual machine network interfaces to backend pools of different SKUs violates SKU isolation policies.
Azure prevents registering a network interface card (NIC) to a mix of Basic and Standard SKU load balancing resources.
3
Identify the necessary remediation steps.
Upgrade the Basic SKU Load Balancer to a Standard SKU Load Balancer.
Using a Standard Load Balancer aligns the SKU level with the Application Gateway Standard v2, resolving the validation failure while supporting the zone-redundant backend VM configuration.

Anahtar Kavram

Load Balancer SKU compatibility and co-existence constraints
Tahmini Süre:2m 30s
Bu soruyu puanla

Konular

Application Load Balancing and Delivery

Bu konudan daha fazla soru