Question

Difficulty: MediumDeploying Cloud Load Balancers and Configuring Cloud DNS

Your company hosts a global web application running on Compute Engine managed instance groups across multiple Google Cloud regions. You need to expose the application externally to internet clients, optimize user latency by routing traffic to the nearest healthy region, and offload SSL/TLS termination at the edge. Which load balancer should you deploy?

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

Answer

Global External Application Load Balancer
The Global External Application Load Balancer is a Layer 7 proxy load balancer capable of routing HTTP and HTTPS traffic from external clients to backends located across multiple Google Cloud regions. It terminates TLS connections at Google's point of presence (PoP) edge network, ensuring low-latency routing to the closest healthy instance group.

Step-by-Step Solution

1
Analyze client accessibility requirements
External internet access is required, ruling out internal load balancers.
The load balancer must accept traffic directly from internet clients.
2
Analyze protocol and feature requirements
HTTP(S) protocol support and edge SSL termination require a Layer 7 (Application) load balancer.
Passthrough network load balancers operate at Layer 4 and do not terminate SSL/TLS.
3
Analyze geographical scope requirements
Routing traffic across backend instance groups in multiple regions requires a global load balancer.
Regional load balancers are restricted to backends within a single region.

Key Concept

Selecting GCP Load Balancers based on traffic scope, protocol, and regionality
Estimated Time:1m 30s
Rate this question