Examkin

Question

Difficulty: HardPlanning Network Load Balancing, Cloud DNS, and Cloud CDN

An enterprise healthcare organization is designing the ingestion architecture for a real-time patient monitoring platform. Connected medical sensors deployed worldwide stream telemetry over a proprietary, non-HTTP raw TCP protocol with TLS encryption. The system architecture requires terminating TLS at Google's global edge network to reduce backend handshake latency, and then proxying the raw TCP payload to Compute Engine backend instance groups distributed across multiple Google Cloud regions. Which Google Cloud load balancing solution should you select to satisfy these requirements?

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

Answer

The Global External Proxy Network Load Balancer is the correct choice because it supports raw non-HTTP TCP traffic, terminates TLS at Google's global edge infrastructure, and distributes incoming client connections across multi-region backend instance groups.
The Global External Proxy Network Load Balancer acts as a Layer 4 reverse proxy with global reach. It supports raw non-HTTP TCP protocols, terminates TLS at Google Cloud edge points of presence (PoPs), and balances connection loads to instance groups across multiple GCP regions.

Step-by-Step Solution

1
Analyze protocol requirements
Workload uses proprietary raw TCP (non-HTTP), eliminating Layer 7 (HTTP/HTTPS) Application Load Balancers.
Application Load Balancers inspect Layer 7 HTTP request headers and fail on raw binary TCP streams.
2
Analyze security and edge termination requirements
TLS must be terminated at Google's edge network, requiring a reverse proxy architecture.
Passthrough load balancers pass client TCP packets untouched directly to backends without offloading TLS at the edge.
3
Analyze scope and traffic direction
Clients connect from the internet globally to multi-region backends, requiring a global external load balancer.
Internal load balancers only accept traffic originating from within the VPC or connected private networks.

Key Concept

Selecting GCP Load Balancers based on protocol (L4 vs L7), traffic scope (External vs Internal), and proxying behavior (Passthrough vs Edge Proxy/TLS offloading).
Estimated Time:2m 0s
Rate this question

Topics

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

More questions from this topic