A renewable energy utility enterprise is migrating its smart grid telemetry platform to Google Cloud. The design requires connecting two primary on-premises data centers to a centralized Shared VPC host network in GCP to handle a sustained ingress throughput of 15 Gbps with a strict 99.99% uptime Service Level Agreement (SLA). Furthermore, analytics applications located in separate spoke VPCs peered to the Shared VPC host network must exchange data directly with on-premises databases. Which hybrid network architecture correctly satisfies both the SLA, bandwidth capacity, and VPC peering routing constraints?
- Establish Dedicated Interconnect connections with at least two attachments in two distinct metropolitan locations configured with Cloud Router and dynamic BGP routing in the Shared VPC host project, while utilizing Network Connectivity Center to enable dynamic route exchange between spoke VPCs and the hybrid connection.Answer
- BDeploy multiple High Availability (HA) Cloud VPN tunnels operating with active/active routing across the two data centers, and rely on standard VPC Network Peering routes to automatically transit on-premises traffic from the host VPC to all attached spoke VPCs.
- CProvision a single 20 Gbps Dedicated Interconnect circuit at one colocation facility, attach a Cloud Router using static routes, and configure VPC Network Peering between the host VPC and spoke VPCs to route on-premises traffic directly.
- DConfigure Partner Interconnect with Layer 2 connections in a single metropolitan region, utilizing static routes on Cloud Routers in each spoke VPC to bypass the Shared VPC host network completely.
Answer
The correct architecture requires establishing Dedicated Interconnect connections across dual metropolitan locations for 99.99% SLA compliance and 15 Gbps throughput capacity, combined with Network Connectivity Center to overcome VPC Peering non-transitivity between spoke VPCs and on-premises networks.
To achieve GCP's 99.99% SLA for hybrid connectivity, an organization must deploy Dedicated Interconnect with redundant links across two distinct metropolitan facilities (edge availability zones) with dynamic BGP routing via Cloud Router. Because the bandwidth demand is 15 Gbps, Dedicated Interconnect is required over Cloud VPN. Furthermore, since VPC Network Peering is non-transitive, Network Connectivity Center (NCC) must be integrated to enable dynamic routing and allow spoke VPC workloads to communicate with on-premises data centers through the host VPC's Interconnect connections.
Step-by-Step Solution
Key Concept
99.99% HA Dedicated Interconnect Topology and VPC Peering Non-Transitivity