Examkin

Question

Difficulty: HardApplication Load Balancing and Delivery

An enterprise is designing a high-throughput gaming backend in Azure. The backend consists of two main workloads:

1. A game-session matchmaking service that communicates over secure HTTP/S on port 443443, requiring SSL/TLS termination, URL path-based routing (e.g., routing `/match/*` to a specific pool), and SQL injection protection. This service is hosted on Azure Virtual Machines.
2. A real-time game telemetry receiver that processes high-frequency custom TCP packets on port 90009000. This receiver is deployed on a separate group of Azure Virtual Machines. The VMs hosting the telemetry receiver are pre-configured with Basic SKU public IP addresses on their network interfaces to allow direct, un-load-balanced administrator access for debugging.

The solution must meet the following requirements:
- Use a single, public entry point for the matchmaking service that is highly secure and supports path-based routing.
- Load-balance the telemetry receiver traffic across the telemetry VMs while ensuring that the current debugging configuration using Basic SKU public IPs remains functional.
- Avoid configuration validation errors due to SKU mismatches.

Which two actions should you perform to implement the load balancing architecture? (Select two.)

  1. Deploy an Azure Application Gateway v2 with a Standard SKU public IP address to load-balance the matchmaking service.Answer
  2. Deploy a Basic Load Balancer to load-balance the telemetry receiver traffic on port 90009000.Answer
  3. C
    Deploy a Standard Load Balancer to load-balance the telemetry receiver traffic on port 90009000 without modifying the VM IP configurations.
  4. D
    Deploy Azure Traffic Manager to load-balance the matchmaking service and manage SSL/TLS termination.
  5. E
    Deploy a Standard Load Balancer with a Basic SKU public IP to load-balance the telemetry receiver traffic.

Answer

Deploy an Azure Application Gateway v2 with a Standard SKU public IP address to load-balance the matchmaking service, and deploy a Basic Load Balancer to load-balance the telemetry receiver traffic on port 90009000.
Deploying an Azure Application Gateway v2 with a Standard SKU public IP successfully fulfills the Layer 7 matchmaking service needs, including WAF protection and path-based routing. Deploying a Basic Load Balancer satisfies the Layer 4 TCP requirement for the telemetry receiver while accommodating the legacy Basic SKU public IPs on the backend VMs, avoiding SKU mismatch validation errors.

Step-by-Step Solution

1
Analyze matchmaking service requirements
Identify that Layer 7 routing, SSL/TLS termination, and WAF protection are required, pointing to Azure Application Gateway v2 with a Standard SKU public IP.
Application Gateway v2 operates at Layer 7 and integrates WAF features, but strictly requires Standard SKU public IPs.
2
Analyze telemetry receiver requirements and constraints
Identify that Layer 4 TCP load balancing is required, and the target VMs must retain their Basic SKU public IPs.
The custom protocol runs on TCP port 90009000, necessitating a Layer 4 load balancer.
3
Evaluate SKU compatibility for the telemetry receiver load balancer
Determine that a Standard Load Balancer cannot be used because it is incompatible with backend VMs that have Basic SKU public IPs on their NICs, meaning a Basic Load Balancer is the correct choice.
Mixing Standard Load Balancer with Basic SKU public IP configurations on VM network interfaces leads to deployment validation errors.

Key Concept

Azure load balancing SKU constraints and Layer 4 vs Layer 7 load balancer capabilities
Estimated Time:2m 30s
Rate this question

Topics

Application Load Balancing and Delivery

More questions from this topic