Google Professional Cloud Network Engineer Question 556
Single answerGoogle Cloud PlatformYour company is hosting a multi-region application on Google Cloud, which has users accessing it both from internal networks (on-premises) and external networks (public internet). You need to configure a DNS setup that resolves the application’s domain to internal IPs for on-premises users while resolving to external IPs for public internet users. Which DNS solution should you implement to meet these requirements?
- A
Use split-horizon DNS with Cloud DNS by creating separate private and public managed zones.
- B
Create a single public managed zone in Cloud DNS and use firewall rules to restrict access for internal users.
- C
Use Cloud DNS forwarding to route DNS queries to a secondary DNS server that resolves based on location.
- D
Configure Cloud DNS with a single private managed zone and use conditional forwarding for external queries.
Show answer and explanation
Correct answer: A
Explanation
Split-horizon DNS is a common solution for scenarios where different DNS responses are required based on the client’s origin (internal or external). In Google Cloud, this can be implemented by setting up separate private and public managed zones in Cloud DNS. The private zone handles internal resolutions (e.g., resolving to internal IPs), while the public zone handles external resolutions (e.g., resolving to external IPs). This approach ensures that DNS queries are resolved appropriately based on the client’s network.
- A. Correct.
This is the correct solution. Split-horizon DNS involves creating separate DNS zones for internal and external resolutions. In Cloud DNS, you can achieve this by creating a private managed zone for internal users and a public managed zone for external users.
- B. Incorrect.
This is incorrect. A single public managed zone cannot differentiate between internal and external users, and firewall rules do not control DNS resolution.
- C. Incorrect.
This is incorrect. While DNS forwarding can route queries, it does not inherently provide the functionality to resolve a domain differently based on whether requests are internal or external.
- D. Incorrect.
This is incorrect. A single private managed zone is limited to internal DNS resolution, and conditional forwarding does not address the need for external resolution.