CLOUD-NETWORK practice question 20 of 30

You have just deployed your infrastructure on Google Cloud. You now need to configure the DNS to meet the following requirements: Your on-premises resources should resolve your Google Cloud zones. Your Google Cloud resources should resolve your on-premises zones. You need the ability to resolve “. internal” zones provisioned by Google Cloud. What should you do?

Full set: 233 questions
Answer options
A: Configure an outbound server policy, and set your alternative name server to be your on-premises DNS resolver. Configure your on-premises DNS resolver to forward Google Cloud zone queries to Google's public DNS 8.8.8.8.
B: Configure both an inbound server policy and outbound DNS forwarding zones with the target as the on-premises DNS resolver. Configure your on-premises DNS resolver to forward Google Cloud zone queries to Google Cloud's DNS resolver. Correct answer
C: Configure an outbound DNS server policy, and set your alternative name server to be your on- premises DNS resolver. Configure your on-premises DNS resolver to forward Google Cloud zone queries to Google Cloud's DNS resolver.
D: Configure Cloud DNS to DNS peer with your on-premises DNS resolver. Configure your on- premises DNS resolver to forward Google Cloud zone queries to Google's public DNS 8.8.8.8.
Correct Answer:
B. Configure both an inbound server policy and outbound DNS forwarding zones with the target as the on-premises DNS resolver. Configure your on-premises DNS resolver to forward Google Cloud zone queries to Google Cloud's DNS resolver.
Explanation

To achieve bidirectional DNS resolution between Google Cloud and on-premises environments, a combination of Cloud DNS policies is required. An inbound server policy creates a forwarding endpoint in your VPC that your on-premises DNS server can send queries to, allowing on-premises to resolve Google Cloud private zones. An outbound DNS forwarding zone directs queries for specific on-premises domains from your VPC to your on-premises DNS resolver. This combination correctly establishes the required two-way name resolution path while preserving the ability to resolve internal Google Cloud zones.

Why Incorrect

A. An outbound policy alone only enables resolution from Google Cloud to on-premises. Forwarding to a public DNS (8.8.8.8) cannot resolve private Google Cloud zones.
C. This option is incomplete as it only configures outbound forwarding from Google Cloud to on-premises, failing to provide a path for on-premises to resolve Google Cloud resources.
D. DNS peering is for connecting two VPC networks' DNS, not for hybrid on-premises connectivity. Forwarding to public DNS for private zones is incorrect.

References

1. Google Cloud Documentation, "Cloud DNS overview". "For hybrid architectures, you can configure Cloud DNS to provide hybrid DNS... Use an inbound server policy to allow on-premises hosts to query Cloud DNS... Use an outbound server policy or DNS forwarding zones to query on-premises name servers." https://cloud.google.com/dns/docs/overview#hybrid-dns

2. Google Cloud Documentation, "Configure DNS forwarding from on-premises networks to a VPC network". "To enable your on-premises network to forward DNS queries to your VPC network, you must create an inbound server policy in the VPC network." https://cloud.google.com/dns/docs/set-up-dns-forwarding-from-on-prem-to-gcp

3. Google Cloud Documentation, "Configure DNS forwarding from a VPC network to on-premises networks". "To enable your VPC network to forward DNS queries to your on-premises network, you can create a forwarding zone or an outbound server policy for the VPC network." https://cloud.google.com/dns/docs/set-up-dns-forwarding-from-gcp-to-on-prem

Scroll to Top