Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization is migrating 40 authoritative DNS zones—spanning mission-critical customer domains and internal partner domains—from on-premises BIND servers to Cloud DNS. During discovery, you observe the following constraints and findings:
NS and SOA records, as well as CNAME and MX targets that lack trailing periods.Which DNS migration strategy should you implement?
CNAME or MX targets, update registrar NS records for all 40 zones simultaneously, and confirm zone transfer completion solely by checking the gcloud dns record-sets list output.Increasing TTL values before a DNS migration extends how long recursive resolvers and clients cache old IP addresses or server targets. Importing unmodified BIND files and executing a simultaneous registrar update attempts to shift all domains at once, while relying solely on gcloud dns record-sets list only verifies stored control-plane configuration rather than live resolution behavior.
CNAME and MX targets: Leaving out trailing periods on external target domains causes Cloud DNS to treat those targets as subdomains of the managed zone origin, breaking mail routing and external aliases.gcloud confirms database presence, not that authoritative Cloud DNS name servers return expected DNS answers or that legacy BIND servers have stopped receiving traffic.$ORIGIN.dig or nslookup) and log inspection across both target and legacy servers.SOA record using --delete-all-existing while importing only A and AAAA records initially, migrate registrar NS delegation in phased waves before importing MX and CNAME records, and shut down the on-premises BIND servers once Cloud DNS query logs show incoming traffic for each wave.This strategy uses a phased wave-based cutover and retains the legacy SOA record via --delete-all-existing, but splits the DNS record import so that registrar NS delegation moves to Cloud DNS before MX and CNAME records exist in the new managed zones. It also treats the first appearance of traffic in Cloud DNS logs as the signal to retire the legacy servers.
MX (email delivery) or CNAME (application aliases) records receive NXDOMAIN or NODATA responses until those records are imported, disrupting production services.--delete-all-existing is only appropriate when a non-Cloud DNS primary name server remains authoritative in a split-provider configuration, not for a full migration to Cloud DNS.A, AAAA, CNAME, MX, TXT, SRV) must be imported and verified in the Cloud DNS managed zone before changing registrar delegation.MX and CNAME—were fully imported and validated before updating registrar NS records, Cloud DNS's native SOA record was preserved, and legacy BIND servers were kept running until their query logs dropped to zero.NS/SOA records and appending trailing periods to FQDNs in CNAME/MX records before importing into Cloud DNS, validate resolution directly against Cloud DNS name servers, execute a phased wave-based cutover at the registrar starting with low-risk zones, and verify zero residual query traffic on the legacy BIND servers before decommissioning.A phased, pre-validated DNS zone migration combines pre-migration record sanitization, TTL reduction, direct authoritative testing, wave-based registrar delegation cutovers, and post-migration log verification. This structured lifecycle ensures data integrity and uninterrupted name resolution across complex multi-zone environments.
.) to external CNAME and MX target FQDNs prevents RFC-compliant relative domain expansion inside Cloud DNS.dig @<cloud-dns-ns>) confirms every record resolves accurately before any registrar delegation changes occur.Unlike big-bang or unvalidated imports, this strategy systematically mitigates every DNS migration failure mode—syntax misinterpretation, stale caching, delegation errors, and premature decommissioning—while keeping production blast radius minimal.
--delete-all-existing and --replace-origin-ns to preserve the original apex NS and SOA records, perform a big-bang cutover of all 40 zones during a single maintenance window, test resolution through a public recursive resolver, and decommission the legacy BIND servers immediately after cutover.Using --delete-all-existing and --replace-origin-ns during a Cloud DNS import forces Cloud DNS to overwrite its automatically provisioned zone apex NS and SOA records with those from the source BIND file. Combining this with a big-bang cutover shifts all 40 zones simultaneously at the domain registrar and immediately powers down the legacy authoritative infrastructure.
CNAME and MX targets omit trailing periods causes Cloud DNS to follow RFC relative naming rules and append the zone origin (for example, turning mail.partner.com into mail.partner.com.example.com.).--replace-origin-ns flag is intended only for specialized split-provider authoritative DNS architectures where a non-Cloud DNS primary name server remains active.Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated