A global retail company is establishing hybrid connectivity between its primary on-premises data center and Google Cloud. The workload requires a continuous 20 Gbps low-latency connection backed by an enterprise SLA. Within Google Cloud, the architecture requires central governance for core services while allowing two isolated workload VPCs (Logistics and Inventory) to communicate with on-premises resources, while strictly preventing inter-VPC traffic between the two workload VPCs. Which network architecture should the cloud architect recommend?
- Provision a Dedicated Interconnect with multiple 10 Gbps circuits using Cloud Router for dynamic BGP routing, and implement a Shared VPC topology attaching the workload projects as Service Projects.Cevap
- BProvision an HA VPN gateway with multiple IPsec tunnels to aggregate 20 Gbps capacity using Cloud Router, and connect the workload VPCs to a central Hub VPC using VPC Network Peering.
- CProvision a Dedicated Interconnect with multiple 10 Gbps circuits, and connect the workload VPCs to a central Transit VPC using VPC Network Peering to allow transitive connectivity to on-premises.
- DProvision Partner Interconnect with 1 Gbps connections configured over public Internet IPSec VPN tunnels, attaching static routes in Cloud Router for each independent VPC.
Cevap
Provision a Dedicated Interconnect with multiple 10 Gbps circuits using Cloud Router for dynamic BGP routing, and implement a Shared VPC topology attaching the workload projects as Service Projects.
Dedicated Interconnect is the correct hybrid connection choice for high-throughput (20 Gbps) continuous enterprise traffic requiring an enterprise SLA. Coupled with a Shared VPC architecture, the Host Project manages the Cloud Routers and Interconnect attachments while Service Projects (Logistics and Inventory) securely utilize the network paths to on-premises without relying on non-transitive VPC Peering.
Adım Adım Çözüm
Anahtar Kavram
Hybrid Connectivity Selection and Shared VPC Topology Design