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 manage a public Cloud DNS zone with fewer than 1,000 record sets that currently has DNSSEC enabled using default RSASHA256 keys (2048-bit KSK, 1024-bit ZSK) and an active DS record at your registrar. You need to update the zone to meet these requirements:
ECDSAP256SHA256 for smaller signed responses.RRSIG generation continue seamlessly.Which procedure should you follow?
gcloud dns managed-zones update with --zsk-algorithm=ECDSAP256SHA256 and --zsk-key-length=256, keeping the RSASHA256 KSK to preserve the registrar DS record, and schedule periodic KSK and ZSK rollovers via Cloud Scheduler.This approach tries to perform an in-place ZSK-only algorithm change on an active DNSSEC-enabled zone to avoid updating the DS record at the domain registrar, while attempting to manage KSK and ZSK rollovers through external automation.
gcloud dns managed-zones update, Cloud DNS requires providing all four parameters (--ksk-algorithm, --zsk-algorithm, --ksk-key-length, and --zsk-key-length).RSASHA256 for the KSK and ECDSAP256SHA256 for the ZSK creates a mixed-algorithm zone. Some validating resolvers fail validation when a zone contains DNSKEY algorithms that are not used to sign every record in the zone.RSASHA256 also fails the requirement to switch both KSK and ZSK to ECDSAP256SHA256.Keeping RSASHA256 for the KSK while using ECDSAP256SHA256 for the ZSK is only appropriate when your TLD registry or registrar does not support ECDSA, you accept potential resolver compatibility risks, and you first deactivate DNSSEC at the registrar and disable it on the zone while passing all four algorithm and key-length flags.
transfer, import externally generated ECDSAP256SHA256 KSK/ZSK DNSKEY records along with pre-signed RRSIG records, and configure a 7-day signature validity period and 1-day refresh period to automate key rollovers.Transfer State and Signature Timing Actually DoThe Transfer DNSSEC state in Cloud DNS is designed exclusively for migrating an already DNSSEC-signed zone between DNS operators without breaking the cryptographic chain of trust. It allows temporary coexistence of external DNSKEY records during a provider migration.
RRSIG imports are not supported: Cloud DNS automatically generates and manages all RRSIG records whenever DNSSEC is enabled. Administrators do not generate, upload, or manually sign zone resource record sets.RRSIG generation and rotation that cannot be modified by users.Transfer state: Using Transfer state for an existing Cloud DNS zone to swap algorithms introduces unnecessary operational complexity and does not leave the zone in the standard On state required for normal automated management.1,533,600 seconds), record TTLs in DNSSEC-enabled zones should not exceed 3 days (259,200 seconds) to avoid synchronized query spikes when signatures expire.DNSKEY records can only be added manually when a public DNSSEC-enabled zone is in the Transfer state during an active migration.Using the Transfer state and importing external DNSKEY records would apply if you were migrating a live DNSSEC-signed zone from another DNS provider into Cloud DNS without interrupting validation, following RFC 6781 migration procedures—though Cloud DNS would still manage RRSIG signing and signature lifetimes automatically.
--ksk-algorithm, --zsk-algorithm, --ksk-key-length, and --zsk-key-length all set for ECDSAP256SHA256, and then publish the new DS record at the registrar while Cloud DNS automates ZSK rollovers and RRSIG signing.In Cloud DNS, changing the cryptographic signing algorithm or key length of an active DNSSEC-enabled managed zone requires disabling DNSSEC, applying the updated KSK and ZSK parameters, and re-enabling DNSSEC. Because removing RRSIG and DNSKEY records while a DS record still exists at the parent TLD registry breaks the chain of trust, the DS record must be removed at the registrar first.
SERVFAIL) when DNSSEC is turned off in Cloud DNS.ECDSAP256SHA256 to both keys: When re-enabling DNSSEC (--dnssec-state=on), specifying all four required flags (--ksk-algorithm=ECDSAP256SHA256, --ksk-key-length=256, --zsk-algorithm=ECDSAP256SHA256, and --zsk-key-length=256) ensures uniform ECDSA signing and smaller DNS response packets.RRSIG signing: Once DNSSEC is enabled, Cloud DNS automatically generates the new KSK and ZSK DNSKEY records, signs all zone record sets with RRSIG records, and performs fully automatic ZSK rotations.DS record via gcloud dns dns-keys list and adding it at the registrar restores full end-to-end DNSSEC validation.RRSIG lifecycle: Cloud DNS manages fixed signature timing automatically, including a 21-day validity period, 18-day refresh period, and 3-day re-sign period.This workflow follows the exact Cloud DNS operational lifecycle for modifying DNSSEC cryptographic parameters while maintaining domain availability and automated ZSK and RRSIG management.
ECDSAP256SHA256 KSK and ZSK flags and --denial-of-existence=NSEC, and rely on Cloud DNS to automatically rotate the KSK, update the DS record at the registrar, and re-sign RRSIG records.This option correctly identifies that disabling and re-enabling DNSSEC with all four algorithm and key-length flags is required to change to ECDSAP256SHA256, and that NSEC produces slightly smaller responses than NSEC3 while enabling negative response caching.
DS record in the parent TLD zone, observe missing or mismatched DNSKEY and RRSIG records in Cloud DNS, and reject responses for the domain.DS record is manually published at the registrar.This workflow would only work safely if the domain had never had DNSSEC activated at the registrar (meaning no DS record existed in the parent zone) and if the administrator manually uploaded the new DS record to the registrar after re-enabling DNSSEC.
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