GCP Associate Cloud Engineer Practice Question 94: Passthrough NLB UDP Preserve IP
Google Cloud Associate Cloud Engineer · Test 10 · question 4 of 10
A media streaming backend accepts UDP traffic on port 5004 from clients on the public internet. The backend VMs run in a single region behind a managed instance group. The application logs and rate-limits based on the client's real IP address, so the original source IP must reach the VM unchanged. You need a Google Cloud load balancer that accepts internet traffic and distributes these UDP flows across the instance group.
Which load balancer should you use?
Show answer and explanation
Answer:
An external passthrough Network Load Balancer operates at the transport layer and forwards TCP or UDP packets directly to backend VMs without terminating the connection, so the client's original source IP address is preserved. It also accepts traffic from the public internet, which this workload requires.
Option A is wrong because Application Load Balancers work at Layer 7 over HTTP(S) and do not support UDP traffic at all. Option C is wrong because a proxy Network Load Balancer supports only TCP, not UDP, and being a proxy it terminates the connection and replaces the client's source IP with its own address when forwarding to the backend. Option D is wrong because an internal passthrough Network Load Balancer only has an internal IP address reachable from within the VPC (or connected networks); it cannot accept traffic directly from internet clients, and Private Service Connect is used to expose a service to other VPCs, not to the public internet.
Reference: External passthrough Network Load Balancer overview