Question

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

An organization plans to host a public web application on Compute Engine instances that serves HTTP and HTTPS traffic to a global audience. They require a Google Cloud load balancing architecture that supports edge caching to speed up static asset delivery. Which Google Cloud load balancer should they choose?

  1. Global External Application Load Balancer with Cloud CDN enabledAnswer
  2. B
    External Passthrough Network Load Balancer with Cloud CDN enabled
  3. C
    Internal Application Load Balancer with Cloud CDN enabled
  4. D
    Internal Passthrough Network Load Balancer with Cloud DNS private zones

Answer

Global External Application Load Balancer with Cloud CDN enabled
The Global External Application Load Balancer operates at Layer 7, providing HTTP/HTTPS proxying across regions and seamlessly integrating with Cloud CDN to cache static content at Google edge points of presence.

Step-by-Step Solution

1
Analyze protocol and client reachability requirements
The application requires serving HTTP/HTTPS traffic to a public global audience.
This necessitates an external Layer 7 (Application) load balancer configured for global availability.
2
Analyze static content caching requirements
Cloud CDN integration is required for caching static assets at Google edge network locations.
Cloud CDN integrates with HTTP(S) Application Load Balancers, not Layer 4 Passthrough load balancers.
3
Select the appropriate Google Cloud load balancing solution
The Global External Application Load Balancer fulfills both global L7 HTTP(S) routing and Cloud CDN caching requirements.
It provides a single global IP address, L7 proxy capabilities, and seamless Cloud CDN integration.

Key Concept

Selecting GCP Load Balancer types based on layer (L4 vs L7), scope (Global vs Regional), and Cloud CDN compatibility
Estimated Time:50s
Rate this question