How to Configure Full VPC Connectivity in Network Connectivity Center?
You are using Network Connectivity Center and you already have the hub configured. All VPCs in your environment need to have network connectivity to each other. All the subnet ranges are unique. You need to configure your topology accordingly. What should you do?
Community Votes
83% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests whether you recognize that full mutual connectivity requires a mesh topology rather than a star topology, while correctly identifying that unique subnets eliminate the need for export range filtering.
This question evaluates your understanding of Hub-and-Spoke topologies in Google Cloud Network Connectivity Center, specifically distinguishing between star and mesh routing behaviors. The community consensus confirms that a mesh topology is mandatory for full inter-VPC connectivity when all subnet ranges are unique.
Option D is frequently selected because candidates mistakenly equate any hub-and-spoke architecture with a traditional star topology, overlooking that NCC automatically enables full mesh routing between spokes upon attachment.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
When VPC spokes are attached to a Network Connectivity Center hub, the service automatically establishes a full Layer 3 mesh between them, enabling direct communication across all VPCs without manual route table configuration. Because the scenario explicitly states that all subnet ranges are unique, there is zero risk of IP overlap, making the excludeExportRanges filter entirely unnecessary. This aligns perfectly with option C, which relies on native NCC behavior.
Why the Other Options Are Wrong
Star topology options incorrectly assume that all cross-VPC traffic must traverse the central hub, which directly contradicts how NCC handles spoke-to-spoke routing in modern cloud environments. Adding theexcludeExportRanges filter in options A and B serves as a distractor meant to test knowledge of overlapping CIDR blocks, which does not apply to this unique-range scenario. Consequently, these choices introduce unnecessary complexity and misrepresent the service's automatic meshing capabilities.Community Comment Notes
Experienced candidates like comment [2] correctly emphasize that mesh topology guarantees full mutual connectivity while noting that unique subnets eliminate filtering requirements. Comment [1] successfully points readers to the official Google Cloud documentation that validates this automatic meshing behavior. Although comment [3] argues for a star configuration based on physical wiring concepts, certification exams prioritize logical routing outcomes and managed service defaults over traditional diagram interpretations.Official Reference
Exam Strategy
Always distinguish between physical topology diagrams and logical routing behaviors in fully managed services; Google Cloud’s NCC automatically creates a full mesh between spokes, so focus on platform defaults rather than traditional on-prem designs. When subnet ranges are explicitly stated as unique, immediately rule out any options involving overlap prevention or export filtering to save time.
Related Analysis
Practice All PCNE Questions
Access 80 questions with complete answers and detailed explanations.
View Full PCNE Practice Test →