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.
An ACTIVE VPC Network Peering connects vpc-spoke and vpc-hub (both using REGIONAL dynamic routing), with vpc-hub exporting custom routes and vpc-spoke importing them:
vpc-spoke: Subnets 10.10.1.0/24 (us-central1) and 10.10.2.0/24 (europe-west1), plus a local static route for 192.168.0.0/16 (priority 1000) to a legacy VPN.vpc-hub: Subnet 10.20.0.0/24 (us-central1), a Cloud Router in us-central1 (default advertisement mode) learning 192.168.0.0/16 via Cloud Interconnect, and an ingress firewall rule with --source-tags=spoke-client.Traffic from vpc-spoke to vpc-hub is blocked, and bidirectional europe-west1–on-premises traffic bypasses Cloud Interconnect.
Which actions resolve all connectivity issues?
192.168.0.0/16 static route in vpc-spoke, set vpc-hub to GLOBAL dynamic routing mode, configure custom advertisement mode on vpc-hub's Cloud Router for vpc-spoke subnets, and replace --source-tags with vpc-spoke subnet CIDRs in vpc-hub's firewall rule.This solution aligns VPC Network Peering custom route exchange, global dynamic routing, Cloud Router custom advertisements, and CIDR-based firewall rules to establish deterministic bidirectional routing across regions and hybrid links.
192.168.0.0/16 route conflict: Deleting the local static route in vpc-spoke removes the local override, because a VPC network always prefers its own local route over an imported peering route with an identical or more specific destination.europe-west1: Switching the exporting VPC (vpc-hub) to GLOBAL dynamic routing mode instructs Google Cloud to program the 192.168.0.0/16 peering dynamic route in every region of vpc-spoke, regardless of vpc-spoke's own dynamic routing mode.vpc-spoke subnets to on-premises: Cloud Routers in default advertisement mode never advertise received peering subnet routes. Switching vpc-hub's Cloud Router to custom advertisement mode and explicitly adding 10.10.1.0/24 and 10.10.2.0/24 (or an aggregate range) provides the return path from on-premises.vpc-spoke to vpc-hub traffic: Because network tags are not evaluated across peered VPC networks, replacing --source-tags=spoke-client with vpc-spoke's subnet IP ranges allows the ingress firewall rule in vpc-hub to match peer VM traffic.Each change directly addresses a specific VPC Network Peering constraint—local route precedence, exporting-side dynamic routing scope, BGP advertisement boundaries, and per-VPC firewall tag isolation—without introducing unnecessary static routes or proxy appliances.
192.168.0.0/16 static route in vpc-spoke, set vpc-spoke to GLOBAL dynamic routing mode, configure custom advertisement mode on vpc-hub's Cloud Router for vpc-spoke subnets, and replace --source-tags with vpc-spoke VM service accounts in vpc-hub's firewall rule.This option correctly removes the conflicting static route in vpc-spoke and configures custom advertisement mode on vpc-hub's Cloud Router, but switches vpc-spoke to GLOBAL dynamic routing mode and attempts to filter peer traffic in vpc-hub using VM service accounts.
vpc-spoke to vpc-hub remains blocked.europe-west1: With VPC Network Peering, the dynamic routing mode of the importing VPC (vpc-spoke) is irrelevant. Because the exporting VPC (vpc-hub) remains in REGIONAL dynamic routing mode, vpc-hub only exports the 192.168.0.0/16 dynamic route to us-central1 in vpc-spoke, leaving europe-west1 without a route via Cloud Interconnect.vpc-spoke subnets to on-premises.The GLOBAL dynamic routing mode were applied to vpc-hub (rather than vpc-spoke) and the vpc-hub ingress firewall rule used vpc-spoke's subnet CIDR ranges (10.10.1.0/24 and 10.10.2.0/24) instead of service accounts.
Engineers migrating from Shared VPC—where tags and service accounts work across service projects sharing one VPC—often mistakenly assume those identities also traverse VPC Network Peering boundaries.
192.168.0.0/16 static route priority to 65535 in vpc-spoke, set vpc-spoke to GLOBAL dynamic routing mode, enable --export-custom-routes on vpc-spoke, and replace --source-tags with vpc-spoke subnet CIDRs in vpc-hub's firewall rule.This approach attempts to deprioritize the conflicting local static route in vpc-spoke by setting its priority to 65535, switches vpc-spoke to global dynamic routing mode, exports custom routes from vpc-spoke, and updates the vpc-hub firewall rule to match subnet CIDR ranges.
65536, which is deliberately one value lower in preference than 65535 (the lowest possible static route priority). Furthermore, when an importing VPC has a local route with an identical or more specific destination than an imported peering route, the local route always takes precedence.vpc-hub) controls which regions receive peering dynamic routes. Changing vpc-spoke (the importing network) to GLOBAL has no effect on europe-west1.--export-custom-routes on vpc-spoke only shares vpc-spoke's custom routes with vpc-hub. Because vpc-hub's Cloud Router remains in default advertisement mode, it still does not advertise received peering subnet routes (10.10.1.0/24 and 10.10.2.0/24) to the on-premises network.0 (highest) to 65535 (lowest), while dynamic routes start at 65536.Instead of adjusting priority to 65535, the 192.168.0.0/16 static route in vpc-spoke were deleted, vpc-hub were switched to GLOBAL dynamic routing mode, and vpc-hub's Cloud Router were configured with custom advertisement mode to advertise vpc-spoke's subnet ranges.
192.168.0.0/16 (priority 500, --tags=interconnect) in vpc-hub, set vpc-hub to GLOBAL dynamic routing mode, keep default advertisement mode on vpc-hub's Cloud Router, and replace --source-tags with vpc-spoke subnet CIDRs in vpc-hub's firewall rule.This approach leaves the local static route in vpc-spoke intact, adds a higher-priority tagged static route in vpc-hub, switches vpc-hub to GLOBAL dynamic routing mode, retains default advertisement mode on vpc-hub's Cloud Router, and fixes the firewall rule using vpc-spoke CIDR ranges.
500 route in vpc-hub never reaches vpc-spoke.vpc-hub had no network tags, vpc-spoke's local static route for 192.168.0.0/16 (priority 1000) still takes precedence over any imported peering route with an identical destination, regardless of the peer route's numerical priority.vpc-spoke: Leaving vpc-hub's Cloud Router in default advertisement mode prevents it from advertising received peering subnet routes (10.10.1.0/24 and 10.10.2.0/24) over BGP to the on-premises router.The local 192.168.0.0/16 static route in vpc-spoke were deleted instead of adding a tagged static route in vpc-hub, and vpc-hub's Cloud Router were switched to custom advertisement mode to advertise vpc-spoke's subnets.
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