An energy enterprise collects telemetry from millions of smart grid sensors. They are establishing hybrid connectivity between their primary on-premises data center and Google Cloud. The workload requires a sustained throughput of 12 Gbps with a strict 99.99% availability SLA. Additionally, three isolated workload environments (Production, Analytics, and Staging) residing in distinct VPC networks must reach on-premises resources. A draft proposal suggests deploying an HA VPN gateway to a central Transit VPC and connecting the spoke VPCs via VPC Network Peering so they can route through the Transit VPC to on-premises. Which architectural modification should a Cloud Architect implement to meet all throughput, availability SLA, and multi-VPC connectivity requirements?
- Provision Dedicated Interconnect with redundant 10 Gbps circuits across two metropolitan locations, and replace the Transit-Spoke VPC peering model with a Shared VPC architecture where the Host VPC contains the Interconnect VLAN attachments and Service Projects house the workload subnets.Cevap
- BUpgrade the on-premises connection to Dedicated Interconnect connected to the Transit VPC, while retaining the VPC Network Peering topology between the Transit VPC and spoke VPCs with custom route exports enabled.
- CScale the HA VPN architecture by adding five parallel HA VPN tunnels to the Transit VPC to accommodate 12 Gbps, and configure Cloud VPN gateways inside each spoke VPC to peer directly with the on-premises VPN gateways.
- DDeploy Partner Interconnect with Layer 2 connections in a single metropolitan location, and use Cloud Router with static routing to distribute traffic across the peered spoke VPCs.