Your organization operates a proprietary non-HTTP software service listening on custom TCP port 8443 across Compute Engine virtual machines deployed in multiple Google Cloud regions. You must expose this service to external Internet clients while terminating SSL/TLS encryption at the Google Cloud network edge prior to passing unencrypted TCP traffic to your backend instances. Which Google Cloud load balancer configuration should you deploy?
- Deploy a Global External Proxy Network Load Balancer (TCP Proxy) with SSL offloading configured on the target proxy.Cevap
- BDeploy an External Passthrough Network Load Balancer with target pools handling port 8443 traffic.
- CDeploy a Global External Application Load Balancer with an HTTPS target proxy and host routing rules.
- DDeploy an Internal Application Load Balancer with cross-region global backend service routing.
Cevap
Deploy a Global External Proxy Network Load Balancer (TCP Proxy) configured for SSL offloading at the edge target proxy.
The Global External Proxy Network Load Balancer (SSL Proxy / TCP Proxy) is specifically designed to route external non-HTTP TCP traffic across global regions while terminating SSL/TLS sessions at the Google Cloud infrastructure edge before delivering unencrypted TCP packets to backend virtual machine instances.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Load Balancer Types based on Protocol Layer and TLS Offloading