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.
You are connecting a custom-mode VPC network (prod-vpc) in Google Cloud to an on-premises data center using Classic VPN. Your environment has the following topology and constraints:
10.10.1.0/24, 10.20.1.0/24, and 10.30.1.0/24192.168.10.0/24 and 192.168.50.0/24 (other 192.168.0.0/16 ranges are used by unrelated branch sites)Which configuration should you deploy?
In a policy-based Classic VPN tunnel, you explicitly specify local and remote traffic selectors (also called encryption domains) that define which source and destination IP ranges are permitted through the tunnel. When using IKEv2, Cloud VPN supports specifying multiple CIDR blocks in both the local and remote traffic selectors, provided all ranges are negotiated inside a single Child Security Association (SA).
10.0.0.0/8 as the local traffic selector and 192.168.0.0/16 as the remote traffic selector, and update the tunnel's traffic selectors later if subnet boundaries change.When you create a policy-based Classic VPN tunnel through the Google Cloud console, Google Cloud configures the specified local and remote traffic selectors and automatically generates custom static routes in your VPC network whose destination prefixes match the exact CIDR blocks entered in the Remote network IP ranges field.
192.168.0.0/16 as the remote traffic selector in the Google Cloud console automatically creates a static route for the entire 192.168.0.0/16 range pointing to the VPN tunnel. This captures traffic destined for the unrelated branch locations that also use 192.168.0.0/16 subnets and misroutes it to this data center.gcloud CLI.10.0.0.0/8 and 192.168.0.0/16) on a Cisco ASA can conflict with other site-to-site VPN policies or internal routing.0.0.0.0/0 selectors) is specifically designed to separate tunnel negotiation from granular static routing.10.0.0.0/8 and 192.168.0.0/16 address spaces were dedicated solely to these two sites, you used the gcloud CLI to manually define specific /24 static routes separately from the broad selectors, and you never needed to edit the selectors post-creation.Because IKEv1 strictly limits each Child SA to a single local CIDR and a single remote CIDR, one traditional workaround for connecting multiple non-contiguous subnets is to split them across multiple individual policy-based tunnels, each handling a single 1-to-1 subnet pair.
N local subnets and M remote subnets requires N × M tunnels, quickly exhausting tunnel quotas and increasing management complexity.0.0.0.0/0 for both local and remote traffic selectors, create custom static routes in prod-vpc for 192.168.10.0/24 and 192.168.50.0/24 pointing to the VPN tunnel, and configure a Virtual Tunnel Interface (VTI) with static routes on the Cisco ASA.A route-based Classic VPN tunnel sets both the local and remote traffic selectors to 0.0.0.0/0, establishing a single IPsec Child SA that permits any IPv4 traffic permitted by routing tables. On Cisco ASA appliances running software version 9.7(x) and later, configuring a Virtual Tunnel Interface (VTI) enables route-based VPN operation that cleanly pairs with Cloud VPN's 0.0.0.0/0 selectors.
0.0.0.0/0 to 0.0.0.0/0 Child SA, completely bypassing the ASA's limitation of spawning multiple Child SAs for multi-CIDR policy-based encryption domains.prod-vpc specifically for 192.168.10.0/24 and 192.168.50.0/24 (with the VPN tunnel as the next hop) ensures only traffic for those data center subnets enters the tunnel, avoiding conflicts with unrelated branch ranges in 192.168.0.0/16.0.0.0.0/0, onboarding new VPC or data center subnets only requires adding or replacing static routes without deleting or recreating the VPN tunnel.0.0.0.0/0) from VPC routing policy (specific custom static routes).Route-based Classic VPN with custom static routes is the only static-routing architecture that works over a single Cisco ASA external IP address, respects Cloud VPN's single Child SA rule, prevents routing unrelated 192.168.0.0/16 prefixes, and supports future subnet additions without tunnel downtime.
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