The Network Load Balancer (NLB) is the correct choice for balancing large volumes of TCP traffic because it operates at the OSI Layer 4 and makes routing decisions based on connection information rather than application payload.

The NLB is optimized for high throughput and low latency and it can scale to handle millions of TCP connections. The NLB routes on TCP or UDP connection details and can preserve client source IP addresses which helps with stateful workloads and direct client identification.

The Application Load Balancer (ALB) is not correct because it operates at OSI Layer 7 and routes based on HTTP and HTTPS request attributes such as headers and paths which do not meet a raw TCP balancing requirement.

The Classic Load Balancer (CLB) is not preferred because it is a legacy option and while it can handle both Layer 4 and Layer 7 traffic it lacks many of the newer features and optimizations that make the NLB the recommended Layer 4 choice for new architectures.

The AWS Global Accelerator is not an Elastic Load Balancer because it provides global anycast and traffic acceleration and routing rather than per connection Layer 4 load balancing within a region so it does not replace the NLB for this use case.

Full AWS Practitioner Certification Question