GCP Associate Cloud Engineer Practice Question 64: Internal TCP Tier Load Balancer
Google Cloud Associate Cloud Engineer · Test 7 · question 4 of 10
A three-tier application runs entirely inside a single VPC in one region. The application tier communicates with a backend tier over a custom TCP protocol on port 9000, not HTTP or HTTPS. All of this traffic must stay private within the VPC, and no client outside the project should ever be able to reach the backend tier. You need to load balance the TCP connections across a managed instance group of backend VMs while preserving the client's source IP address at the backend.
Which load balancer should you configure?
Show answer and explanation
Answer:
An internal passthrough Network Load Balancer is a regional load balancer with an internal IP address that is reachable only from within the VPC (or connected networks). It operates at the transport layer, so it load balances any TCP or UDP traffic, not just HTTP or HTTPS, and because it is a passthrough load balancer rather than a proxy, the original client source IP is preserved all the way to the backend VM.
Option A is wrong because an external Application Load Balancer always has an internet-facing frontend, even if its backend is marked internal, so it does not keep the traffic private end to end, and it is also a Layer 7 HTTP(S) load balancer, which cannot forward a custom TCP protocol. Option B is wrong for the same protocol reason: an internal Application Load Balancer parses HTTP requests and routes on URL paths, which has no meaning for a raw TCP stream on port 9000. Option D is wrong because an external proxy Network Load Balancer terminates connections at Google's edge and provisions a public IP address; restricting access with a firewall rule limits who can send traffic but does not make the load balancer itself internal, and as a proxy it also replaces the client's source IP with its own.
Reference: Internal passthrough Network Load Balancer overview