Following an acquisition, Sandrine Foods must connect a manufacturer whose data centres consume almost all of 10.0.0.0/8, including ranges already used by Sandrine's production VPC. Re-addressing either estate is impossible because of embedded shop-floor controllers. New Google Cloud subnets are needed for the acquired workloads, which must initiate connections to a shared inventory service in Sandrine's existing VPC. What should you do?
- A.
Allocate the new subnets from the RFC 6598 range 100.64.0.0/10, which Google Cloud supports as a privately used non-RFC 1918 subnet range, and peer that VPC with Sandrine's production VPC.
- B.
Re-address the acquired company's shop-floor networks into 172.16.0.0/12 before the first migration wave.
- C.
Create a VPC Network Peering connection between the two networks and enable the option to allow overlapping subnet ranges.
- D.
Assign external IPv6 addresses to the migrated workloads and reach the inventory service through an external Application Load Balancer over the public internet, restricted by a Google Cloud Armor allowlist.
Show answer
Answer: A
Google Cloud subnets accept non-RFC 1918 ranges, so carving the new subnets from 100.64.0.0/10 avoids the collision entirely and lets the two VPCs peer.
- A. Google Cloud VPC subnets accept non-RFC 1918 ranges such as 100.64.0.0/10, giving the migrated workloads address space that collides with neither estate and peers cleanly.
- B. Re-addressing the shop-floor networks is exactly the project the business ruled out because of the embedded controllers.
- C. VPC Network Peering explicitly refuses to establish when subnet ranges overlap and offers no setting to permit the overlap.
- D. Fronting an internal inventory service with an internet-facing load balancer adds public exposure and latency when private, non-overlapping connectivity is available.