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 is deploying an HA VPN connection between a Google Cloud VPC network and two redundant on-premises VPN gateway devices, each with one external IPv4 address, to achieve a 99.99% availability SLA. Your security team enforces the following tunnel configuration requirements:
AES-GCM-16-256 for Phase 1 and Phase 2, with AES-CBC-256 as a fallbackHMAC-SHA2-256-128Group-19 (ecp_256)How should you configure the HA VPN gateway, external VPN gateway resource, and IPsec tunnels?
SINGLE_IP_INTERNALLY_REDUNDANT for the primary on-premises device. Configure two IKEv2 tunnels on HA VPN interface 0 using matching pre-shared keys, AES-GCM-16-256 followed by AES-CBC-256, HMAC-SHA2-256-128, and Group-19, while keeping HA VPN interface 1 unconfigured as a standby interface.This approach applies the correct IKEv2 cryptographic suite and ordering (AES-GCM-16-256 before AES-CBC-256, HMAC-SHA2-256-128, and Group-19), but it registers only a single peer IP with SINGLE_IP_INTERNALLY_REDUNDANT, assigns tunnels solely to HA VPN interface 0, and leaves HA VPN interface 1 unconfigured.
interface 0 and interface 1). Leaving interface 1 unused eliminates gateway-level redundancy and forfeits the SLA.SINGLE_IP_INTERNALLY_REDUNDANT leaves the second physical on-premises VPN device unused, creating a single point of failure on-premises.interface 0 to the same single peer interface 0.The external VPN gateway used TWO_IPS_REDUNDANCY for both on-premises devices and configured one IKEv2 tunnel on HA VPN interface 0 and a second IKEv2 tunnel on HA VPN interface 1.
TWO_IPS_REDUNDANCY. Configure two IKEv2 tunnels on a Cloud Router—mapping HA VPN interface 0 to peer interface 0 and interface 1 to peer interface 1—with matching pre-shared keys, custom ciphers listing AES-GCM-16-256 before AES-CBC-256 for Phase 1 and Phase 2 encryption, HMAC-SHA2-256-128 for integrity, and Group-19 for DH and PFS.HA VPN automatically provisions a regional gateway with two independent external IP interfaces (interface 0 and interface 1) drawn from separate address pools for fault tolerance. To represent two distinct on-premises VPN devices in Google Cloud, an external VPN gateway resource is configured with the TWO_IPS_REDUNDANCY type (id: 0 and id: 1). Custom cryptographic suites are applied directly during IKEv2 tunnel creation for both Phase 1 (IKE SA) and Phase 2 (IPsec SA) negotiations.
interface 0 to peer interface 0 and HA VPN interface 1 to peer interface 1 ensures active IPsec tunnels on both Cloud VPN interfaces with dynamic BGP routing via Cloud Router.AES-GCM-16-256 before AES-CBC-256 satisfies the strict Cloud VPN requirement that Authenticated Encryption with Associated Data (AEAD) ciphers precede non-AEAD ciphers.HMAC-SHA2-256-128 covers integrity for the non-AEAD fallback (AES-CBC-256), while AES-GCM-16-256 handles both encryption and integrity natively.Group-19 (ecp_256) for Phase 1 Diffie-Hellman (DH) and Phase 2 Perfect Forward Secrecy (PFS), along with unique matching IKE pre-shared keys on each tunnel pair, ensures compliant and authenticated connections.AES-GCM-16-256) cryptography while preserving backward compatibility via AES-CBC-256.This is the only configuration that simultaneously fulfills the 99.99% SLA topology rules for two external peer devices and adheres to Cloud VPN's IKEv2 custom cipher ordering and immutability constraints.
TWO_IPS_REDUNDANCY. Configure two IKEv2 tunnels on a Cloud Router—mapping HA VPN interface 0 to peer interface 0 and interface 1 to peer interface 1—with matching pre-shared keys, custom ciphers listing AES-CBC-256 before AES-GCM-16-256 for Phase 1 and Phase 2 encryption, HMAC-SHA2-256-128 for integrity, and Group-19 for DH and PFS.This approach establishes the correct HA VPN physical topology (TWO_IPS_REDUNDANCY across interface 0 and interface 1) and selects IKEv2 with custom ciphers, Group-19 key exchange, and unique pre-shared keys. However, it places AES-CBC-256 (a non-AEAD cipher) ahead of AES-GCM-16-256 (an AEAD cipher) in the Phase 1 and Phase 2 encryption preference lists.
AES-CBC-256 first violates Cloud VPN tunnel validation rules.AES-CBC-256 first makes it the preferred encryption algorithm during IKE SA negotiation rather than AES-GCM-16-256.AES-GCM-16-256 combine confidentiality and integrity into a single operation, whereas AES-CBC-256 requires a separate integrity algorithm like HMAC-SHA2-256-128.The encryption cipher list were reversed to specify AES-GCM-16-256,AES-CBC-256, ensuring the AEAD cipher precedes the non-AEAD fallback and acts as the primary encryption algorithm.
TWO_IPS_REDUNDANCY. Configure two IKEv1 tunnels on a Cloud Router—mapping HA VPN interface 0 to peer interface 0 and interface 1 to peer interface 1—with matching pre-shared keys, and then update the tunnels after creation to apply AES-GCM-16-256, AES-CBC-256, HMAC-SHA2-256-128, and Group-19 for DH and PFS.This option initially deploys the redundant two-interface HA VPN topology using IKEv1 and attempts to modify the tunnels afterward to apply the custom AES-GCM-16-256, AES-CBC-256, HMAC-SHA2-256-128, and Group-19 cryptographic parameters.
AES-CBC-128, HMAC-SHA1-96, and Diffie-Hellman Group 2 / modp_1024) and cannot use AES-GCM-16-256, HMAC-SHA2-256-128, or Group-19.SHA-1 integrity and 1024-bit MODP groups, which fail modern enterprise security compliance.The tunnels were initially created using IKEv2 with all custom ciphers, integrity algorithms, and Group-19 parameters defined at creation time rather than attempting post-creation updates on IKEv1 tunnels.
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