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.
You are migrating the public DNS zone example.com from a legacy BIND server to Cloud DNS. The exported BIND zone file has the following characteristics:
@ to represent the zone apex.NS and SOA records.MX record pointing to mail.example.net without a trailing dot.You must migrate the records, sign the zone with DNSSEC using ECDSAP256SHA256, and validate the DNSSEC chain before updating your domain registrar. Which sequence of actions should you take?
--dnssec-state=on and all four KSK/ZSK ECDSAP256SHA256 flags. Import the unmodified BIND zone file using gcloud dns record-sets import --delete-all-existing, and then update your registrar's NS and DS records before verifying propagation with DNSViz.This approach correctly initializes a new Cloud DNS managed zone with DNSSEC and ECDSAP256SHA256 enabled prior to populating records, but attempts to import an unmodified BIND zone file without specifying the BIND format flag and pushes registrar updates before validating DNSSEC.
--zone-file-format flag instructs gcloud dns record-sets import to expect a YAML-formatted record file rather than a standard BIND zone file, causing the import operation to fail.--zone-file-format, Cloud DNS treats @ literally rather than as the zone apex, and interprets mail.example.net without a trailing dot as relative (mail.example.net.example.com.).NS conflict and premature delegation: Legacy NS records at the apex fail validation during import unless removed (or intentionally replacing origin NS records matching Cloud DNS shards). Updating the registrar before running pre-delegation checks risks SERVFAIL outages for validating resolvers.gcloud dns record-sets import defaults to YAML format unless --zone-file-format is explicitly passed.The BIND zone file were converted to valid YAML (or --zone-file-format were added after fixing @, trailing dots, and apex NS/SOA records) and DNSSEC validation were completed prior to modifying the registrar.
gcloud dns record-sets import with --zone-file-format and --replace-origin-ns. Then run gcloud dns managed-zones update with --dnssec-state=on and --ksk-algorithm=ECDSAP256SHA256, and add the DS record at your registrar.This sequence creates an unsigned Cloud DNS managed zone, imports a BIND zone file while attempting to overwrite the zone's authoritative NS records with --replace-origin-ns, and then tries to enable DNSSEC afterward using a single KSK algorithm flag.
gcloud, providing --ksk-algorithm alone fails validation because all four parameters (--ksk-algorithm, --zsk-algorithm, --ksk-key-length, and --zsk-key-length) must be supplied together.--replace-origin-ns with legacy NS records causes conflicts or replaces Cloud DNS's assigned name servers, while retaining @ and omitting trailing dots creates literal @ entries and relative mail.example.net.example.com. targets.ECDSAP256SHA256 requires specifying a 256-bit key length for both KSK and ZSK.The zone contained 3,000 or fewer record sets, the BIND file were cleaned to replace @ and add trailing dots while matching Cloud DNS NS records, and all four KSK/ZSK algorithm and key-length flags were provided alongside pre-delegation validation.
NS and SOA records from the BIND file, create the managed zone with --dnssec-state=on using default algorithms, and import the records with --zone-file-format. Next, run gcloud dns managed-zones update to set ECDSAP256SHA256 for KSK and ZSK, and verify with Zonemaster before updating the registrar.This sequence removes conflicting apex NS and SOA records and creates a DNSSEC-enabled zone with default RSASHA256 algorithms before importing the 4,200 records, intending to update the signing algorithms to ECDSAP256SHA256 afterward.
@ and relative MX target errors: Failing to replace @ with example.com. creates literal @.example.com. records instead of apex records, and omitting the trailing dot on mail.example.net causes Cloud DNS to interpret the target as mail.example.net.example.com..2048-bit KSK, 1024-bit ZSK) rather than ECDSAP256SHA256.@ as a literal character in BIND imports and treats any domain name lacking a trailing dot as relative to the zone's DNS suffix.The ECDSAP256SHA256 KSK/ZSK algorithm and key-length flags were specified at zone creation time (rather than after importing 4,200 records), and the BIND file were updated to replace @ and add the trailing dot to mail.example.net..
NS and SOA records, replace @ with example.com., and add a trailing dot to mail.example.net.. Create the managed zone with --dnssec-state=on and all four --ksk-algorithm, --zsk-algorithm, --ksk-key-length, and --zsk-key-length flags, import with --zone-file-format, and validate with Verisign DNSSEC debugger before updating the registrar.This sequence properly prepares a BIND zone file for Cloud DNS RFC-compliant parsing, bypasses the 3,000-record-set DNSSEC toggle limit by enabling ECDSAP256SHA256 signing on an empty zone at creation time, and verifies the cryptographic chain of trust before changing public delegation.
--dnssec-state=on when creating the zone allows all 4,200 records to be imported and automatically signed.--ksk-algorithm ECDSAP256SHA256, --zsk-algorithm ECDSAP256SHA256, --ksk-key-length 256, and --zsk-key-length 256) ensures valid key generation without mismatched algorithms.NS and SOA records prevents conflicts with Cloud DNS's authoritative apex records, replacing @ with example.com. ensures apex records bind to the domain root rather than a literal @ label, and appending a trailing dot to mail.example.net. prevents relative expansion to mail.example.net.example.com..DNSKEY, RRSIG, and DS parameters before updating the registrar.DS records or invalid signing keys during cutover.--zone-file-format.Unlike post-import DNSSEC activation or partial CLI flags, creating the zone pre-configured with all four ECDSA parameters and importing a sanitized BIND file avoids hitting the 3,000-record limit and prevents syntax-induced routing errors before live traffic switches over.
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