Question

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

Your company is deploying a new web application on Google Cloud. You need to configure network components to serve public static web assets with edge caching and resolve internal service hostnames privately within your Virtual Private Cloud (VPC) network. Which two Google Cloud networking services should you include in your design? (Select TWO.)

  1. Cloud CDN integrated with a Global External HTTP(S) Load BalancerAnswer
  2. Cloud DNS private managed zone linked to the VPC networkAnswer
  3. C
    Internal Passthrough Network Load Balancer configured for static media caching
  4. D
    Cloud DNS public managed zone configured for internal VPC hostname resolution

Answer

The architecture should use Cloud CDN integrated with a Global External HTTP(S) Load Balancer for public static asset caching, and a Cloud DNS private managed zone linked to the VPC network for private internal hostname resolution.
Cloud CDN works alongside Global External HTTP(S) Load Balancers to store cached web responses close to end users, reducing latency and backend server load. To handle internal hostname resolution inside a VPC without public exposure, Cloud DNS private managed zones allow custom DNS records to be queried exclusively by authorized internal resources.

Step-by-Step Solution

1
Identify the public caching requirement for web content
Cloud CDN requires an HTTP(S) Load Balancer (Global External) to serve cached static assets to internet clients.
Cloud CDN caches content at Google edge locations for external HTTP(S) traffic.
2
Identify the internal DNS resolution requirement
A Cloud DNS private managed zone provides private domain name resolution for VMs inside the VPC.
Private DNS zones restrict hostname resolution visibility exclusively to authorized VPC networks.

Key Concept

Selecting Cloud CDN for edge caching and Cloud DNS private zones for VPC internal name resolution
Rate this question