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 operates a Google Cloud VPC network (prod-vpc) containing Compute Engine VMs tagged secure-egress as well as untagged VMs. You inspect the active routes in prod-vpc:
| Route Name | Destination Range | Next Hop | Priority | Network Tag |
|---|---|---|---|---|
default-route | 0.0.0.0/0 | default-internet-gateway | 1000 | (none) |
nva-egress-route | 0.0.0.0/0 | Internal passthrough NLB (ilb-nva, global access enabled) | 1500 | secure-egress |
partner-primary | 198.51.100.0/24 | nva-vm-1 (next-hop-instance) | 100 | secure-egress |
partner-backup | 198.51.100.0/25 | nva-vm-2 (next-hop-instance) | 500 | secure-egress |
You observe two routing problems for VMs with the secure-egress tag:
0.0.0.0/0) bypasses ilb-nva and exits directly through default-internet-gateway.198.51.100.10 is forwarded to nva-vm-2 instead of nva-vm-1.You need to implement deterministic traffic steering so that VMs tagged secure-egress send all internet traffic through ilb-nva (while untagged VMs continue using default-internet-gateway), and send all traffic for 198.51.100.0/24 to nva-vm-1 while failing over to nva-vm-2 only if nva-vm-1 is stopped or deleted.
What should you do?
partner-backup and recreate it with destination 198.51.100.0/25, priority 65535, and network tag secure-egress; delete default-route and recreate nva-egress-route without a network tag at priority 1000.This option retains the /25 prefix on partner-backup while lowering its priority to 65535, deletes the VPC's system-generated default-route, and removes the secure-egress network tag from nva-egress-route.
partner-backup at 198.51.100.0/25 fails to steer traffic for 198.51.100.10 to nva-vm-1. Regardless of whether partner-backup has priority 500 or 65535, Google Cloud evaluates most specific destination before route priority, causing /25 to eliminate the /24 partner-primary route from consideration.default-route removes the default-internet-gateway path for the entire VPC network, and recreating nva-egress-route without a network tag forces all VPC resources—including untagged VMs, Cloud VPN tunnels, and proxies—to route outbound internet traffic through ilb-nva. This violates the requirement that untagged VMs continue using default-internet-gateway.0.0.0.0/0 route to default-internet-gateway disrupts direct external IPv4 connectivity and public Cloud NAT gateways, which depend on a local static route pointing to the default internet gateway.0 on /24 vs. 65535 on /25) can make a broader prefix supersede a more specific prefix.This approach would only work if the organization intended to force all VPC workloads through the NVA without exception and wanted nva-vm-2 to permanently handle the 198.51.100.0/25 subnet exclusively.
nva-egress-route and recreate it with destination 0.0.0.0/0, priority 500, and network tag secure-egress; delete partner-backup and recreate it with destination 198.51.100.0/24, priority 500, and network tag secure-egress.This approach uses custom static route replacement, destination prefix alignment, numeric route priority ordering, and network tag scoping to achieve deterministic traffic steering in a Google Cloud VPC network. In Google Cloud, custom static route priorities are immutable after creation, and route evaluation strictly checks most specific destination before comparing route priority.
nva-egress-route with priority 500 gives it a higher priority than default-route (priority 1000), because lower numerical values indicate higher priority (0 is highest and 65,535 is lowest). When a secure-egress VM sends traffic to the internet, both 0.0.0.0/0 routes match the destination specificity step, and nva-egress-route wins at the priority evaluation step.secure-egress network tag on nva-egress-route ensures it applies exclusively to VM instances carrying that tag. Untagged VMs do not evaluate nva-egress-route and continue routing through default-route.partner-backup from 198.51.100.0/25 to 198.51.100.0/24 places both partner-primary and partner-backup on the exact same destination prefix. Because both share 198.51.100.0/24, priority evaluation (100 vs. 500) determines the active path instead of longest-prefix match.partner-primary (priority 100), and disregards partner-backup (priority 500). If nva-vm-1 is stopped or deleted, Google Cloud disregards partner-primary as an unusable next hop and automatically steers traffic to partner-backup.Unlike in-place updates (which are unsupported for static route priorities) or relying on priority changes alone while leaving a /25 prefix intact, recreating both routes with aligned prefixes and properly ordered priorities directly aligns with the Google Cloud VPC routing order and guarantees deterministic forwarding.
nva-egress-route and recreate it with destination 0.0.0.0/0, priority 2000, and network tag secure-egress; delete partner-backup and recreate it with destination 198.51.100.0/24, priority 100, and network tag secure-egress.This option replaces both routes using valid delete-and-recreate operations and aligns partner-backup to 198.51.100.0/24, but assigns priority 2000 to nva-egress-route and priority 100 to partner-backup.
2000 makes nva-egress-route lower priority than default-route (priority 1000). During route selection, Google Cloud discards nva-egress-route, so tagged VMs continue bypassing ilb-nva and exiting directly through default-internet-gateway.partner-backup to destination 198.51.100.0/24 and priority 100 gives it the exact same destination, priority, and preference category (next-hop-instance) as partner-primary. When multiple usable routes remain after priority filtering and belong to the same preference category, Google Cloud performs equal-cost multipath (ECMP) routing, splitting packets across both nva-vm-1 and nva-vm-2 rather than deterministically using nva-vm-1 as primary.0 (highest) to 65,535 (lowest).This approach would satisfy the requirements only if nva-egress-route were recreated with a priority lower than 1000 (such as 500) and partner-backup were recreated with a higher numeric priority than 100 (such as 500), while also ensuring active-active ECMP was not desired.
nva-egress-route in place to set its priority to 500, and update partner-backup in place to set its priority to 65535.This option attempts to modify the priority attribute of existing VPC custom static routes in place and relies on lowering the numeric priority of partner-backup to 65535 while keeping its 198.51.100.0/25 destination range unchanged.
/25 vs. /24 routing conflict: Even if partner-backup were recreated with priority 65535 (the lowest possible static route priority), traffic destined for 198.51.100.10 would still be forwarded to nva-vm-2. In Google Cloud's routing order, the most specific destination step runs before the disregard low priority routes step. Because 198.51.100.0/25 is more specific than 198.51.100.0/24, Google Cloud discards partner-primary before priorities are ever compared.65535 only affects tie-breaking among routes with the exact same destination prefix (or against dynamic routes, which use Andromeda priority 65536).This option is invalid as written because static route priorities cannot be changed in place. A priority adjustment only establishes precedence if the routes are deleted and recreated and both partner-primary and partner-backup share the identical 198.51.100.0/24 destination range.
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