What is the primary consideration when choosing between an Application Load Balancer and a Network Load Balancer for a real-time gaming application?

Question

Options

• AThe game's color scheme and graphics
• BThe need for static IP addresses
• CThe ability to handle UDP traffic
• DThe game's soundtrack quality

• A
  5% (1)
• B
  11% (2)
• C
  79% (15)
• D
  5% (1)

Explanation

Why C is correct: Real-time gaming applications frequently rely on UDP (User Datagram Protocol) for low-latency communication - things like player position updates, game state sync, and voice chat. Network Load Balancers (NLB) support UDP traffic, while Application Load Balancers (ALB) operate only at Layer 7 (HTTP/HTTPS) and cannot handle UDP at all, making NLB the correct choice for this use case.

Why the distractors are wrong:

• A (color scheme/graphics) and D (soundtrack quality) are nonsense distractors - load balancers handle network traffic routing and have zero involvement in a game's visual or audio assets.
• B (static IP addresses) is a real NLB feature, but it's not the primary consideration for real-time gaming - UDP support is the functional requirement that forces the choice.

Memory tip: Think Network Load Balancer = Not just HTTP - it handles raw TCP/UDP traffic. If your app speaks anything other than HTTP/HTTPS, NLB is your answer. For gaming, the telltale keyword is "real-time" + UDP.

No community discussion yet for this question.