You want to deploy a VPN Gateway to connect your on-premises network to GCP. You are using a non BGP-capable on-premises VPN device. You want to minimize downtime and operational overhead when your…

Question

Options

• ACreate a Cloud VPN instance.
• BCreate a Cloud VPN instance.
• CCreate a Cloud VPN instance.
• DCreate a Cloud VPN instance.

• A
  7% (4)
• B
  78% (43)
• C
  11% (6)
• D
  4% (2)

Explanation

Since the on-premises device is non-BGP-capable, HA VPN (which requires BGP/Cloud Router) is not an option. Classic Cloud VPN with policy-based or route-based static routing is required. Among the Classic VPN options, using route-based VPN with static routes (rather than policy-based VPN) minimizes operational overhead as the network grows, because adding new subnets only requires updating routes rather than redefining traffic selectors on both ends. The device's IKEv2 support is compatible with Classic Cloud VPN. Option B most likely describes this recommended configuration: Classic VPN with route-based routing and static routes, following Google's best practices for non-BGP peers.

No community discussion yet for this question.