SAA-C03 Practice Question 66: NLB Static IP TCP
AWS Certified Solutions Architect – Associate (SAA-C03) · Test 7 · question 6 of 10
A manufacturer is moving its telemetry ingestion service into a VPC. Several hundred thousand already-deployed field devices connect to it over plain TCP on port 9443, wrap their own TLS inside that connection, and have the destination IP addresses burned into firmware that cannot be updated to use DNS. The ingest application must also see each device's real source IP address for geographic auditing, and the service peaks at millions of connections.
Which load balancing option should the architect choose?
Show answer and explanation
Answer:
A Network Load Balancer operates at layer 4 and can handle millions of requests per second, which covers the connection volume and the plain-TCP, application-managed-TLS protocol. It creates a network interface per enabled Availability Zone, and for an internet-facing load balancer you can associate one Elastic IP address per subnet, a fixed address the hard-coded firmware can keep using. With instance-ID or IP targets, client IP preservation means the application sees the device's real source address rather than the load balancer's.
Option B is the wrong layer. An Application Load Balancer only understands HTTP and HTTPS, so it cannot carry an opaque TCP stream on port 9443, and it has no static IP addresses; clients are expected to resolve its DNS name, which these devices cannot do.
Option C does solve the static address problem, since Global Accelerator provides fixed anycast IP addresses. It fails on the endpoint named in the option: an Application Load Balancer still cannot terminate a non-HTTP TCP protocol. Global Accelerator in front of a *Network* Load Balancer would work, but that is not what is offered.
Option D is a legacy load balancer that AWS no longer recommends for new designs. More concretely, it has no static IP addresses either (like an Application Load Balancer it is reached by DNS name), so the firmware constraint alone rules it out, whatever proxy protocol would do for the source address.
Reference: What is a Network Load Balancer?