A real-time multiplayer game needs millions of concurrent TCP connections at ultra-low latency, with a static IP for whitelisting. Which load balancer fits?
A.Application Load Balancer
ALB handles HTTP/WebSocket with path/host routing — it terminates at L7 and doesn't fit raw TCP at this scale.
B.Network Load Balancer
Correct. L4, massive connection count, static IPs.
C.Classic Load Balancer
Classic LB is legacy — fewer features, no static IP, weaker performance.
D.API Gateway
API Gateway fronts API requests, not raw TCP game traffic.
Why this answer
NLB operates at Layer 4: millions of connections/sec, ultra-low latency, static IP per AZ, source-IP preservation. ALB is for HTTP(S) L7 routing rules — the game protocol is raw TCP.
Correct answer: B · Last reviewed 2026-11-01
Official AWS references
Practice this interactively
Answer without seeing the solution first in the Compute Selection practice session.
Practice Compute Selection