Question

Difficulty: MediumDeploying Cloud Load Balancers and Configuring Cloud DNS

Your company is deploying a proprietary binary communication service hosted on Compute Engine managed instance groups across the us-central1 and europe-west1 regions. The service receives external client traffic over custom non-HTTP TCP connections on port 8443. Your security policy mandates that TLS/SSL encryption must be terminated at the Google Cloud load balancer edge before passing decrypted TCP traffic to backend virtual machines. Which Google Cloud load balancer type should you configure to meet these requirements?

  1. Deploy a Global External Proxy Network Load Balancer with a Target SSL Proxy.Answer
  2. B
    Deploy an External Passthrough Network Load Balancer with a Target Pool.
  3. C
    Deploy a Global External Application Load Balancer with a Target HTTPS Proxy.
  4. D
    Deploy a Regional Internal Application Load Balancer with a Target HTTP Proxy.

Answer

Deploy a Global External Proxy Network Load Balancer with a Target SSL Proxy.
The Global External Proxy Network Load Balancer (using a Target SSL Proxy) is designed specifically for external non-HTTP TCP traffic on supported ports such as 8443, and terminates TLS/SSL at the load balancer edge before proxying traffic to backend instance groups.

Step-by-Step Solution

1
Analyze the protocol requirement.
The application uses non-HTTP raw TCP traffic on port 8443.
Layer 7 HTTP(S) load balancers cannot handle non-HTTP TCP protocols.
2
Analyze the security and offloading requirement.
TLS/SSL termination must take place at the load balancer edge.
Passthrough network load balancers do not terminate TLS; proxy load balancers are required for TLS offloading.
3
Select the matching load balancer type.
Choose a Global External Proxy Network Load Balancer configured with a Target SSL Proxy.
This load balancer accepts external non-HTTP TCP traffic globally, terminates TLS at the edge, and proxies connection requests to backend Compute Engine instances.

Key Concept

Selecting GCP Load Balancer types based on protocol (TCP vs HTTP), traffic scope (External vs Internal), and SSL/TLS termination requirements.
Rate this question