Deploying a global external TCP load balancer and you need to preserve the original source IP at layer 3. Which load balancer type should you use?

The TCP/SSL Proxy Load Balancer is the correct choice because it's a global external load balancer that operates at Layer 4 (TCP/SSL) and is specifically designed to preserve the original client IP address. This is crucial for logging, analytics, and security policies that rely on source IP information. The HTTP(S) load balancer operates at Layer 7 and proxies connections, meaning it terminates the client connection and establishes a new one to the backend, thus losing the original source IP by default (though it can be forwarded in an X-Forwarded-For header, it's not the Layer 3 preservation requested). The Network Load Balancer (now referred to as an External Passthrough Network Load Balancer) is a regional, not global, load balancer and passes traffic directly to backend VMs, but it's not a proxy. The Internal Load Balancer is for internal traffic within a VPC network, not external global traffic.