A company has a hub-and-spoke VPC topology with multiple on-premises locations connected via Cloud VPN to the hub VPC. They notice IP conflicts because overlapping CIDR ranges are used in different spokes. The network team wants to allow communication between spokes without re-IPing. What should they do?
Trap 1: Use Cloud VPN tunnels between spokes through the hub.
VPN tunnels can work with overlapping ranges but require careful routing and possibly NAT; however, overlapping ranges will cause routing ambiguity.
Trap 2: Configure static routes in the hub to summarize ranges with a…
Summarizing does not resolve the overlap; traffic will still be confused.
Trap 3: Create VPC peering between each spoke VPC.
VPC peering does not support overlapping IP ranges; it will fail.
- A
Use Cloud NAT in each spoke and private routing via the hub with network tags to distinguish ranges.
Cloud NAT can map overlapping private IPs to a unique internal IP range within the hub, and tags can help route traffic appropriately, though this approach has limitations; alternative is to re-IP. But among options, this allows some communication without re-IPing.
- B
Use Cloud VPN tunnels between spokes through the hub.
Why wrong: VPN tunnels can work with overlapping ranges but require careful routing and possibly NAT; however, overlapping ranges will cause routing ambiguity.
- C
Configure static routes in the hub to summarize ranges with a smaller prefix.
Why wrong: Summarizing does not resolve the overlap; traffic will still be confused.
- D
Create VPC peering between each spoke VPC.
Why wrong: VPC peering does not support overlapping IP ranges; it will fail.