An organization is executing a disaster recovery (DR) test to validate hybrid failover from their on-premises data center to a secondary Google Cloud Virtual Private Cloud (VPC-B). The on-premises environment connects directly to VPC-A using Cloud VPN, while VPC-A is connected to VPC-B using VPC Network Peering. During the DR test, on-premises workloads fail to reach resources in VPC-B. Which action should the cloud architect take to establish connectivity for the DR failover scenario?
- Deploy a direct hybrid connection such as Cloud VPN between the on-premises network and VPC-B, because VPC Network Peering does not support transitive routing.Cevap
- BEnable custom route exchange on the VPC Peering connection in VPC-A to transit the on-premises Cloud VPN routes directly into VPC-B.
- CMigrate the target relational database in VPC-B to Cloud Spanner to natively bypass VPC peering constraints during disaster recovery.
- DProvision a new Dedicated Interconnect during the active DR event to replace Cloud VPN without prior quota management.
Cevap
Deploy a direct hybrid connection such as Cloud VPN between the on-premises network and VPC-B, because VPC Network Peering does not support transitive routing.
VPC Network Peering does not support transitive routing. Traffic originating on-premises over Cloud VPN entering VPC-A cannot traverse VPC Peering to reach VPC-B. Establishing direct VPN connectivity to VPC-B provides the necessary network pathway for disaster recovery execution.
Adım Adım Çözüm
Anahtar Kavram
VPC Network Peering Non-Transitivity in Disaster Recovery