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 configuring a Classic Cloud VPN gateway in a custom-mode VPC (10.10.0.0/16) to establish a route-based tunnel to an on-premises subnet (192.168.0.0/16) whose peer gateway is behind a one-to-one NAT device. Your deployment must meet the following requirements:
Which configuration should you implement?
0.0.0.0/0 traffic selectors, a matching pre-shared key, and only AES-GCM-16-256 and Group-14 for Phase 1 and Phase 2 without separate integrity ciphers. Create external forwarding rules for ESP, UDP 500, and UDP 4500 (with UDP 500 and 4500 forwarded by the NAT device), add a static route for 192.168.0.0/16, and create VPC ingress firewall rules allowing payload traffic from 192.168.0.0/16.This solution implements a route-based Classic Cloud VPN tunnel using IKEv2, custom Authenticated Encryption with Associated Data (AEAD) ciphers, explicit external forwarding rules, static VPC routing, and VPC ingress firewall rules. In Google Cloud, custom cipher suites are exclusively supported on IKEv2 tunnels and must be defined at tunnel creation time.
AES-GCM-16-256 and Group-14 satisfies the cryptographic mandate. Because AES-GCM-16-256 is an AEAD cipher, it handles both encryption and integrity simultaneously, so separate integrity algorithms must be omitted. Configuring only this single cipher for each role ensures the same algorithm is always negotiated during key rotation regardless of whether Cloud VPN or the peer acts as the initiator.sharedSecret) on both Cloud VPN and the peer gateway completes mutual IKE_AUTH verification.500 and 4500 on the peer's one-to-one NAT device allows NAT-T encapsulation to traverse the NAT boundary.0.0.0.0/0 configures route-based mode, while a static route for 192.168.0.0/16 directs outbound packets into the tunnel. After decapsulation, VPC firewall rules evaluate the inner packet headers, so permitting ingress from 192.168.0.0/16 allows on-premises workloads to reach 10.10.0.0/16.1406 bytes, or 1398 bytes with NAT-T) compared to non-AEAD suites.0.0.0.0/0 traffic selectors decouples routing from IKE SA negotiation, allowing subnet additions via static routes without recreating the tunnel.Every other approach either attempts unsupported cipher combinations (such as custom AEAD ciphers under IKEv1 or pairing separate integrity hashes with AEAD), introduces non-deterministic cipher lists, omits required NAT-T forwarding rules, or misconfigures traffic selectors and firewall source ranges.
10.10.0.0/16 local and 192.168.0.0/16 remote traffic selectors, a matching pre-shared key, and AES-GCM-16-256 and Group-14 for Phase 1 and Phase 2. Create external forwarding rules for ESP and UDP 500, rely on the traffic selectors to route traffic without creating a static route, and create VPC ingress firewall rules allowing payload traffic from 192.168.0.0/16.This option correctly uses IKEv2 with AES-GCM-16-256 and Group-14 without separate integrity ciphers, and properly configures VPC ingress firewall rules for 192.168.0.0/16. However, it implements policy-based traffic selectors, omits static routing, and omits UDP 4500 for NAT-Traversal.
10.10.0.0/16 and 192.168.0.0/16 creates a policy-based tunnel rather than the required route-based tunnel (0.0.0.0/0 for both local and remote selectors).192.168.0.0/16 to the VPN tunnel next hop, VPC instances have no route to reach on-premises subnets.500 to UDP 4500 encapsulation for NAT-Traversal (NAT-T). Omitting the UDP 4500 external forwarding rule on Google Cloud and failing to forward UDP 500/4500 on the NAT device prevents tunnel establishment and data transfer.1460-byte IKE MTU.ESP, UDP 500, UDP 4500) leaves the tunnel in a STOPPED or NO INCOMING PACKETS state.UDP 4500 forwarding were included, and a static route for 192.168.0.0/16 pointing to the VPN tunnel were explicitly created.0.0.0.0/0 traffic selectors, a matching pre-shared key, and AES-GCM-16-256, HMAC-SHA2-256-128, and Group-14 for Phase 1 and Phase 2. Create VPC ingress firewall rules allowing ESP, UDP 500, and UDP 4500 from the peer's public IP alongside payload traffic from 192.168.0.0/16, and add a static route for 192.168.0.0/16.This approach attempts to deploy a route-based Classic VPN tunnel using IKEv1 while supplying custom IKEv2 AEAD and HMAC cipher parameters, and attempts to handle IPsec gateway traffic using VPC ingress firewall rules instead of external forwarding rules.
AES-GCM-16-256; they are strictly locked to AES-CBC-128, HMAC-SHA1-96, and modp_1024 (Group 2) for both Phase 1 and Phase 2.AES-GCM-16-256) with a separate integrity algorithm (HMAC-SHA2-256-128) is invalid because AEAD algorithms perform integrity verification internally.500 and 4500 on the one-to-one NAT device—IKE packets never reach the VPN gateway.no-proposal-chosen error.0.0.0.0/0 satisfies route-based mode.AES-CBC-128, HMAC-SHA1-96, and Group 2, custom AES-GCM-16-256 ciphers were not required, and external forwarding rules plus NAT port forwarding were configured in place of VPC firewall rules for ESP/UDP.0.0.0.0/0 traffic selectors, a matching pre-shared key, and prioritized cipher lists starting with AES-GCM-16-256, HMAC-SHA2-256-128, and Group-14 for Phase 1 and Phase 2. Create external forwarding rules for ESP, UDP 500, and UDP 4500, add a static route for 192.168.0.0/16, and create VPC ingress firewall rules allowing payload traffic from the peer gateway's external NAT IP address.This option correctly selects IKEv2, route-based 0.0.0.0/0 selectors, external forwarding rules, and a static route, but it misconfigures cipher proposal lists, AEAD integrity settings, NAT port forwarding, and VPC firewall source ranges.
HMAC-SHA2-256-128 alongside AES-GCM-16-256 is rejected by Cloud VPN when only AEAD encryption is used, because AEAD handles both confidentiality and integrity.192.168.0.0/16.1406 bytes down to 1374 bytes), potentially causing silent packet drops.AES-GCM-16-256 and Group-14 (with no separate integrity flag) were configured as single-item proposals, UDP 500 and 4500 were forwarded by the NAT device, and the VPC firewall rule permitted 192.168.0.0/16 instead of the external NAT IP.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