An organization deploys Compute Engine instances across two regions, us-central1 and europe-west1, within a single custom-mode Virtual Private Cloud (VPC) network. A Cloud Router and Dedicated Interconnect attachment are configured in us-central1 to exchange BGP routes with an on-premises data center. Workloads in us-central1 can communicate with on-premises resources, but workloads in europe-west1 cannot reach on-premises IP ranges because dynamic routes learned by the Cloud Router are missing from the routing table in europe-west1. Which configuration change should the cloud architect implement to enable inter-region dynamic route propagation across the VPC?
- Change the dynamic routing mode of the VPC network from Regional to Global.Cevap
- BEstablish a VPC Network Peering connection between the us-central1 subnet and the europe-west1 subnet and enable custom route export.
- CReplace the Dedicated Interconnect with an HA VPN gateway in europe-west1 because Cloud Routers cannot share Interconnect routes across regions.
- DCreate a VPC Service Controls perimeter encompassing the europe-west1 subnet and configure an egress rule for the on-premises network.
Cevap
Change the dynamic routing mode of the VPC network from Regional to Global.
Google Cloud VPC networks support two dynamic routing modes: Regional and Global. When set to Regional dynamic routing, a Cloud Router only installs learned BGP routes into the subnets of its local region. Setting the VPC network dynamic routing mode to Global configures Cloud Routers to advertise and install dynamically learned routes across subnets in all regions within the VPC, allowing instances in europe-west1 to seamlessly route traffic through the us-central1 Cloud Interconnect.
Adım Adım Çözüm
Anahtar Kavram
VPC Dynamic Routing Modes (Regional vs. Global)