Examkin

Question

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

An enterprise is designing the network architecture for a public web application deployed on Compute Engine instances across multiple Google Cloud regions. The application serves HTTP/HTTPS traffic to a worldwide user base. The design requires routing incoming requests to the closest regional backend and caching static content at Google edge locations to reduce latency. Which TWO Google Cloud components should be planned for this implementation? (Select TWO)

  1. Global External Application Load Balancer for multi-region HTTP/HTTPS request distributionAnswer
  2. Cloud CDN enabled on backend services to cache static content near end usersAnswer
  3. C
    Internal Passthrough Network Load Balancer to route incoming internet traffic across regions
  4. D
    External Passthrough Network Load Balancer to handle HTTP protocol routing and edge caching

Answer

The architectural plan must include the Global External Application Load Balancer and Cloud CDN.
To distribute global HTTP/HTTPS traffic efficiently, a Global External Application Load Balancer acts as a single global IP endpoint that forwards requests to the closest regional backend. Enabling Cloud CDN on its backend services leverages Google's global points of presence (PoPs) to cache static responses and lower overall latency.

Step-by-Step Solution

1
Analyze client locality and application layer protocols.
Traffic originates from public internet clients globally using HTTP/HTTPS (Layer 7).
Selecting the correct load balancer requires matching traffic source (external), reach (global), and layer (Layer 7 HTTP/HTTPS).
2
Select the appropriate Google Cloud load balancing product.
Choose the Global External Application Load Balancer.
This component supports global HTTP/HTTPS ingress and routes users to the nearest available compute backend.
3
Select the caching mechanism to minimize latency for static assets.
Enable Cloud CDN on the load balancer's backend service.
Cloud CDN leverages Google's global edge network to cache HTTP responses close to end users.

Key Concept

Selecting load balancer types and caching mechanisms based on protocol, scope, and caching requirements.
Rate this question

Topics

Planning Network Load Balancing, Cloud DNS, and Cloud CDN

More questions from this topic