An organization is deploying a web application in Google Cloud that serves static media content to global internet users over HTTPS. The application architecture requires edge caching to reduce latency for static assets. Additionally, backend Compute Engine instances in a Virtual Private Cloud (VPC) must resolve internal database server names using a private domain namespace that is isolated from the public internet. Which TWO architectural components should you include in your network design? (Select TWO)
- A Global External Application Load Balancer with Cloud CDN enabled for static content backendsAnswer
- A Cloud DNS private managed zone authorized for the application's VPC networkAnswer
- CAn External Passthrough Network Load Balancer with Cloud CDN enabled for static content backends
- DAn Internal Passthrough Network Load Balancer configured to accept and decrypt incoming public internet HTTPS traffic
Answer
The correct architecture requires configuring a Global External Application Load Balancer with Cloud CDN enabled for serving global HTTPS static content, and creating a Cloud DNS private managed zone bound to the VPC network for private internal name resolution.
To serve global HTTPS static content with edge caching, Google Cloud requires a Global External Application Load Balancer because Cloud CDN integrates specifically with HTTP(S) proxy load balancers. For internal database name resolution restricted from the public internet, a Cloud DNS private managed zone must be created and linked to the VPC network.
Step-by-Step Solution
Key Concept
Selecting appropriate GCP load balancer types for HTTP(S) content caching with Cloud CDN and implementing Cloud DNS private zones for isolated internal name resolution.