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 the example.com domain from a legacy BIND DNS provider to Cloud DNS. The exported BIND zone file contains:
SOA, NS, A, and TXT (SPF) records using the @ symbolMX and CNAME records referencing external hostnames without trailing periods (for example, 10 mx1.mailprovider.net)After migration, VPC workloads must resolve api.example.com through a private zone using a health-checked failover policy across regional Internal Application Load Balancers (us-central1 primary, us-east1 backup), while still resolving public www.example.com records.
Which configuration steps should you perform?
NS and SOA records, replacing @ with example.com., and appending trailing periods (.) to external MX and CNAME targets, then import it into the public zone with --zone-file-format. 2. Create a private zone for example.com that includes both www.example.com and api.example.com, configuring api.example.com as an A record with a FAILOVER routing policy and GEO backup targets pointing to Internal Application Load Balancers with global access enabled.
This solution properly sanitizes a legacy BIND zone file for Cloud DNS standards before import and implements a split-horizon private zone with a health-checked failover routing policy for internal application traffic.
A, CNAME, MX, TXT):
NS and SOA records preserves Cloud DNS's authoritative name servers and SOA metadata.@ with example.com. ensures apex A and TXT (SPF) records are properly named because Cloud DNS treats @ literally..) to external MX and CNAME targets prevents Cloud DNS from appending .example.com. to external hostnames.--zone-file-format tells gcloud dns record-sets import to parse BIND syntax rather than YAML.www.example.com: Because a private zone for example.com overrides the entire public zone for authorized VPC networks, explicitly adding www.example.com to the private zone prevents VPC workloads from receiving NXDOMAIN responses.FAILOVER routing policies require A (or public AAAA) records for health checking and mandate GEO (--routing-policy-backup-data-type=GEO) as the backup target type.MX and CNAME records during cutover.us-central1 to the us-east1 backup target if primary health checks fail.It adheres strictly to Cloud DNS RFC-compliant import rules, split-horizon override behavior, and private routing policy prerequisites without breaking existing services during or after migration.
NS and SOA records, replace @ with example.com., and append trailing periods (.) to external MX and CNAME targets, then import the file into the public zone with --zone-file-format. 2. Create a private zone for example.com including www.example.com, and configure api.example.com with a combined WRR and GEO routing policy (weight=100 primary, weight=0 backup) targeting regional Internal Application Load Balancers without enabling global access.
This option correctly prepares and imports the BIND zone file into the public zone and includes www.example.com in the private zone, but attempts to build failover by combining Weighted Round Robin (WRR) and Geolocation (GEO) routing policies without enabling global access on the internal load balancers.
WRR routing policy with a GEO routing policy on the same resource record set. Only one routing policy type can be applied at a time, with the sole exception of a FAILOVER routing policy using a GEO backup target.us-east1 backup load balancer fail.WRR policies distribute traffic proportionally based on non-negative weights (0 to 1000), and zero-weighted targets act as active-passive backups only when health checks are attached exclusively to non-zero targets—not in combination with GEO rules.Step 2 instead configured a FAILOVER routing policy (with GEO as the backup target type) or a pure WRR policy without GEO rules, and global access was enabled on both regional Internal Application Load Balancers.
When configuring WRR for active-passive failover without FAILOVER mode, engineers must ensure zero-weighted backup targets do not have health checks attached; otherwise, if all targets fail health checks, Cloud DNS returns the non-zero targets and ignores the zero-weighted targets.
gcloud dns record-sets import --zone-file-format --delete-all-existing --replace-origin-ns so Cloud DNS automatically converts @ records and resolves external MX and CNAME targets. 2. Create a private zone for example.com containing only api.example.com with a FAILOVER routing policy pointing to regional Internal Application Load Balancers with global access enabled, relying on public fallback for www.example.com.
This approach attempts to import a raw third-party BIND zone file while overwriting Cloud DNS's authoritative NS and SOA records, and relies on a partial private zone falling back to a public zone for missing records.
--delete-all-existing and --replace-origin-ns forces Cloud DNS to replace its automatically assigned Google Cloud name server (NS) and SOA records with the legacy provider's records, breaking authoritative resolution once you migrate.@ and relative hostnames: Cloud DNS treats @ literally rather than expanding it to the zone apex, and interprets domain names without a trailing period (.) as relative to example.com. (for example, turning mx1.mailprovider.net into mx1.mailprovider.net.example.com.).www.example.com resolution in VPCs: In a split-horizon DNS configuration, a private zone for example.com completely overrides the public zone for example.com within authorized VPC networks. Queries from VPC VMs for www.example.com return NXDOMAIN rather than falling back to the public zone.example.com.) instead of @ in BIND imports.MX, CNAME, and PTR records must end with a trailing dot (.).You were intentionally running a multi-provider split-authoritative public DNS deployment with a non-Cloud DNS primary server (requiring --delete-all-existing and --replace-origin-ns), had already sanitized @ and trailing dots in the BIND file, and did not need VPC VMs to resolve www.example.com via the public zone.
--zone-file-format flag so Cloud DNS treats @ as the zone apex and normalizes relative MX and CNAME targets automatically. 2. Create a Cloud DNS forwarding zone for example.com and configure api.example.com as a CNAME record with a health-checked FAILOVER routing policy targeting the regional Internal Application Load Balancers.
This option attempts to import a BIND file using the YAML import parser and tries to host a health-checked CNAME failover routing policy inside a Cloud DNS forwarding zone.
--zone-file-format flag causes gcloud dns record-sets import to expect a YAML-formatted records file (kind: dns#resourceRecordSet), resulting in a syntax failure when given a BIND zone file. Moreover, Cloud DNS never auto-converts @ or omits trailing-dot relative resolution rules.CNAME records: Even within a standard private zone, Cloud DNS routing policies do not support health checks on CNAME records. Health checks in private zones are only supported for A records pointing to internal load balancers.gcloud dns record-sets import defaults to YAML format unless --zone-file-format is specified for BIND files.A records (private and public zones) and AAAA records (public zones only).The import file were converted to Cloud DNS YAML format with fully qualified names (removing @ and adding trailing dots), and a standard private zone (not a forwarding zone) were created with A records using a FAILOVER policy and global access enabled on the internal load balancers.
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