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 Classic VPN gateway (route-based, IKEv2) connecting a VPC network to a BGP-capable on-premises firewall. Peak tunnel traffic is 1.2 Gbps and 100,000 packets per second (pps). After expanding your VPC subnets, you observe the following in the Cloud VPN Monitoring tab and Cloud Logging (resource.type="vpn_gateway"):
Received SA_DELETELocal traffic selectors narrowed during negotiation for the new subnetsManagement also requires upgrading the connection to a 99.99% availability SLA with zero capacity loss during failover.
Which diagnosis and migration plan should you execute?
36000s / 10800s), verify connectivity, and then delete the Classic VPN tunnels, custom static routes, and gateway.This solution accurately diagnoses the Phase 2 rekeying failure and traffic selector narrowing from Cloud Logging while executing the supported migration pathway from Classic VPN to HA VPN to satisfy the 99.99% availability SLA and failover throughput requirements.
Received SA_DELETE): A Received SA_DELETE log immediately before brief tunnel drops confirms the peer gateway is tearing down the expired ESP Child SA instead of proactively rekeying. Aligning Phase 1 (36000 seconds) and Phase 2 (10800 seconds) lifetimes (or matching the vendor template values exactly) eliminates key-rotation interruptions.Local traffic selectors narrowed): Classic VPN traffic selectors are immutable after creation and require deleting and recreating the tunnel to update. Migrating to HA VPN with BGP dynamic routing via Cloud Router replaces static selectors with dynamic prefix advertisement.interface 0 and interface 1) connected to the peer gateway achieves a 99.99% SLA.Unlike Classic VPN workarounds that remain capped at a 99.9% SLA or invalid in-place conversion attempts, creating a parallel HA VPN deployment respects Cloud VPN's resource immutability, satisfies the 99.99% SLA, and provides clean cutover without capacity degradation.
This approach attempts to resolve the outages and SLA requirement by scaling Classic VPN horizontally with equal-cost multipath (ECMP) routing and enabling BGP dynamic routing on Classic VPN tunnels, while attributing the log messages to a Diffie-Hellman (DH) mismatch and throughput saturation.
Peer proposal: DOES NOT HAVE DIFFIE_HELLMAN_GROUP, not Received SA_DELETE. Additionally, 1.2 Gbps and 100,000 pps remain within a single tunnel's maximum 3 Gbps and 250,000 pps limits.Local traffic selectors narrowed indicates a mismatch between the VPC ranges configured on the Cloud VPN local selector and the remote selector on the peer gateway.Scaling with a second Classic VPN gateway would be appropriate only if the organization could accept a 99.9% SLA, used static routing exclusively, and needed aggregate bandwidth exceeding 3 Gbps across two gateways.
This option correctly identifies the Phase 2 rekeying and traffic selector issues from Cloud Logging, but proposes an unsupported HA VPN-to-Classic VPN connection topology, an insufficient single-tunnel HA VPN configuration, and an ineffective active-active scaling threshold.
CONNECTION_REDUNDANCY_NOT_MET) and does not qualify for the 99.99% availability SLA.This approach would be valid only if the new HA VPN gateway connected directly to the on-premises peer (represented as an ExternalVpnGateway) using two tunnels across both HA VPN interfaces (interface 0 and interface 1), rather than attempting to peer with the Classic VPN gateway.
Received SA_DELETE log indicates a Phase 1 no-proposal-chosen cipher mismatch. Migrate the existing Classic VPN tunnels and external IP address in-place to a new HA VPN gateway, edit the traffic selectors to 0.0.0.0/0, and attach a Cloud Router for BGP to achieve a 99.99% SLA.This option misinterprets a Phase 2 lifecycle event (Received SA_DELETE) as a Phase 1 cipher negotiation failure (no-proposal-chosen) and assumes that Classic VPN gateways, tunnels, and external IP addresses can be converted in-place into HA VPN resources.
Received SA_DELETE entry followed by brief drops and re-establishment means the peer gateway failed to rekey its Phase 2 Child Security Association (SA) before expiration, deleting the active SA before negotiating a replacement. By contrast, a cipher mismatch produces a no-proposal-chosen error during IKE negotiation.vpn-gateway API resource with two mandatory interfaces for high availability, whereas Classic VPN uses the single-interface target-vpn-gateway resource.no-proposal-chosen, while Phase 2 Child SA terminations appear as received DELETE for ESP CHILD_SA or Received SA_DELETE.This diagnosis would apply only if Cloud Logging explicitly showed no-proposal-chosen during IKE_SA_INIT or IKE_AUTH, and if Google Cloud supported converting target-vpn-gateway resources into dual-interface vpn-gateway resources without provisioning new external IP addresses.
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