SAP-C02 · Question #179
A company has implemented a global multiplayer gaming platform. The platform requires gaming clients to have reliable, low-latency access to the server infrastructure that is hosted on a fleet of…
The correct answer is A. Create a Network Load Balancer (NLB), and add the EC2 instances to a target group. For a gaming platform requiring low-latency TCP access with client IP address preservation, a Network Load Balancer is the optimal solution.
Question
A company has implemented a global multiplayer gaming platform. The platform requires gaming clients to have reliable, low-latency access to the server infrastructure that is hosted on a fleet of Amazon EC2 instances in a single AWS Region The gaming clients use a custom TCP protocol to connect to the server infrastructure. The application architecture requires client IP addresses to be available to the server software. Which solution meets these requirements?
Options
- ACreate a Network Load Balancer (NLB), and add the EC2 instances to a target group
- BUse an AWS Direct Connect gateway to connect multiple Direct Connect locations in different
- CCreate an accelerator in AWS Global Accelerator and configure the listener to point to a single
- DCreate an Application Load Balancer (ALB) and add the EC2 instances to a target group
How the community answered
(38 responses)- A84% (32)
- B5% (2)
- C8% (3)
- D3% (1)
Why each option
For a gaming platform requiring low-latency TCP access with client IP address preservation, a Network Load Balancer is the optimal solution.
A Network Load Balancer (NLB) operates at Layer 4 (TCP), inherently supporting custom TCP protocols, and critically, it preserves the client IP address for the backend targets, which meets the requirement for client IP visibility by the server software.
AWS Direct Connect Gateway provides private connectivity between on-premises and AWS, which is unrelated to load balancing client connections for an EC2-hosted application or preserving client IP addresses.
AWS Global Accelerator optimizes traffic globally and provides static IP addresses, but it doesn't intrinsically preserve client IP addresses for backend EC2 instances or offer Layer 4 load balancing capabilities directly in the same way an NLB does for this specific requirement in a single region.
An Application Load Balancer (ALB) operates at Layer 7 (HTTP/S) and terminates client connections, passing the client IP in the X-Forwarded-For header, but does not preserve the original client IP directly at the TCP layer, failing the requirement for client IP address availability to the server software.
Concept tested: Load balancer selection based on protocol and client IP preservation
Source: https://docs.aws.amazon.com/elasticloadbalancing/latest/network/network-load-balancers.html#how-nlbs-work
Community Discussion
No community discussion yet for this question.