Google Professional Cloud Network Engineer Question 535
Select 3Google Cloud PlatformYour organization is planning to migrate an external DNS zone to Google Cloud DNS. The external DNS provider supports zone transfers (AXFR). You want to minimize downtime and ensure a seamless migration. Which steps should you take to successfully migrate to Cloud DNS?
- A
Create a Cloud DNS managed zone and configure it as a secondary zone to pull data from the external DNS provider.
- B
Ensure the external DNS provider allows your Google Cloud DNS name servers to perform zone transfers.
- C
Manually recreate all DNS records from the external DNS provider in the Cloud DNS managed zone.
- D
Update the registrar to point to the Cloud DNS name servers only after testing and validating the DNS records in Cloud DNS.
- E
Enable DNSSEC on the Cloud DNS managed zone before migrating any records.
Show answer and explanation
Correct answers: A, B, D
Explanation
To migrate to Cloud DNS with minimal downtime, you should use a secondary zone to automatically pull records from the external provider via zone transfers (AXFR). Ensure that the external provider allows zone transfers and test the migrated DNS records in Cloud DNS before updating the registrar to point to the new name servers. Avoid manual record creation and postpone enabling DNSSEC until after the migration is complete to avoid potential issues.
- A. Correct.
Correct: Configuring a Cloud DNS managed zone as a secondary zone allows you to automatically pull DNS records via zone transfers (AXFR), reducing manual effort and minimizing errors.
- B. Correct.
Correct: The external DNS provider must allow zone transfers to Google Cloud DNS for the migration to succeed. Ensure the necessary permissions and configurations are set.
- C. Incorrect.
Incorrect: Manually recreating all DNS records is error-prone and unnecessary when zone transfers (AXFR) are supported. Using a secondary zone approach is more efficient.
- D. Correct.
Correct: Updating the registrar to point to the Cloud DNS name servers after testing ensures a smooth transition with minimal downtime or service disruption.
- E. Incorrect.
Incorrect: Enabling DNSSEC before migrating records can cause configuration conflicts or issues. DNSSEC should be enabled only after the migration is successfully completed and validated.