An enterprise is architecture-planning a global web application deployed across Compute Engine instance groups in the us-east1 and europe-west3 regions. The application serves dynamic REST API requests along with large static media assets. The design must meet three strict constraints:
1. Terminate client HTTPS connections at the Google Cloud edge and cache static media assets to minimize backend latency and bandwidth usage.
2. Steer public end-user DNS queries for app.example.com to the nearest healthy regional backend pool based on client geographic origin.
3. Automatically divert DNS traffic away from a region if its backend instances fail health checks.
Which combination of Google Cloud networking services and configurations fulfills these requirements while adhering to Google recommended practices?
- Deploy a Global External HTTP(S) Load Balancer backed by instance groups in both regions, enable Cloud CDN on the backend service, and configure a Cloud DNS public zone using a Geolocation routing policy with health checking.Cevap
- BDeploy an External Passthrough Network Load Balancer in each region, enable Cloud CDN on the target pools, and configure Cloud DNS using a Weighted Round Robin routing policy.
- CDeploy an External Proxy Network Load Balancer with backend services in both regions, enable Cloud CDN on the backend service, and configure Cloud DNS using a Failover routing policy.
- DDeploy an Internal Application Load Balancer in us-east1 and europe-west3, attach Cloud CDN directly to the backend services, and configure Cloud DNS private zone forwarding.