An organization is deploying a global gaming application on Google Cloud that uses a custom binary non-HTTP protocol over TCP. Clients worldwide must connect to the service with encrypted TLS sessions. To minimize latency, the solution must terminate TLS at Google's global edge network using Google-managed SSL certificates and distribute the decrypted raw TCP traffic to backend Compute Engine instance groups located in multiple regions. Which load balancing architecture should you recommend to meet these requirements?
- Configure a Global External Proxy Network Load Balancer with an SSL proxy target proxy and backend services in each region.Cevap
- BConfigure a Global External Application Load Balancer with an HTTPS target proxy and instance group backends.
- CConfigure an External Passthrough Network Load Balancer with target pools configured in each destination region.
- DConfigure an Internal Passthrough Network Load Balancer integrated with Cloud DNS geolocation routing policies.
Cevap
Configure a Global External Proxy Network Load Balancer with an SSL proxy target proxy and backend services in each region.
The Global External Proxy Network Load Balancer configured with an SSL proxy target proxy is specifically designed for non-HTTP raw TCP traffic requiring global TLS termination at Google's edge network and routing across multiple backend regions.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Load Balancers based on Traffic Scope (Global vs Regional), Protocol (HTTP vs Raw TCP), and TLS Offloading Needs
Tahmini Süre:2m 0s