Globally distributed users experience slow SMTP and IMAP. End-to-end encryption is required but you cannot access SSL certificates. Which Google Cloud load balancer should you use?

The TCP proxy load balancer is the correct choice because it supports end-to-end encryption without requiring you to manage SSL certificates. It terminates the client-side TCP connection and then establishes a new connection to the backend, allowing for SSL offloading or passthrough depending on configuration. This is ideal for protocols like SMTP and IMAP where encryption is needed but certificate management is not feasible on the load balancer itself. The SSL proxy load balancer is incorrect because it requires you to provide and manage SSL certificates for decryption at the load balancer. The Network load balancer is incorrect as it is a pass-through load balancer at Layer 4 and does not terminate connections or provide encryption capabilities. The HTTPS load balancer is incorrect because it is designed for HTTP/S traffic (Layer 7) and requires SSL certificates for its operation.