QuestionQ52

VerifiedConfiguring and implementing hybrid and multi-cloud network interconnectivity

You are deploying a VPC architecture for your organization by using a Network Connectivity Center hub-and-spoke topology:

  • There is one Network Connectivity Center hybrid spoke that receives on-premises routes.
  • There is one VPC spoke that must be added as a Network Connectivity Center spoke.

Your organization has limited routable IP space for its cloud environment (192.168.0.0/20). The Network Connectivity Center spoke VPC connects to on-premises through a Cloud Interconnect connection in the us-east4 region. The on-premises IP range is 172.16.0.0/16. You must reach on-premises resources from multiple Google Cloud regions (us-west1, europe-central1, and asia-southeast1) while minimizing the IP addresses used. What should you do?

Explanation

Private NAT is regional: a gateway provides NAT for eligible VM interfaces that use subnets in its region, and its Private NAT addresses must come from a Private NAT subnet in the same region and VPC. Separate NAT subnets in the three workload regions are therefore required. The 192.168.x.0/24 ranges are within the available cloud address space and do not overlap the on-premises 172.16.0.0/16 range. An export include filter restricts the VPC spoke to exporting precisely those NAT subnet routes, and global dynamic routing permits cross-region access to hybrid connectivity in us-east4.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!