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 VPC architecture connected via VPC Network Peering:
hub-vpc (10.10.0.0/16): Hosts highly available multi-NIC Network Virtual Appliances (NVAs) with IP forwarding enabled behind an internal passthrough Network Load Balancer at 10.10.1.100 (global access enabled), and a protected subnet 10.10.2.0/24.spoke-a (10.20.0.0/16): Hosts workloads in 10.20.1.0/24, including an authorized scanner VM at 10.20.1.50/32.You must intercept only TCP traffic from 10.20.1.0/24 to 10.10.2.0/24 through the NVAs, while allowing 10.20.1.50/32 to bypass the NVAs and use direct peering subnet routing.
Which configuration should you implement?
hub-vpc, create two policy-based routes with --ip-protocol=TCP and --destination-range=10.10.2.0/24 using priority 100 (10.20.1.50/32 with DEFAULT_ROUTING) and priority 200 (10.20.1.0/24 with 10.10.1.100), then enable custom route export and import on the VPC Network Peering connection.This approach creates properly prioritized policy-based routes inside hub-vpc (where the NVA load balancer and destination subnet reside) and attempts to distribute them to spoke-a using VPC Network Peering custom route exchange.
--export-custom-routes and --import-custom-routes on a VPC Network Peering connection only exchanges dynamic routes and eligible static routes. Policy-based routes are never propagated between peered VPC networks.hub-vpc has zero effect on packets originating from 10.20.1.0/24 in spoke-a.spoke-a traverse the peering connection into hub-vpc, they are delivered to 10.10.2.0/24 using hub-vpc's local subnet routing without triggering hub-vpc egress PBRs.--next-hop-ilb-ip can reside in a peered VPC network.default-internet-gateway next hop.The two policy-based routes were created directly inside spoke-a rather than hub-vpc, pointing their --next-hop-ilb-ip to 10.10.1.100 in the peered hub-vpc.
spoke-a, create two policy-based routes with --ip-protocol=TCP, --destination-range=10.10.2.0/24, and --priority=100: one matching --source-range=10.20.1.50/32 with --next-hop-other-routes=DEFAULT_ROUTING, and one matching --source-range=10.20.1.0/24 with --next-hop-ilb-ip=10.10.1.100.This option creates both policy-based routes (PBRs) in the correct VPC network (spoke-a) with valid match criteria (--ip-protocol=TCP, source/destination CIDRs) and uses the DEFAULT_ROUTING skip action, but it assigns the same numeric priority (100) to both rules.
/32 source range does not automatically take precedence over a /24 source range.10.20.1.50/32, Google Cloud selects a single route using an internal algorithm. That algorithm is not guaranteed to pick the more specific /32 rule.10.20.1.50/32) could match the 10.20.1.0/24 rule and be unexpectedly redirected to the NVA load balancer instead of bypassing inspection.The 10.20.1.50/32 bypass rule was given a strictly higher priority (for example, --priority=100) than the 10.20.1.0/24 interception rule (for example, --priority=200).
spoke-a, create two policy-based routes with --ip-protocol=TCP and --destination-range=10.10.2.0/24: one at --priority=100 matching --source-range=10.20.1.50/32 with --next-hop-other-routes=DEFAULT_ROUTING, and one at --priority=200 matching --source-range=10.20.1.0/24 with --next-hop-ilb-ip=10.10.1.100.This configuration implements ordered policy-based routes (PBRs) in spoke-a using multi-tuple classification (--source-range, --destination-range, and --ip-protocol) with unique priorities and the DEFAULT_ROUTING skip mechanism to selectively steer traffic to an internal passthrough Network Load Balancer in a peered VPC.
spoke-a to intercept traffic destined for 10.10.2.0/24 even though a peering subnet route exists.--next-hop-ilb-ip can point directly to an internal passthrough Network Load Balancer in a VPC network connected via VPC Network Peering (hub-vpc).100 before 200), TCP packets from 10.20.1.50/32 match the priority 100 rule first. Setting --next-hop-other-routes=DEFAULT_ROUTING causes Google Cloud to ignore all lower-priority PBRs and fall through to the subnet routes step, where the peering subnet route delivers traffic directly to 10.10.2.0/24.--ip-protocol=TCP restricts interception to TCP flows; non-TCP traffic (such as UDP or ICMP) matches neither PBR and automatically follows standard VPC peering subnet routing.hub-vpc forward inspected packets to 10.10.2.0/24 via local subnet routing without re-triggering the spoke-a PBR.Assigning unique priorities guarantees deterministic evaluation without relying on longest-prefix matching, placing the bypass exception cleanly ahead of the broader subnet interception rule in the exact VPC where the traffic originates.
spoke-a, create a custom static route for destination 10.10.2.0/24 at priority 50 with next hop 10.10.1.100 and network tags applied to all VMs except the scanner VM, allowing 10.20.1.50/32 to fall back to the imported peering subnet route.This option attempts to use a standard custom static route with network tags in spoke-a to override the imported peering subnet route for 10.10.2.0/24 and steer traffic toward the NVA internal passthrough Network Load Balancer.
10.10.2.0/24). The route creation will be rejected by the control plane.TCP only) or source IP ranges, which would cause UDP and ICMP traffic from tagged VMs to be intercepted as well.ALL, TCP, or UDP).You needed to route traffic toward an external or on-premises IP range (not a local or peered VPC subnet route) for all IP protocols without requiring source IP or protocol-level differentiation.
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