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 topology with three custom-mode VPC networks: hub-vpc, spoke-a-vpc, and spoke-b-vpc.
hub-vpc connects to your on-premises data center via Dedicated Interconnect VLAN attachments in us-central1 using a Cloud Router with default advertisement mode and REGIONAL dynamic routing.spoke-a-vpc (workloads in us-east1) and spoke-b-vpc (workloads in us-central1) each have VPC Network Peering with hub-vpc, with export-custom-routes enabled on hub-vpc and import-custom-routes enabled on both spokes.corp.example.com targeting on-premises DNS servers and authorized hub-vpc, spoke-a-vpc, and spoke-b-vpc to use it.a.gcp.example.com (authorized only for spoke-a-vpc) and b.gcp.example.com (authorized only for spoke-b-vpc).Workloads report that VMs in both spokes cannot resolve corp.example.com or reach on-premises IPs, on-premises hosts cannot reach either spoke, and VMs in spoke-a-vpc cannot communicate with VMs in spoke-b-vpc or resolve b.gcp.example.com. You must fix all connectivity and DNS issues while keeping the VPC Network Peering design without deploying Network Connectivity Center or network virtual appliances.
Which set of changes should you implement?
GLOBAL dynamic routing on hub-vpc, configure its Cloud Router to use custom advertisement mode for all hub-vpc and spoke subnets plus 35.199.192.0/19, peer spoke-a-vpc and spoke-b-vpc directly, create separate corp.example.com forwarding zones inside spoke-a-vpc and spoke-b-vpc targeting the on-premises DNS servers, and authorize each private zone for both spokes.This option correctly resolves Layer 3 routing across hub-vpc, the spokes, and on-premises—including 35.199.192.0/19—and shares a.gcp.example.com and b.gcp.example.com across the spokes. However, instead of centralizing outbound DNS forwarding in hub-vpc via DNS peering, it configures independent corp.example.com forwarding zones directly inside spoke-a-vpc and spoke-b-vpc.
spoke-a-vpc and spoke-b-vpc do not have their own Cloud Interconnect or Cloud VPN connections to on-premises, their forwarding zones cannot use VPC Network Peering through hub-vpc to reach on-premises DNS targets.35.199.192.0/19 source IP ambiguity: Outbound forwarding from any VPC network uses the same 35.199.192.0/19 source IP range. Even if multiple VPCs had hybrid links to the same on-premises DNS servers, on-premises routers could not distinguish which VPC originated a query when routing 35.199.192.0/19 replies.hub-vpc if the forwarding query originated from a forwarding zone in spoke-a-vpc or spoke-b-vpc.Instead of creating forwarding zones in spoke-a-vpc and spoke-b-vpc, you kept the corp.example.com forwarding zone exclusively in hub-vpc and created Cloud DNS peering zones in both spokes targeting hub-vpc (or if each spoke connected to separate isolated on-premises DNS environments via its own dedicated hybrid links).
GLOBAL dynamic routing on hub-vpc, configure its Cloud Router to use custom advertisement mode for all hub-vpc and spoke subnets, restrict the corp.example.com forwarding zone to hub-vpc with Cloud DNS peering zones from each spoke to hub-vpc, and rely on the existing hub-vpc peering connections for inter-spoke traffic and private zone resolution.This option correctly sets GLOBAL dynamic routing on hub-vpc, uses custom Cloud Router advertisements for VPC subnets, and introduces Cloud DNS peering zones from the spokes to hub-vpc for corp.example.com. However, it omits the 35.199.192.0/19 route advertisement, skips direct peering between the spokes, and assumes VPC Network Peering shares private DNS zones.
35.199.192.0/19. Because hub-vpc's Cloud Router does not advertise 35.199.192.0/19 in its custom advertisements, on-premises routers lack a route back to Google Cloud for DNS responses, causing corp.example.com lookups to time out.spoke-a-vpc and spoke-b-vpc cannot communicate with each other via hub-vpc without direct peering between the two spokes.b.gcp.example.com for spoke-a-vpc or configuring Cloud DNS peering zones, spoke-a-vpc still cannot resolve b.gcp.example.com.35.199.192.0/19 is never advertised automatically.You added 35.199.192.0/19 to the Cloud Router custom advertisements, peered spoke-a-vpc directly with spoke-b-vpc, and configured Cloud DNS peering zones (or cross-VPC authorization) for a.gcp.example.com and b.gcp.example.com.
GLOBAL dynamic routing on spoke-a-vpc and spoke-b-vpc, configure hub-vpc's Cloud Router to use custom advertisement mode for all hub-vpc and spoke subnets plus 35.199.192.0/19, enable export-custom-routes and import-custom-routes on all VPC Network Peering connections, and keep the corp.example.com forwarding zone authorized for all three VPC networks.This approach attempts to fix cross-region routing on the importing spoke VPCs, make VPC peering transitive by enabling custom route exchange in both directions, and allow spokes to share a single Cloud DNS forwarding zone directly via zone authorization.
hub-vpc) determines which regions receive peering dynamic routes. Leaving hub-vpc set to REGIONAL prevents spoke-a-vpc workloads in us-east1 from receiving on-premises dynamic routes, regardless of the dynamic routing mode configured on spoke-a-vpc.spoke-a-vpc and on-premises, Cloud DNS cannot use transitive routing to reach a forwarding target. Authorizing spoke-a-vpc and spoke-b-vpc directly on a forwarding zone whose targets are behind hub-vpc's Interconnect still causes DNS queries from the spokes to fail.export-custom-routes and import-custom-routes on the spokes does not forward traffic from spoke-a-vpc through hub-vpc to spoke-b-vpc, because VPC Network Peering never propagates peering subnet routes across a second peering hop.a.gcp.example.com and b.gcp.example.com remain isolated to their respective VPCs.No such tweak makes direct forwarding-zone authorization work over VPC peering; hub-vpc must use GLOBAL dynamic routing, spokes must use Cloud DNS peering zones, and spokes must be directly peered to communicate.
GLOBAL dynamic routing on hub-vpc, configure its Cloud Router to use custom advertisement mode for all hub-vpc and spoke subnets plus 35.199.192.0/19, peer spoke-a-vpc and spoke-b-vpc directly, restrict the corp.example.com forwarding zone to hub-vpc with Cloud DNS peering zones from each spoke to hub-vpc, and configure Cloud DNS peering zones between the spokes for a.gcp.example.com and b.gcp.example.com.This solution combines a full-mesh VPC Network Peering topology for inter-spoke data plane traffic, global dynamic routing with custom Cloud Router route advertisements in the transit hub, and Cloud DNS peering zones for cross-VPC and hybrid name resolution.
us-east1 and us-central1): Because hub-vpc is the route-exporting VPC network, switching hub-vpc to GLOBAL dynamic routing ensures its Cloud Router in us-central1 exports learned on-premises routes as peering dynamic routes into every region of the peered spokes, including us-east1 in spoke-a-vpc. Switching the Cloud Router to custom advertisement mode ensures that spoke-a-vpc and spoke-b-vpc subnet ranges (which default advertisements omit across VPC peering) are advertised to on-premises.spoke-a-vpc and spoke-b-vpc cannot traverse hub-vpc. Adding a direct VPC Network Peering connection between spoke-a-vpc and spoke-b-vpc completes the mesh and enables full-bandwidth private communication.corp.example.com: Outbound DNS forwarding cannot traverse VPC Network Peering directly. Restricting the forwarding zone to hub-vpc, advertising 35.199.192.0/19 from hub-vpc to on-premises for return DNS traffic, and configuring Cloud DNS peering zones in both spokes targeting hub-vpc routes DNS queries through hub-vpc seamlessly—even from us-east1 once hub-vpc uses GLOBAL dynamic routing.spoke-a-vpc and spoke-b-vpc allows VMs in either spoke to resolve a.gcp.example.com and b.gcp.example.com.35.199.192.0/19 proxy range through hub-vpc.Within the constraint of retaining VPC Network Peering without Network Connectivity Center or virtual appliances, this is the only pattern that resolves non-transitive spoke routing, cross-region dynamic route export, and non-transitive Cloud DNS forwarding simultaneously.
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