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 manages a public parent zone (example.com) and a delegated subdomain (portal.example.com) in Cloud DNS, with DNSSEC enabled on both zones. Your hybrid network also relies on a Cloud DNS forwarding zone and an inbound server policy. After delegating portal.example.com, you observe the following behavior:
8.8.8.8) receive SERVFAIL responses.dig portal.example.com @ns-cloud-e1.googledomains.com) returns NOERROR with the expected A record.Which approach should you take to troubleshoot the validation failure and meet your DNSSEC requirements?
Cloud DNS forwarding zones direct outbound DNS queries from a VPC network to specified target name servers (such as on-premises BIND or Active Directory servers), while inbound server policies expose internal VPC DNS resolution endpoints so on-premises hosts can query Cloud DNS private zones and forwarding zones. Neither mechanism acts as a DNSSEC-validating recursive resolver or signs zone data.
--dnssec-state on) is supported only on public managed zones, not on private zones, forwarding zones, or server policies.DNSKEY and RRSIG records, but cryptographic signature verification must be performed by a validating DNS resolver.169.254.169.254) from a VM tests VPC path resolution, not the public delegation chain of trust (DS to DNSKEY) that is causing 8.8.8.8 to return SERVFAIL.35.199.192.0/19 or outbound endpoints.DNS_RESOLVER IP addresses inside VPC subnets to accept port 53 queries over Cloud VPN or Cloud Interconnect.NOERROR with signed records even when the parent DS record is broken; only validating resolvers enforce the chain of trust and return SERVFAIL on mismatch.You were troubleshooting private zone or inbound forwarding reachability rather than DNSSEC validation—for example, confirming whether a Compute Engine VM uses 169.254.169.254 to reach a private zone or forwarding target.
Full DNSSEC protection requires three distinct layers: signing the DNS zone, publishing a matching DS record in the parent zone or TLD registry, and querying through a validating resolver (such as Google Public DNS or a local validating caching resolver).
Running dig +short NS retrieves only the authoritative name server (NS) records for a domain. Switching denial-of-existence between NSEC3 (default) and NSEC changes how non-existent domain names are proven, while TTL controls how long resolvers cache resource records.
dig +short NS omits DS, DNSKEY, and RRSIG records as well as status codes (SERVFAIL vs. NOERROR), so it cannot reveal a broken DNSSEC chain of trust.NSEC3 vs. NSEC: Both NSEC and NSEC3 provide authenticated denial of existence; switching from NSEC3 to NSEC only reduces response packet size and removes zone-walking protection (hash salting), and requires disabling and re-enabling DNSSEC—it does not resolve a DS mismatch.259200 seconds (3 days) in DNSSEC-enabled zones is explicitly discouraged and does not fix signature validation errors.DS record is removed beforehand.You had already verified a healthy DS chain of trust and specifically wanted to reduce DNSSEC negative-response sizes or allow validating resolvers to synthesize negative answers using cached NSEC records while keeping TTLs well below 259200 seconds.
To inspect DNSSEC failures effectively, administrators must examine the full response header and cryptographic records (+trace or DNSSEC debugging tools) rather than +short NS summaries.
DNSSEC validation ensures the authenticity and integrity of DNS responses by cryptographically verifying RRSIG signatures against a zone's Zone Signing Key (ZSK) and Key Signing Key (KSK), chained upward through a Delegation Signer (DS) record in the parent zone. When a validating recursive resolver encounters a DS record in example.com that does not match an active DNSKEY in portal.example.com, it rejects the response as bogus and returns SERVFAIL, whereas the authoritative Cloud DNS name server continues to return NOERROR because authoritative servers do not validate parent delegations.
dig +trace portal.example.com traces resolution from the root zone through example.com to portal.example.com, exposing DS, DNSKEY, NSEC3, and RRSIG records at each hop. Pairing this with DNSViz, Verisign DNSSEC debugger, or Zonemaster identifies mismatched or mistyped DS records.gcloud dns dns-keys describe --zone portal-zone 0 --format="value(ds_record())" retrieves the exact DS record for the subdomain's KSK so you can update the DS and NS records in the parent zone example.com.169.254.169.254 for internal Cloud DNS forwarding zones.dig +trace reveals exact RRSIG timestamps, algorithm numbers, and DS digests across every delegation boundary.DS matches the subdomain KSK, Cloud DNS automatically rotates keys and signs records.This approach directly fixes the root cause of the SERVFAIL mismatch between example.com and portal.example.com and places DNSSEC validation at the proper architectural layer—the recursive resolver—without disrupting Cloud DNS forwarding zones.
A Cloud DNS outbound server policy overrides a VPC network's default name resolution order by sending all VM DNS queries to specified alternative name servers. Disabling DNSSEC on a managed zone (--dnssec-state off) stops Cloud DNS from serving DNSKEY and RRSIG signatures for that zone.
8.8.8.8 prevents VPC workloads from resolving Cloud DNS private zones, forwarding zones, peering zones, and Compute Engine internal DNS zones.SERVFAIL validation errors: Turning off DNSSEC on portal.example.com while a DS record remains in the parent example.com zone guarantees that all DNSSEC-validating resolvers will continue returning SERVFAIL because the parent still advertises that the child must be signed.portal.example.com rather than fixing the underlying DS or key mismatch.DS records from the parent zone or domain registrar first and waiting for cached DS records to expire (often 24 hours or longer) before running gcloud dns managed-zones update --dnssec-state off.NOERROR when DNSSEC is misconfigured, masking parent-zone mismatches from basic non-validating checks.You intentionally wanted to route all VPC DNS traffic to an external or on-premises resolver that also handles internal zones, and you had already removed the DS record from the parent zone and waited for its TTL to expire before disabling DNSSEC.
When migrating or disabling DNSSEC-signed zones, maintaining synchronization between the child zone's DNSKEY and the parent zone's DS record is critical to preventing resolver blackouts.
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