Question

Difficulty: MediumDeploying Cloud Load Balancers and Configuring Cloud DNS

Your organization is deploying a real-time telemetry ingestion service on Compute Engine instances located in the `us-central1` region. The client devices transmit data using a custom UDP-based protocol and require original client source IP addresses to be preserved for logging and routing purposes. Which Google Cloud load balancer should you deploy to meet these requirements?

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

Answer

External Passthrough Network Load Balancer
An External Passthrough Network Load Balancer operates at Layer 4 (TCP/UDP) and routes packets directly to backend instances without proxying. This makes it ideal for non-HTTP UDP workloads while preserving original client source IP addresses.

Step-by-Step Solution

1
Analyze the network protocol requirements.
The application uses UDP rather than HTTP/HTTPS or TCP.
Protocol compatibility determines which load balancer types can handle incoming network packets.
2
Analyze IP preservation and proxy behavior requirements.
The workload requires preserving the original client source IP address without proxy termination.
Passthrough load balancers forward packets directly to backend instances without altering headers, whereas proxy load balancers terminate connections.
3
Select the appropriate GCP load balancer.
Deploy an External Passthrough Network Load Balancer.
It is a regional Layer 4 load balancer capable of routing incoming UDP traffic to backends with original source IP addresses preserved.

Key Concept

Load Balancer Protocol and Architecture Selection (Layer 4 Passthrough vs. Layer 7 Proxy)
Estimated Time:1m 0s
Rate this question