Google Professional Cloud Network Engineer Question 15
Single answerGoogle Cloud PlatformYour company has an on-premises data center and multiple applications hosted in Google Cloud. You need to design a DNS architecture to ensure low-latency name resolution for both internal users in the on-premises network and external users accessing services hosted in Google Cloud. The solution must allow on-premises users to resolve names for Google Cloud resources while also supporting dynamic updates for internal DNS records. Which DNS topology should you implement?
- A
Use Cloud DNS as the primary DNS and configure a forwarding zone to the on-premises DNS.
- B
Use on-premises DNS as the primary DNS and configure a forwarding zone to Cloud DNS.
- C
Use Cloud DNS for both internal and external users without any integration with the on-premises DNS.
- D
Set up a hybrid DNS architecture where Cloud DNS is used for Google Cloud resources, and the on-premises DNS is used for on-premises resources, with bidirectional forwarding zones.
Show answer and explanation
Correct answer: D
Explanation
A hybrid DNS architecture is best suited for scenarios where you need to integrate on-premises DNS with Cloud DNS. This topology allows low-latency name resolution for both internal and external users while supporting dynamic updates and bidirectional communication between on-premises and Cloud DNS systems. It provides the flexibility and functionality required to meet the needs of both environments.
- A. Incorrect.
This option does not address the need for on-premises users to resolve Google Cloud resources dynamically, as the on-premises DNS would still need a way to query Cloud DNS.
- B. Incorrect.
This option does not ensure low-latency resolution for external users, as the on-premises DNS would become a bottleneck for resolving Google Cloud services.
- C. Incorrect.
This option does not meet the requirement to allow on-premises users to resolve internal Google Cloud resources since it lacks integration with the on-premises DNS.
- D. Correct.
This option meets all requirements by creating a hybrid DNS architecture. It allows on-premises users to resolve Google Cloud resources via a forwarding zone and external users to resolve Google Cloud services directly using Cloud DNS. It also supports dynamic updates.