Examkin

Question

Difficulty: MediumDeploying Cloud Load Balancers and Configuring Cloud DNS

Your enterprise web application is hosted across Compute Engine virtual machine instance groups located in two Google Cloud regions: us-central1 and europe-west3. The application requires SSL termination at Google's network edge, HTTP/2 support for client connections, and Layer 7 path-based URL map routing (such as forwarding requests for /static/* to a Cloud Storage bucket and /api/* to the Compute Engine backend service). Which Google Cloud load balancer should you deploy?

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

Answer

Global External Application Load Balancer
The Global External Application Load Balancer is a proxy-based Layer 7 load balancer that handles HTTP, HTTPS, and HTTP/2 traffic. It terminates SSL at Google's global edge points of presence, uses URL maps for path-based routing to different backends (such as backend services or Cloud Storage buckets), and balances traffic globally across backend instance groups in multiple regions.

Step-by-Step Solution

1
Analyze client accessibility and geographical reach requirements.
The application must serve public internet traffic across multiple regions (us-central1 and europe-west3), requiring a global external frontend IP.
Regional load balancers cannot distribute traffic across multiple Google Cloud regions under one IP address.
2
Identify the required network protocol layer and routing features.
The requirement specifies Layer 7 capabilities: SSL termination at Google edge locations, HTTP/2, and URL map path-based routing (/static/* vs /api/*).
Layer 4 Network Load Balancers only inspect transport-level headers (IP/port) and cannot parse HTTP paths or handle Layer 7 SSL termination.
3
Match requirements to the correct Google Cloud Load Balancing product.
The Global External Application Load Balancer fulfills all requirements: global reach, multi-region backends, Layer 7 URL map routing, and edge SSL termination.
It is designed specifically for HTTP(S) workloads distributed globally.

Key Concept

Selecting Cloud Load Balancer types based on traffic scope (global vs regional), client access (external vs internal), and protocol layer (Layer 4 vs Layer 7).
Rate this question

Topics

Deploying Cloud Load Balancers and Configuring Cloud DNS

More questions from this topic