Google Professional Cloud Network Engineer Question 527
Select 2Google Cloud PlatformYour organization is hosting a web application on Google Cloud, and you need to configure Cloud DNS to support routing traffic to a backend service hosted in multiple regions. You are required to ensure low-latency responses to users worldwide and enable failover in case one of the regions becomes unavailable. Which steps should you take to achieve this?
- A
Configure a Cloud DNS public managed zone and create A or AAAA records pointing to the backend service IP addresses.
- B
Implement a Cloud Load Balancer with a global external IP address and update the Cloud DNS zone with an A record pointing to the load balancer.
- C
Enable geo-location-based routing for the Cloud DNS managed zone to route users to the nearest backend service.
- D
Configure health checks within the Cloud DNS managed zone to ensure failover to another region in case of regional outages.
- E
Use Cloud DNS forwarding zones to route the DNS queries to external DNS providers for latency optimization.
Show answer and explanation
Correct answers: B, C
Explanation
To ensure low-latency responses and failover for a globally distributed application, you should configure a Cloud Load Balancer with a global external IP for traffic distribution and then integrate it with Cloud DNS by creating an A record pointing to the load balancer. Additionally, enabling geo-location-based routing in Cloud DNS ensures users are directed to the nearest backend service, optimizing performance.
- A. Incorrect.
This option is incorrect because directly pointing A or AAAA records to backend service IPs does not support global load balancing or failover.
- B. Correct.
This option is correct because a Cloud Load Balancer with a global external IP ensures traffic is routed to backend services across multiple regions with low latency and failover capabilities.
- C. Correct.
This option is correct because enabling geo-location-based routing in Cloud DNS helps direct users to the nearest backend service, improving latency for global users.
- D. Incorrect.
This option is incorrect because Cloud DNS does not natively support health checks for failover; health checks are typically implemented at the load balancer level.
- E. Incorrect.
This option is incorrect because forwarding zones are used to route DNS queries to external DNS providers, which is unrelated to optimizing latency for global users.