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 its DNS infrastructure to Cloud DNS across a hub-and-spoke VPC topology connected by VPC Network Peering. Only hub-vpc in hub-project has Cloud Interconnect connectivity to on-premises DNS servers hosting corp.example.com, while spoke-vpc resides in spoke-project. You are also migrating the public example.com zone (1,200 records) with DNSSEC and least-privilege Cloud IAM.
Your solution must meet these requirements:
spoke-vpc must resolve corp.example.com while retaining Compute Engine internal DNS resolution.spoke-project DNS administrator needs minimal IAM permissions on hub-project to configure cross-VPC resolution.example.com responses must minimize DNSSEC packet sizes and prevent signature-expiration query spikes.Which configuration should you implement?
spoke-vpc to directly query the corp.example.com forwarding zone in hub-project over VPC Network Peering, grant roles/dns.admin on hub-project to the spoke administrator, and enable DNSSEC on example.com with RSASHA256, NSEC3, and a 1533600-second TTL before adding the DS record at the registrar.This approach attempts to share an outbound Cloud DNS forwarding zone directly across a VPC Network Peering connection while granting broad administrative permissions (roles/dns.admin) on the hub project and configuring DNSSEC with RSASHA256, NSEC3, and a 1533600-second TTL.
spoke-vpc has IP connectivity to on-premises via imported custom routes from hub-vpc, queries sent by spoke-vpc VMs to their metadata server (169.254.169.254) for a forwarding zone in hub-project will fail.roles/dns.admin on hub-project gives the spoke administrator full permissions to create, modify, and delete all DNS zones and records in the hub, far exceeding the permission needed to target hub-vpc from a peering zone.1533600-second (17.75-day) TTL matches Cloud DNS's minimum signature validity (refresh - jitter), exceeding the recommended maximum TTL of 259200 seconds (3 days) and causing clients to flood authoritative servers when signatures expire. Furthermore, RSASHA256 and NSEC3 generate larger DNSSEC-signed responses than ECDSAP256SHA256 and NSEC.1533600 seconds.NSEC3 limits zone walking, it produces slightly larger responses and prevents resolvers from synthesizing negative responses.spoke-vpc had its own direct Cloud Interconnect or Cloud VPN connection to on-premises, full DNS administrative access on hub-project was intentionally required, and NSEC3 zone-walking protection was prioritized over minimizing response sizes and respecting the 3-day TTL limit.
corp.example.com in spoke-project and a Cloud DNS peering zone in hub-project targeting spoke-vpc, grant roles/dns.reader on hub-project to the spoke administrator, and enable DNSSEC on example.com with RSASHA512, NSEC3, and an 86400-second TTL before adding the DS record at the registrar.This configuration places the forwarding zone in spoke-project, creates a DNS peering zone in hub-project targeting spoke-vpc, assigns roles/dns.reader on hub-project, and configures DNSSEC using RSASHA512, NSEC3, and an 86400-second (24-hour) TTL.
hub-project targeting spoke-vpc allows hub-vpc to resolve records in spoke-vpc, rather than enabling spoke-vpc to use hub-vpc's Cloud Interconnect path. Moreover, a forwarding zone in spoke-project cannot reach on-premises servers across VPC Network Peering.roles/dns.reader role provides read-only visibility into Cloud DNS records and zones, but it lacks the dns.networks.targetWithPeeringZone permission required to establish a DNS peering zone targeting a producer network.RSASHA512 is not widely supported by resolvers and registries and produces much larger signed packets than ECDSAP256SHA256, while NSEC3 generates larger negative responses than NSEC and prevents RFC 8198 negative-response synthesis.hub-vpc) must be the DNS producer, while the requesting network (spoke-vpc) must host the peering zone as the DNS consumer.roles/dns.reader is intended for auditing or viewing DNS configurations, whereas roles/dns.peer is required for cross-network DNS peering.86400-second TTL satisfies the 3-day (259200-second) ceiling, it cannot compensate for the broken forwarding topology and suboptimal signing algorithm.spoke-vpc owned the Cloud Interconnect link to on-premises and hub-vpc needed to consume DNS records from spoke-vpc, the spoke administrator only needed read-only access to hub-project, and RSASHA512 with NSEC3 was required despite larger response sizes.
corp.example.com in hub-project authorized for hub-vpc, create a Cloud DNS peering zone in spoke-project targeting hub-vpc, grant roles/dns.peer on hub-project to the spoke administrator, and enable DNSSEC on example.com with ECDSAP256SHA256, NSEC, and TTLs of 259200 seconds or less before adding the DS record at the registrar.This solution combines a Cloud DNS outbound forwarding zone in the hub VPC, a Cloud DNS peering zone in the spoke VPC, least-privilege Cloud IAM (roles/dns.peer), and optimized DNSSEC settings (ECDSAP256SHA256, NSEC, and TTLs at or below 259200 seconds) for a secure, high-performance migration.
corp.example.com and preserves internal DNS: Because outbound forwarding cannot traverse VPC Network Peering, hub-vpc is designated as the single network hosting the corp.example.com forwarding zone over Cloud Interconnect. The peering zone in spoke-project directs corp.example.com lookups to hub-vpc, following hub-vpc's name resolution order while leaving Compute Engine internal DNS (*.internal) intact in spoke-vpc.roles/dns.peer on hub-project provides the exact dns.networks.targetWithPeeringZone permission needed for the spoke administrator to bind a peering zone to hub-vpc, without granting zone-editing privileges in hub-project.ECDSAP256SHA256 with NSEC produces the smallest DNSSEC-signed packets in Cloud DNS and allows validating resolvers (such as Google Public DNS) to synthesize negative responses from cached NSEC records. Keeping TTLs at or below 259200 seconds (3 days) ensures caches refresh well ahead of Cloud DNS's fixed 17.75-day (1533600-second) minimum signature validity, preventing synchronized expiration spikes. Adding the DS record at the registrar completes the chain of trust.spoke-vpc) to producer (hub-vpc).Unlike direct forwarding over VPC peering (which fails) or outbound alternative name servers (which break .internal resolution), hub-and-spoke DNS peering with roles/dns.peer and ECDSAP256SHA256/NSEC fulfills every security, access-control, and performance constraint.
spoke-project pointing to the on-premises servers, grant roles/editor on hub-project to the spoke administrator, and enable DNSSEC on example.com with ECDSAP256SHA256, NSEC3, and a 604800-second TTL before adding the DS record at the registrar.An outbound DNS server policy configured with an alternative name server overrides the default VPC name resolution order and redirects all DNS queries from VMs in that VPC to the specified external or on-premises DNS servers. This option also pairs that policy with the basic roles/editor role and a 604800-second (7-day) TTL under NSEC3.
*.internal), Cloud DNS private zones, forwarding zones, and peering zones for VMs in spoke-vpc. Additionally, because spoke-vpc lacks direct Cloud Interconnect connectivity, outbound forwarding cannot traverse VPC Network Peering to reach the on-premises servers.roles/editor role grants broad read and modify access across nearly all Google Cloud resources in hub-project, introducing severe security risk compared to DNS-specific IAM roles.604800-second (7-day) TTL exceeds the recommended 259200-second (3-day) maximum for DNSSEC-signed zones, increasing the risk of synchronized cache-expiration load spikes. Selecting NSEC3 also yields larger responses than NSEC.roles/owner, roles/editor) should be avoided for DNS management because they grant permissions far beyond DNS operations.All DNS traffic from spoke-vpc (including internal queries) had to be routed to on-premises servers over a direct connection in spoke-vpc, broad project-wide permissions were acceptable, and NSEC3 with a 7-day TTL was explicitly mandated.
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