CLOUD-NETWORK practice question 1 of 30

You are configuring the final elements of a migration effort where resources have been moved from on-premises to Google Cloud. While reviewing the…

Full set: 233 questions
You are configuring the final elements of a migration effort where resources have been moved from on-premises to Google Cloud. While reviewing the deployed architecture, you noticed that DNS resolution is failing when queries are being sent to the on-premises environment. You log in to a Compute Engine instance, try to resolve an on-premises hostname, and the query fails. DNS queries are not arriving at the on-premises DNS server. You need to use managed services to reconfigure Cloud DNS to resolve the DNS error. What should you do?
Answer options
A: Validate that the Compute Engine instances are using the Metadata Service IP address as their resolver. Configure an outbound forwarding zone for the on-premises domain pointing to the on- premises DNS server. Configure Cloud Router to advertise the Cloud DNS proxy range to the on- premises network. Correct answer
B: Validate that there is network connectivity to the on-premises environment and that the Compute Engine instances can reach other on-premises resources. If errors persist, remove the VPC Network Peerings and recreate the peerings after validating the routes.
C: Review the existing Cloud DNS zones, and validate that there is a route in the VPC directing traffic destined to the IP address of the DNS servers. Recreate the existing DNS forwarding zones to forward all queries to the on-premises DNS servers.
D: Ensure that the operating systems of the Compute Engine instances are configured to send DNS queries to the on-premises DNS servers directly.
Correct Answer:
A. Validate that the Compute Engine instances are using the Metadata Service IP address as their resolver. Configure an outbound forwarding zone for the on-premises domain pointing to the on- premises DNS server. Configure Cloud Router to advertise the Cloud DNS proxy range to the on- premises network.
Explanation

For a hybrid environment, the recommended managed solution for resolving on-premises hostnames from Google Cloud is Cloud DNS outbound forwarding. Compute Engine instances should use the metadata server (169.254.169.254) for DNS resolution. A Cloud DNS outbound forwarding zone is then created for the on-premises domain, pointing to the on-premises DNS servers. For the on-premises servers to return responses, they must be able to route back to the special IP range (35.199.192.0/19) that Cloud DNS uses to send forwarded queries. This range must be advertised from Google Cloud to the on-premises network via Cloud Router.

Why Incorrect

B. While network connectivity is necessary, it doesn't solve the DNS resolution architecture problem. Recreating peerings is unlikely to fix a DNS configuration issue.
C. Recreating existing zones is not the correct action. The issue is with outbound queries to a different domain, which requires an outbound forwarding policy, not modifying existing zones.
D. Configuring the OS on each VM to use on-premises DNS servers directly is not a managed or scalable solution and bypasses the benefits of Cloud DNS.

References

1. Google Cloud Documentation, "Configure DNS forwarding from a VPC network to your on-premises network". This document outlines the exact steps in option A: create an outbound forwarding zone and configure firewall rules and routing for the 35.199.192.0/19 IP range.

Source: https://cloud.google.com/dns/docs/hybrid/forwarding-to-on-prem

2. Google Cloud Documentation, "Cloud DNS forwarding zones". It states, "An outbound forwarding zone sends requests for a specific zone or zones to a set of your own DNS name servers."

Source: https://cloud.google.com/dns/zones#forwarding-zones

3. Google Cloud Documentation, "Cloud DNS for hybrid cloud". This architecture guide explains that for outbound forwarding, "You must configure your on-premises VPN gateway to advertise routes to the Cloud DNS forwarding IP range (35.199.192.0/19)."

Source: https://cloud.google.com/architecture/hybrid-cloud-dns-patterns

Scroll to Top