A solutions architect is planning a multi-region network layout for an enterprise application across two custom-mode Virtual Private Cloud (VPC) networks named `vpc-analytics` and `vpc-services`. The organization plans to establish VPC Network Peering between `vpc-analytics` and `vpc-services` so instances in both networks can communicate using internal IP addresses. Which network planning requirement must be met before creating the VPC Network Peering connection?
- The primary and secondary IP ranges of subnets in both VPC networks must not overlap.Cevap
- BBoth VPC networks must first be converted from custom-mode to auto-mode VPC networks.
- CSubnets in both VPC networks must be created within the same Google Cloud region.
- DFirewall rules from both networks must be combined into a single legacy network configuration.
Cevap
The primary and secondary IP ranges of subnets in both VPC networks must not overlap.
VPC Network Peering enables private RFC 1918 connectivity between two VPC networks. A fundamental constraint of GCP VPC Network Peering is that no subnets (including primary and secondary IP ranges) can overlap between the peered networks.
Adım Adım Çözüm
Anahtar Kavram
VPC Network Peering IP Non-Overlap Requirement
Tahmini Süre:1m 30s