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 uses a hub-and-spoke network where hub-vpc connects to on-premises via HA VPN and spoke-vpc connects to hub-vpc via VPC Network Peering. A public Cloud DNS zone for example.com. hosts www.example.com.
You must implement name resolution to meet these requirements:
corp.example.com. on-premises via hub-vpc.spoke-vpc must resolve db.dev.example.com privately, www.example.com publicly, and Compute Engine .internal names.dev.example.com. records from spoke-vpc.Which Cloud DNS configuration should you implement?
dev.example.com. authorized for spoke-vpc. Configure an outbound DNS server policy on spoke-vpc specifying the on-premises DNS servers as alternative name servers, and authorize both hub-vpc and spoke-vpc on a corp.example.com. forwarding zone. Create an inbound DNS server policy on spoke-vpc, then configure on-premises conditional forwarding for dev.example.com. to the spoke-vpc inbound forwarder IP.This configuration attempts to use an outbound DNS server policy with alternative name servers for outbound resolution, shares a single forwarding zone across peered VPCs, and exposes an inbound server policy directly from spoke-vpc.
spoke-vpc: In VPC name resolution order, an outbound server policy is evaluated first (step 1), superseding all other VPC-scoped DNS mechanisms. Sending all queries to alternative name servers prevents spoke-vpc VMs from resolving the dev.example.com. private zone, the corp.example.com. forwarding zone, and Compute Engine internal DNS (.internal) records.spoke-vpc directly on a forwarding zone whose targets are only reachable via hub-vpc fails because Cloud DNS outbound forwarding cannot traverse VPC Network Peering.spoke-vpc's inbound forwarder IP through hub-vpc.35.199.192.0/19 must return directly to the VPC where the forwarding query originated.An outbound server policy is appropriate only when all DNS queries from a VPC must be inspected or filtered by centralized on-premises resolvers (and local private zones or .internal resolution are not needed), while an inbound server policy in spoke-vpc would work only if spoke-vpc had its own direct VPN or Interconnect connection to on-premises.
dev.example.com. authorized for spoke-vpc. Create a forwarding zone for corp.example.com. targeting the on-premises DNS servers and authorize both hub-vpc and spoke-vpc to use it, exporting custom routes over VPC Network Peering. Create an inbound DNS server policy in hub-vpc, then configure on-premises conditional forwarding for dev.example.com. to the hub-vpc inbound forwarder IP.This configuration scopes the private zone to dev.example.com. and deploys an inbound DNS server policy in hub-vpc, but it relies on VPC Network Peering route exchange for outbound forwarding from spoke-vpc and omits a DNS peering zone in hub-vpc.
spoke-vpc: Cloud DNS outbound forwarding cannot traverse VPC Network Peering, even when custom routes to on-premises subnets are exported and imported between hub-vpc and spoke-vpc. Furthermore, Cloud DNS sends outbound queries from 35.199.192.0/19 and discards responses not routed back to the exact VPC where the query originated.dev.example.com. fails: An inbound DNS server policy resolves incoming queries using the name resolution order of the VPC network where the policy is attached (hub-vpc). Because VPC Network Peering does not share DNS zones, hub-vpc has no visibility into spoke-vpc's dev.example.com. private zone unless you create a DNS peering zone in hub-vpc targeting spoke-vpc.spoke-vpc requires direct hybrid connectivity (such as HA VPN or Cloud Interconnect) in spoke-vpc itself—or must be accessed indirectly through a DNS peering zone targeting hub-vpc.Authorizing multiple VPC networks on a single forwarding zone works only when each authorized VPC network has its own direct hybrid connectivity and separate return routing paths to on-premises, rather than transiting through a peered hub VPC.
dev.example.com. authorized for spoke-vpc. Create a forwarding zone for corp.example.com. authorized for hub-vpc targeting the on-premises DNS servers, and a peering zone for corp.example.com. in spoke-vpc targeting hub-vpc. Create an inbound DNS server policy in hub-vpc and a peering zone for dev.example.com. in hub-vpc targeting spoke-vpc, then configure on-premises conditional forwarding for dev.example.com. to the hub-vpc inbound forwarder IP.This design combines scoped private zones, outbound forwarding, unidirectional DNS peering, and a local inbound DNS server policy to align with Cloud DNS VPC name resolution order and longest-suffix matching.
corp.example.com.): Cloud DNS outbound forwarding cannot traverse VPC Network Peering, and responses to 35.199.192.0/19 must return to the originating VPC. Placing the forwarding zone in hub-vpc and creating a DNS peering zone in spoke-vpc targeting hub-vpc routes spoke-vpc queries through hub-vpc's resolution order and HA VPN path.dev.example.com. and www.example.com): Scoping the private zone specifically to the subdomain dev.example.com. ensures queries for db.dev.example.com match that private zone by longest-suffix matching, while queries for www.example.com have no matching private zone and fall through to Compute Engine internal DNS and public DNS. Because no outbound server policy is configured, .internal resolution remains intact.spoke-vpc resolution (dev.example.com.): Inbound server policy entry points are not reachable across VPC Network Peering. Deploying the inbound server policy in hub-vpc (where the HA VPN terminates) alongside a DNS peering zone in hub-vpc targeting spoke-vpc allows hub-vpc to resolve dev.example.com. on behalf of on-premises conditional forwarders..internal) and public DNS resolution without extra hops.hub-vpc, avoiding asymmetric return routing for 35.199.192.0/19.Unlike outbound server policies or apex-level private zones, this architecture respects Cloud DNS precedence rules and peering boundaries, delivering seamless resolution across both VPCs and on-premises.
example.com. authorized for spoke-vpc containing db.dev.example.com, and rely on fallback to the public example.com. zone for www.example.com. Create a forwarding zone for corp.example.com. authorized for hub-vpc targeting the on-premises DNS servers, and a peering zone for corp.example.com. in spoke-vpc targeting hub-vpc. Create an inbound DNS server policy in hub-vpc and a peering zone for example.com. in hub-vpc targeting spoke-vpc.This configuration correctly uses a DNS peering zone for corp.example.com. and a local inbound server policy in hub-vpc, but it places the private zone at the parent domain example.com. rather than scoping it to the dev.example.com. subdomain.
www.example.com: Under Cloud DNS longest-suffix matching and VPC name resolution order, authorized private zones are evaluated before public zones. When a VM in spoke-vpc queries www.example.com, the query matches the authorized private zone example.com.. Because www.example.com does not exist in that private zone, Cloud DNS immediately returns NXDOMAIN and never falls back to the public example.com. zone.hub-vpc resolution of example.com.: Creating a peering zone for example.com. in hub-vpc targeting spoke-vpc causes hub-vpc (and on-premises queries arriving at hub-vpc's inbound forwarder) to delegate all example.com. lookups to spoke-vpc's private zone, similarly returning NXDOMAIN for www.example.com.example.com.), the private zone completely masks the public zone's records for authorized VPCs.Creating a private zone for example.com. would be correct if you intentionally wanted split-horizon DNS for the entire example.com. domain and explicitly replicated all required public records (including www.example.com) inside the private example.com. zone.
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