An enterprise organization maintains a Google Cloud VPC network with subnets provisioned in both `us-central1` and `europe-west1`. The organization establishes a Dedicated Interconnect connection attached to a Cloud Router residing in `us-central1` to link their on-premises data center. Virtual machine instances deployed in `europe-west1` must dynamically receive on-premises routes advertised via BGP and route egress traffic to the on-premises network through the `us-central1` Cloud Router without establishing additional physical interconnects or manually managing static routes. Which VPC network routing configuration should you implement to satisfy this requirement?
- Set the dynamic routing mode of the VPC network from Regional to Global.Cevap
- BCreate a VPC Network Peering connection between the us-central1 and europe-west1 subnets and enable custom route import and export.
- CProvision an HA VPN gateway in europe-west1 and establish an IPsec tunnel terminating on the Cloud Router in us-central1.
- DConfigure a Private Service Connect (PSC) endpoint in europe-west1 targeting the control plane IP of the Cloud Router in us-central1.
Cevap
Setting the VPC network's dynamic routing mode from Regional to Global enables Cloud Routers in us-central1 to share learned BGP routes with resources across all regions in the VPC, including europe-west1.
In Google Cloud VPC networks, the dynamic routing mode determines the scope in which Cloud Routers share routes. In Regional dynamic routing mode (the default for auto-mode networks), a Cloud Router only learns and advertises routes for resources in its local region. By configuring the dynamic routing mode to Global, Cloud Routers share learned BGP routes (such as on-premises subnets learned over Cloud Interconnect) with all subnets across all regions in the VPC.
Adım Adım Çözüm
Anahtar Kavram
VPC Dynamic Routing Modes (Regional vs. Global)