Google Professional Cloud Network Engineer Question 164
Single answerGoogle Cloud PlatformYour organization has a multi-cloud environment and uses Google Cloud for its main workloads. You need to design a DNS strategy that allows workloads in Google Cloud to resolve private DNS zones hosted in an on-premises data center, while also enabling on-premises workloads to resolve private DNS zones in Google Cloud. The solution must minimize latency and avoid recursive DNS loops. Which DNS forwarding design should you implement?
- A
Configure Cloud DNS with a DNS peering zone in Google Cloud to forward queries to the on-premises DNS server, and set up conditional forwarding on the on-premises DNS server to forward Google Cloud private DNS zone queries back.
- B
Deploy a DNS resolver in Google Cloud to handle all DNS queries for Google Cloud workloads and configure conditional forwarding to the on-premises DNS server.
- C
Use DNS forwarding on both sides, where Google Cloud forwards queries for private on-premises zones to the on-premises DNS server, and the on-premises DNS server forwards queries for private Google Cloud zones to Cloud DNS.
- D
Set up DNS over VPN to allow both Google Cloud and on-premises workloads to directly query each other’s DNS zones without any forwarding.
Show answer and explanation
Correct answer: C
Explanation
The correct answer ensures that private DNS zones in both Google Cloud and on-premises environments are resolvable without creating recursive loops or unnecessary complexity. By configuring DNS forwarding in both directions, each environment can resolve the other's private DNS zones efficiently. This approach minimizes latency and aligns with best practices for hybrid DNS configurations.
- A. Incorrect.
This option is correct because it establishes a forwarding path for both private DNS zones without creating recursive loops or unnecessary complexity. Google Cloud forwards queries for on-premises zones to the on-premises DNS server, while the on-premises server forwards queries for Google Cloud zones to Cloud DNS.
- B. Incorrect.
This option is incorrect because deploying a separate DNS resolver in Google Cloud introduces unnecessary complexity and does not address the requirement for the on-premises DNS server to resolve Google Cloud private zones.
- C. Correct.
This option is correct because it ensures a two-way DNS forwarding strategy that minimizes latency and avoids recursive loops. By configuring each environment to forward only the necessary queries to the other, you achieve an efficient resolution process.
- D. Incorrect.
This option is incorrect because DNS over VPN does not inherently solve the problem of resolving private DNS zones without a forwarding strategy. Additionally, it could lead to increased latency and complexity.