A retail enterprise is designing hybrid connectivity between its primary on-premises data center and Google Cloud. The architecture requires transferring continuous backup data streams at a rate of 12 Gbps. Additionally, multiple project VPC networks need to communicate centrally with on-premises services without relying on non-supported routing behaviors between VPC networks. Which TWO architectural decisions should the cloud architect implement to fulfill these requirements? (Select TWO.)
- Provision a Dedicated Interconnect connection to support the required throughput of 12 Gbps between the on-premises facility and Google Cloud.Answer
- Design a Shared VPC topology or hub-and-spoke model using VPN/Interconnect gateways in a host project rather than expecting VPC Network Peering to route traffic transitively across spoke VPCs.Answer
- CDeploy an HA VPN gateway with multiple IPSec tunnels over the public internet to handle the continuous 12 Gbps data transfer requirement.
- DConfigure sequential VPC Network Peering pairs across spoke VPCs to enable transitive routing from all spokes back to the on-premises network.
Answer
The architect must provision Dedicated Interconnect for high-bandwidth data transfers exceeding 10 Gbps and adopt a Shared VPC or central hub architecture instead of assuming VPC Network Peering provides transitive routing.
Dedicated Interconnect delivers physical 10 Gbps or 100 Gbps connections necessary for bandwidth requirements of 12 Gbps, while adopting Shared VPC or central hub routing accounts for the fundamental non-transitive limitation of VPC Network Peering.
Step-by-Step Solution
Key Concept
Hybrid Cloud Connectivity and VPC Peering Transitivity Constraints