You need a private, cross-zone internal load balancer with a single private IP that distributes TCP traffic to GKE backends in multiple zones. Which Google Cloud load balancer should you use?

The Regional Internal TCP/UDP Load Balancer is the correct choice because it is designed for internal, private IP load balancing within a region, distributing TCP/UDP traffic. It supports backends across multiple zones within that region, fulfilling the cross-zone requirement. It also provides a single private IP address for the load balancer frontend. The Zonal Internal HTTP(S) Load Balancer is incorrect because it is an HTTP(S) load balancer, not suitable for generic TCP traffic, and it is zonal, not cross-zone. An External HTTP(S) Load Balancer with a private IP is incorrect because it's an external load balancer, typically used for internet-facing services, even if configured with a private IP. Cloud Router-based load distribution is incorrect as Cloud Router is primarily for connecting on-premises networks to Google Cloud and for BGP routing, not for internal application load balancing.