Google Professional Cloud Network Engineer Question 558
Single answerGoogle Cloud PlatformYour company has deployed an application in Google Cloud that needs to resolve DNS queries differently based on the user's location. Internal users accessing the application from the corporate network should resolve the domain to a private IP address, while external users should resolve the domain to a public IP address. What is the most appropriate approach to achieve this using split-horizon DNS in Google Cloud?
- A
Configure a single Cloud DNS zone and use a global load balancer to resolve the domain based on user location.
- B
Create two separate Cloud DNS zones: one for internal use with private visibility, and one for external use with public visibility.
- C
Use a private Cloud DNS zone and configure conditional forwarding for external DNS queries.
- D
Deploy an internal DNS server for private queries and use an external public DNS provider for public queries.
Show answer and explanation
Correct answer: B
Explanation
Split-horizon DNS involves providing different DNS responses based on the source of the query. In Google Cloud, the best way to achieve this is by creating separate Cloud DNS zones: one with private visibility (for internal users) and one with public visibility (for external users). This approach leverages Google Cloud's built-in capabilities, ensuring simplicity and scalability without the need for additional infrastructure.
- A. Incorrect.
This option is incorrect because a single Cloud DNS zone does not allow you to provide different IP resolutions for internal and external users. Global load balancers handle traffic distribution, not DNS resolution split by visibility.
- B. Correct.
This is the correct option because creating separate Cloud DNS zones with private and public visibility allows you to implement split-horizon DNS, ensuring internal and external users resolve the domain to the appropriate IP addresses.
- C. Incorrect.
This option is incorrect because private Cloud DNS zones cannot forward queries to public DNS servers. Conditional forwarding is not applicable for this scenario.
- D. Incorrect.
This option is suboptimal because managing separate DNS servers introduces unnecessary complexity and is not the recommended approach with Google Cloud's native tools like Cloud DNS.