Google Professional Cloud Network Engineer Question 12
Single answerGoogle Cloud PlatformYour company is migrating workloads to Google Cloud while maintaining some critical services in the on-premises data center. You need to design a DNS topology that ensures low-latency name resolution for services hosted both on Google Cloud and on-premises. The on-premises environment uses an existing DNS server, and you also need to configure DNS in Google Cloud to resolve both internal and external domains seamlessly. Which design approach should you choose?
- A
Configure a private Cloud DNS zone in Google Cloud and set up a DNS forwarding rule to forward queries for on-premises domains to the on-premises DNS server.
- B
Configure a public Cloud DNS zone in Google Cloud and use it for all DNS queries, including internal on-premises domains.
- C
Set up a DNS peering zone in Google Cloud and configure the on-premises DNS server to forward all queries to the Cloud DNS server.
- D
Use a hybrid DNS setup with a private Cloud DNS zone for Google Cloud resources and an on-premises DNS server for local resources, without forwarding DNS queries between the two environments.
Show answer and explanation
Correct answer: A
Explanation
The correct answer is to configure a private Cloud DNS zone in Google Cloud and set up a DNS forwarding rule to forward queries for on-premises domains to the on-premises DNS server. This approach ensures that DNS resolution works seamlessly across Google Cloud and on-premises environments while maintaining separation and security for internal and external domains. Public Cloud DNS zones are not suitable for private or on-premises domains, DNS peering is not designed for hybrid setups, and not forwarding DNS queries between environments would break connectivity and name resolution.
- A. Correct.
This is the correct approach. A private Cloud DNS zone allows you to manage DNS for Google Cloud resources securely, and setting up a DNS forwarding rule ensures that queries for on-premises domains are directed to the on-premises DNS server, enabling seamless name resolution across both environments.
- B. Incorrect.
This is incorrect because a public Cloud DNS zone is designed for external DNS resolution, not for internal or private domains. Using it for internal on-premises domains would expose sensitive information and is not suitable for this scenario.
- C. Incorrect.
This is incorrect because DNS peering zones are intended to allow DNS query resolution across different VPCs, not between on-premises and Google Cloud environments. Additionally, forwarding all queries to the Cloud DNS server would not ensure proper resolution for on-premises domains.
- D. Incorrect.
This is incorrect because without forwarding DNS queries between the two environments, there would be no seamless name resolution. Applications in Google Cloud would not be able to resolve on-premises domains and vice versa.