Examkin

Question

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

An organization is designing a high-traffic web application deployed across Compute Engine instances in multiple Google Cloud regions. The application serves global users over HTTPS and requires low-latency delivery of static assets using edge caching, as well as automatic routing of user requests to the nearest healthy backend region. Which TWO architectural components should the cloud engineer include in the design to meet these requirements?

  1. Configure a Global External Application Load Balancer to route HTTPS traffic to the closest healthy backend instance group.Answer
  2. Enable Cloud CDN on the backend service of the Global External Application Load Balancer to cache static content at edge locations.Answer
  3. C
    Deploy an Internal Passthrough Network Load Balancer in each region with Cloud CDN enabled.
  4. D
    Use an External Passthrough Network Load Balancer configured with Cloud DNS routing policies to cache static HTTP assets.

Answer

The application architecture requires a Global External Application Load Balancer to handle multi-region HTTPS traffic and routing, along with enabling Cloud CDN on its backend service to cache static assets at edge locations.
The Global External Application Load Balancer acts as a Layer 7 reverse proxy using a single global anycast IP address, distributing HTTPS requests across instance groups in multiple regions based on proximity and health. Enabling Cloud CDN directly on the backend service of this load balancer caches HTTP(S) static assets at edge POPs, minimizing latency for global clients.

Step-by-Step Solution

1
Identify the application protocol and scope requirements.
The application serves global internet users over HTTPS across multiple regions.
Global HTTPS routing requires a Layer 7 global proxy load balancer, specifically the Global External Application Load Balancer.
2
Determine the edge caching requirement for low-latency static content delivery.
Cloud CDN must be enabled on the HTTP(S) load balancer backend service.
Cloud CDN caches HTTP(S) content at Google's global network edge POPs, which reduces latency and backend load.
3
Evaluate alternative load balancing options.
Layer 4 passthrough network load balancers (internal or external) are ruled out.
Layer 4 passthrough load balancers do not terminate HTTP(S) requests or support Cloud CDN integration.

Key Concept

Global External Application Load Balancing and Cloud CDN Integration
Estimated Time:1m 30s
Rate this question

Topics

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

More questions from this topic