An enterprise application receives raw encrypted TCP traffic on port 8443 from global clients. The infrastructure team needs to terminate SSL/TLS at the load balancer level and forward unencrypted TCP traffic to a backend Compute Engine Managed Instance Group. The application does not use HTTP or HTTPS protocols. Which Google Cloud load balancing architecture should be deployed to fulfill these requirements?
- Deploy a Global External Proxy Network Load Balancer with a target SSL proxy and an SSL certificate configured on the target proxy.Answer
- BDeploy a Global External Application Load Balancer with an HTTPS target proxy and a URL map configured for port 8443.
- CDeploy a Regional External Passthrough Network Load Balancer with an SSL certificate attached directly to the target pool.
- DEnable the Cloud DNS API in the target project and configure round-robin A records pointing directly to individual Compute Engine VM external IP addresses.
Answer
Deploy a Global External Proxy Network Load Balancer with a target SSL proxy and an SSL certificate configured on the target proxy.
The Global External Proxy Network Load Balancer using an SSL Proxy is specifically designed to handle global, non-HTTP raw TCP traffic while terminating SSL/TLS connections at the load balancer level before routing cleartext traffic to backend instances.
Step-by-Step Solution
Key Concept
Selecting GCP Load Balancers Based on Protocol, SSL Offloading, and Scope
Estimated Time:2m 0s