QuestionQ139

VerifiedPlanning and implementing a cloud solution

You deployed an application on a managed instance group in Compute Engine. The application accepts Transmission Control Protocol (TCP) traffic on port 389 and requires you to preserve the IP address of the client who is making a request. You want to expose the application to the internet by using a load balancer. What should you do?

Explanation

An external passthrough Network Load Balancer is not a proxy: backend VMs receive load-balanced packets with the original source and destination IP addresses, so the application sees the client's IP address, and it load balances traffic that comes from clients on the internet. Google recommends choosing a passthrough Network Load Balancer to preserve client source IP addresses. An external proxy Network Load Balancer with a TCP proxy (B) terminates connections at the load balancer and by default does not preserve the original client IP address and port; you would have to enable the PROXY protocol. The SSL proxy variant (C) has the same limitation and is meant for offloading SSL/TLS, which this plain TCP application doesn't need. An internal passthrough Network Load Balancer (D) uses an internal IP address that is accessible only to systems in the same VPC network, so it cannot expose the application to the internet.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!