For an internet-facing standard VoIP application requiring low-latency TCP/UDP passthrough, which GCP load balancer type should you use?

The Network Load Balancer is the correct choice because it is a pass-through load balancer that supports both TCP and UDP traffic, making it ideal for VoIP applications that require low-latency, direct handling of these protocols. It operates at Layer 4 and preserves the client's IP address, which is often crucial for VoIP session management. The HTTP(S) Load Balancer operates at Layer 7 and is designed for HTTP/S traffic, not raw TCP/UDP. The Internal TCP/UDP Load Balancer is for internal-only traffic, not internet-facing applications. The TCP/SSL Proxy Load Balancer terminates TCP/SSL connections at the load balancer, which introduces latency and is not a pass-through solution suitable for the direct, low-latency requirements of standard VoIP.