Examkin

Question

Difficulty: MediumDeploying Cloud Load Balancers and Configuring Cloud DNS

An infrastructure team is deploying a proprietary state-synchronization service on Compute Engine instance groups located in the us-east1 and europe-west3 regions. The service receives non-HTTP TCP traffic on port 9090, requires SSL/TLS offloading at the load balancer proxy layer, and must expose a single global IP address for client connections. Which Google Cloud load balancer type should you deploy?

  1. Global external Proxy Network Load BalancerAnswer
  2. B
    Global external Application Load Balancer
  3. C
    External passthrough Network Load Balancer
  4. D
    Regional external Application Load Balancer

Answer

Global external Proxy Network Load Balancer
The Global external Proxy Network Load Balancer handles non-HTTP TCP traffic, terminates TLS/SSL at the load balancer proxy edge using target SSL proxies or target TCP proxies, and provides a single global IP address with backends in multiple regions.

Step-by-Step Solution

1
Analyze protocol requirements
The application uses non-HTTP raw TCP traffic on port 9090, eliminating HTTP/HTTPS (layer 7) Application Load Balancers.
Application Load Balancers expect valid HTTP/HTTPS protocol headers.
2
Analyze security and proxy requirements
SSL/TLS offloading must occur at the proxy layer before reaching backends, eliminating passthrough load balancers.
Passthrough Network Load Balancers route raw packets directly to instances without terminating SSL/TLS.
3
Determine geographic scope
The requirement specifies a single global IPv4 address distributing traffic across us-east1 and europe-west3.
Global external Proxy Network Load Balancers provide reverse proxying for TCP traffic with SSL offloading globally.

Key Concept

Selecting GCP Load Balancers Based on Traffic Protocol, SSL Termination, and Scope
Rate this question

Topics

Deploying Cloud Load Balancers and Configuring Cloud DNS

More questions from this topic