Google Professional Cloud Network Engineer Question 553
Select 3Google Cloud PlatformYour organization has an on-premises DNS server that manages internal domain names. You are migrating some workloads to Google Cloud and need internal DNS resolution to work seamlessly between the on-premises environment and your Google Cloud VPC. How can you achieve this integration?
- A
Set up a Cloud DNS private zone and manually synchronize DNS records between the on-premises DNS server and the private zone.
- B
Use a Cloud DNS forwarding zone to forward DNS queries from Google Cloud to the on-premises DNS server.
- C
Configure a Cloud VPN or Interconnect to establish connectivity between the on-premises environment and the VPC, then use inbound DNS forwarding.
- D
Enable the on-premises DNS server to forward requests for Google Cloud internal domains to the Google Cloud DNS resolver at 169.254.169.254.
- E
Use a public Cloud DNS zone to host internal domain names to simplify management across environments.
Show answer and explanation
Correct answers: B, C, D
Explanation
To integrate on-premises DNS with Google Cloud, you can use a Cloud DNS forwarding zone to forward queries to your on-premises DNS server. Additionally, you need network connectivity, such as through Cloud VPN or Interconnect, to enable DNS communication between the environments. For resolving Google Cloud internal domains on-premises, you can forward requests to the Google Cloud DNS resolver at 169.254.169.254. These approaches ensure seamless and secure DNS integration.
- A. Incorrect.
While a Cloud DNS private zone can manage internal DNS, manually synchronizing DNS records is error-prone and not recommended for dynamic or large-scale environments.
- B. Correct.
A Cloud DNS forwarding zone allows DNS queries to be forwarded from Google Cloud to on-premises, enabling seamless DNS integration for internal domains.
- C. Correct.
Establishing connectivity using Cloud VPN or Interconnect is a prerequisite for inbound DNS forwarding, which allows the on-premises DNS server to handle queries originating in the VPC.
- D. Correct.
Forwarding requests for Google Cloud internal domains to the IP address 169.254.169.254 ensures that the on-premises DNS server can resolve internal Google Cloud domain names.
- E. Incorrect.
A public Cloud DNS zone is not suitable for internal domain names as it exposes those names to the public internet, violating security best practices.