An organization is deploying a global public web application on Google Cloud Compute Engine. The application serves static web assets (such as images and scripts) as well as dynamic web endpoints over HTTPS. The networking team needs to reduce load times for static assets by caching them near end users worldwide, and they must configure public DNS resolution for their custom domain using geo-based traffic steering to direct users to regional backend entry points. Which TWO of the following configuration choices should the team implement to satisfy these requirements?
- Deploy a Global External HTTP(S) Load Balancer and enable Cloud CDN on the backend services or Cloud Storage buckets that host the static content.Answer
- Create a Cloud DNS public managed zone and configure a Geolocation routing policy for the domain's record set.Answer
- CDeploy an Internal Passthrough Network Load Balancer and enable Cloud CDN on its backend instance group.
- DDeploy an External TCP Proxy Load Balancer and enable Cloud CDN on its backend services.
Answer
The team should deploy a Global External HTTP(S) Load Balancer with Cloud CDN enabled on static content backends, and set up a Cloud DNS public managed zone using Geolocation routing policies.
Global External HTTP(S) Load Balancers support Cloud CDN for caching static assets at Google edge locations worldwide, satisfying the requirement to reduce static load times. Additionally, Cloud DNS public managed zones support Geolocation routing policies to steer user DNS queries based on source location.
Step-by-Step Solution
Key Concept
Planning Layer 7 HTTP(S) Load Balancing with Cloud CDN caching alongside Cloud DNS Geolocation routing policies for global public web workloads.