Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization is deploying High Availability (HA) VPN over Cloud Interconnect to meet strict compliance mandates for data-in-transit encryption between its on-premises data center and a Google Cloud VPC network.
The underlying Dedicated Interconnect connection is fully operational, and the BGP session for the Interconnect Cloud Router is established. However, the HA VPN tunnels fail to establish (IKE negotiation fails), and the on-premises VPN device cannot reach or detect the Google Cloud HA VPN gateway endpoints.
Which action should the security engineer take to resolve this issue?
Custom advertised routes allow network administrators to specify exact IP address ranges (such as RFC 1918 ranges, Private Google Access endpoints, or Cloud DNS forwarders) that a Cloud Router advertises to on-premises BGP peers instead of, or in addition to, default VPC subnet CIDRs.
The HA VPN tunnels were already in an ESTABLISHED state, but on-premises workloads were unable to reach Google APIs or specific non-RFC 1918 VPC custom ranges due to missing route advertisements.
Media Access Control security (MACsec) (IEEE 802.1AE) is a Layer 2 cryptographic standard that encrypts all network traffic across physical point-to-point Ethernet links between on-premises edge routers and Google Cloud edge routers on supported Dedicated Interconnect circuits.
The requirement mandated hardware-based Layer 2 link encryption across the physical Interconnect circuits without adding IPsec encapsulation overhead or deploying HA VPN gateway infrastructure.
The Maximum Transmission Unit (MTU) specifies the maximum packet size in bytes that a network interface or VLAN attachment can transmit without fragmentation. Cloud Interconnect supports MTU sizes of 1440, 1460, 1500, or 8896 bytes (jumbo frames).
The scenario involved optimizing large data transfers on an unencrypted Dedicated Interconnect connection where both on-premises routers and VPC networks were configured end-to-end to support 8896 MTU payload sizes.
--ipsec-internal-addresses) so that the Interconnect Cloud Router advertises the HA VPN gateway IP ranges.In an HA VPN over Cloud Interconnect deployment, the architecture uses a two-tier routing and encapsulation design. The underlying Cloud Interconnect tier provides private transport, while the HA VPN tier encapsulates data inside encrypted IPsec tunnels. To make the Google Cloud HA VPN gateways reachable to the on-premises VPN devices across the private Interconnect transport, each VLAN attachment must be assigned regional internal IPv4 addresses using the --ipsec-internal-addresses flag.
advertisedRoutes field on the Interconnect Cloud Router confirms that the internal gateway prefixes are being shared with the peer.Without assigning the --ipsec-internal-addresses property to the VLAN attachments, the Interconnect Cloud Router cannot advertise the HA VPN gateway endpoints to the peer network. Configuring this setting addresses the root cause of the IKE negotiation failure by establishing underlying Layer 3 reachability between the VPN endpoints.
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