A telehealth company is planning the networking infrastructure for a global web application hosted on Compute Engine. The application serves static web assets to global clients while routing HTTPS API requests to backend instance groups in multiple regions based on user proximity. Internal microservices running inside the VPC network must also securely resolve private domain names without exposing DNS records to the public internet. Which TWO Google Cloud networking configurations should you implement to satisfy these requirements? (Select TWO.)
- Configure a Global External Application Load Balancer with Cloud CDN enabled on the backend service to serve static content and route global HTTPS traffic.Answer
- BDeploy an External Passthrough Network Load Balancer with Cloud CDN attached to distribute HTTPS traffic across regions.
- Set up a Cloud DNS private zone bound to the application's VPC network for internal service name resolution.Answer
- DConfigure a Cloud DNS public forwarding zone pointing to an external public resolver to handle internal VPC service requests.
Answer
The two correct configurations are enabling a Global External Application Load Balancer with Cloud CDN on the backend service and setting up a Cloud DNS private zone bound to the VPC network.
Global HTTPS proxy routing and Cloud CDN caching require an External Application Load Balancer operating at Layer 7. Meanwhile, internal domain resolution restricted to a specific VPC network requires a Cloud DNS private zone.
Step-by-Step Solution
Key Concept
Selecting Layer 7 Global Load Balancing with Cloud CDN for external web content caching alongside Cloud DNS private zones for VPC internal domain resolution.