Soru

Zorluk: OrtaPlanning Network Load Balancing, Cloud DNS, and Cloud CDN

An online learning platform needs to serve static video assets and course documents to internet users globally over HTTPS. To minimize latency and reduce origin server load, static assets must be cached at the Google network edge, and SSL/TLS termination must occur at the global edge. Which TWO Google Cloud networking components or features should you include in your architecture plan?

  1. Global External Application Load Balancer with Google-managed SSL certificatesCevap
  2. Cloud CDN enabled on the load balancer backend service or storage bucketCevap
  3. C
    Internal Passthrough Network Load Balancer with a regional forwarding rule
  4. D
    Cloud DNS Private Zone configured with outbound forwarding targets

Cevap

Deploy a Global External Application Load Balancer to terminate global HTTPS traffic at the edge and enable Cloud CDN on the backend to cache static assets.
A Global External Application Load Balancer handles global public HTTP(S) requests and supports Google-managed SSL certificates at the network edge. Enabling Cloud CDN on the load balancer's backend leverages Google's global PoPs to cache static video and document assets close to users, reducing latency and origin workload.

Adım Adım Çözüm

1
Analyze the entry point and protocol requirements
External internet users need access over HTTPS with edge SSL termination, requiring a Global External Application Load Balancer (HTTP/HTTPS).
Layer 7 external load balancing is required to handle HTTP(S) traffic globally and terminate TLS at Google's edge.
2
Analyze the caching requirement
Cloud CDN must be attached to the backend service or Cloud Storage bucket underlying the external load balancer.
Cloud CDN utilizes Google's global points of presence (PoPs) to store cached copies of static assets near end users.

Anahtar Kavram

Planning Global Load Balancing and Edge Caching with Cloud CDN
Bu soruyu puanla