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 connect two Google Cloud VPCs (vpc-core and vpc-app) using HA VPN gateways (ha-gw-core and ha-gw-app) with two tunnels (tunnel-0 and tunnel-1) to maintain a 99.99% availability SLA. After recreating tunnel-1 with custom compliance ciphers, Cloud Monitoring shows tunnel_established is 0 for tunnel-1, and you observe these logs:
vpn_gateway): no-proposal-chosen during negotiation on tunnel-1gce_router): CONFIG_DISABLED for the BGP session mapped to tunnel-1Which diagnosis and corrective action using gcloud restores full 99.99% SLA redundancy?
no-proposal-chosen error indicates tunnel-1 is missing a matching Cloud Router MED priority for active/active failover. Configure an additional tunnel on interface 0 of ha-gw-core and verify CONNECTION_REDUNDANCY_MET with gcloud compute vpn-gateways get-status.This option misinterprets no-proposal-chosen as a BGP Multi-Exit Discriminator (MED) routing mismatch and attempts to satisfy HA VPN redundancy by adding another tunnel onto interface 0 of ha-gw-core while checking gcloud compute vpn-gateways get-status.
no-proposal-chosen is an IKE/IPsec cipher negotiation error that prevents Phase 1 or Phase 2 SAs from forming. Cloud Router advertised route priority (MED) only affects BGP path preference after the tunnel is ESTABLISHED and BGP is UP.interface 0 and interface 1) on both sides. Adding a second tunnel to interface 0 leaves interface 1 non-functional and does not provide fault-domain redundancy.0 and 1) backed by external IP addresses from separate pools and fault domains.get-status redundancy check: Running gcloud compute vpn-gateways get-status evaluates tunnel configuration coverage (CONNECTION_REDUNDANCY_MET vs. INCOMPLETE_TUNNELS_COVERAGE), not whether IKE cipher negotiation succeeded.The tunnel and BGP sessions were already ESTABLISHED, but traffic was routing asymmetrically or failing to load-balance across both tunnels due to mismatched Cloud Router advertised route priorities (MED).
CONFIG_DISABLED indicates Cloud Router permanently shut down the BGP session after repeated handshake timeouts. Run gcloud compute vpn-tunnels update to align the IKEv2 ciphers on tunnel-1, then disable and re-enable the BGP peer on Cloud Router to clear the error state.This option assumes that Cloud VPN tunnel cipher options can be modified in place using an update command and that Cloud Router requires a manual administrative reset (disable and re-enable) of the BGP peer to recover from a CONFIG_DISABLED log event.
CONFIG_DISABLED caused by an unestablished VPN tunnel SA is not a permanent administrative shutdown. Cloud Router holds the BGP session down only while the underlying tunnel lacks an active IKE and child SA; manually toggling the BGP peer cannot bring BGP up while tunnel-1 remains down.CONFIG_DISABLED triggered by a down VPN tunnel, BGP automatically attempts to re-establish once the tunnel transitions to ESTABLISHED.gcloud to delete and recreate a tunnel, BGP sessions on Cloud Router remain configured unless explicitly removed with gcloud compute routers remove-bgp-peer.The Cloud Router logs instead showed BGP: Sent NOTIFICATION 6/1 (CEASE/MAX_PREFIXES_REACHED) because the peer advertised more than 5,000 prefixes. In that scenario, Cloud Router genuinely shuts down the BGP session and does not attempt to re-establish it until you reduce the advertised prefixes and manually disable and re-enable the BGP peer.
tunnel-1 using IKEv1 with custom cipher lists so Cloud VPN can auto-negotiate the strongest mutually supported cipher.This option attributes the no-proposal-chosen error to IKEv2 requiring an exact, ordered cipher match and recommends switching tunnel-1 to IKEv1 with custom cipher lists to enable flexible cipher auto-negotiation.
There is no valid Cloud VPN scenario where switching to IKEv1 enables custom cipher selection; however, matching an exact default cipher set would be relevant if integrating with a legacy third-party peer device that only supports IKEv1.
CONFIG_DISABLED occurs because tunnel-1 has not established an IKE/child SA due to mismatched ciphers. Delete and recreate tunnel-1 with gcloud so both tunnel endpoints share at least one common IKEv2 cipher, noting that gcloud tunnel deletion leaves the existing Cloud Router BGP session intact.When connecting two Google Cloud VPCs with HA VPN, Cloud Router monitors the underlying IKE and IPsec child security association (SA) state of each linked tunnel. A CONFIG_DISABLED event in Cloud Router logs (gce_router) indicates that Cloud Router intentionally stopped the BGP session to signal an error state to its peer because the associated VPN tunnel has not established its Phase 1 and Phase 2 SAs. Simultaneously, the no-proposal-chosen entry in Cloud VPN logs (vpn_gateway) pinpoints the root cause: the two HA VPN endpoints could not agree on a common IKEv2 cipher suite during negotiation, keeping tunnel_established at 0.
tunnel-1 with at least one mutually supported IKEv2 cipher (encryption, integrity, PRF, and Diffie-Hellman/PFS algorithms) on both sides.tunnel-1 reaches the ESTABLISHED state, Cloud Router automatically clears the CONFIG_DISABLED condition and re-establishes the BGP session without manual BGP reset.gcloud behavior: Deleting a tunnel via gcloud compute vpn-tunnels delete does not automatically remove the associated BGP peer on Cloud Router (unlike deleting a tunnel in the Google Cloud console), allowing you to preserve or re-verify the BGP configuration.tunnel-1 back up restores active tunnels across both interface 0 and interface 1 on ha-gw-core and ha-gw-app.36000 seconds) and Phase 2 (10800 seconds) lifetimes should also align to avoid drops during key rotation.CONNECTION_REDUNDANCY_MET with gcloud compute vpn-gateways get-status after recreating the tunnel.Attempting to update ciphers in place fails because Cloud VPN tunnel cipher parameters are immutable, and manually cycling BGP cannot succeed until the underlying IPsec tunnel is established. Recreating the tunnel with matching IKEv2 proposals directly resolves both the vpn_gateway and gce_router faults.
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