An enterprise is deploying an internal backend microservice hosted on Compute Engine instances across multiple zones within a single Virtual Private Cloud (VPC) network. The microservice receives raw TCP RPC requests directly from other internal workloads. The network architecture requires an internal load balancing mechanism that provides high availability, supports TCP health checks, and preserves the original client IP addresses without proxying or performing Layer 7 inspection. Which Google Cloud load balancing solution should you choose?
- Internal Passthrough Network Load BalancerCevap
- BGlobal External HTTP(S) Load Balancer
- CExternal SSL Proxy Load Balancer
- DInternal Application Load Balancer
Cevap
The Internal Passthrough Network Load Balancer is the correct choice because it provides regional, Layer 4 internal load balancing for TCP/UDP traffic without proxying, preserving the original client source IP addresses.
The Internal Passthrough Network Load Balancer is built on Andromeda network virtualization. It distributes internal Layer 4 (TCP/UDP) traffic among instances in the same region within a VPC. Because it is non-proxied (passthrough), packets arrive at the backend virtual machines with the source client IP intact, matching all workload requirements.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Load Balancers based on Traffic Scope (Internal vs External), OSI Layer (L4 vs L7), and Proxy Behavior (Passthrough vs Proxy)
Tahmini Süre:1m 30s