How to Configure Network Connectivity Center for Hub-and-Spoke Architecture?
Your company deployed a hub and spoke architecture in Google Cloud to host their workloads. They use VPC network peerings to connect the hub and the spokes. You need to replicate the design and use Network Connectivity Center. What should you do?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests your understanding of NCC's logical grouping model versus physical topology, with the common trap being reversing the center/edge assignments or confusing star with mesh topologies.
This question tests configuring Google Cloud Network Connectivity Center to replicate a traditional hub-and-spoke VPC peering design using star topology. The community unanimously agrees that placing the hub VPC in the center group and spoke VPCs in the edge group is the correct implementation.
Candidates frequently choose option B by incorrectly assigning the hub VPC to the edge group, mistakenly assuming edge implies perimeter security rather than recognizing NCC's logical center-group routing model.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option A correctly aligns with Google Cloud's Network Connectivity Center architecture by utilizing a star topology. In this model, the central router or firewall resides in the center group, while all remote VPCs are registered as spokes in the edge group. This setup enables centralized policy enforcement, global routing management, and simplified peering without direct spoke-to-spoke connections.Why the Other Options Are Wrong
Option B reverses the logical placement, which directly contradicts NCC's design principles and breaks centralized routing. Options C and D suggest a mesh topology, which eliminates the centralized control plane and requires complex full-mesh peerings. Mesh configurations also bypass NCC's centralized routing benefits and increase operational overhead unnecessarily.Community Comment Notes
The community strongly validates option A, noting that keeping the hub in the central group with spokes in the edge group matches official documentation. One user shared the direct link to Google's NCC star topology overview, confirming the exact configuration steps. Another comment simply reinforces that A is the definitive answer based on recent exam experience.Official Reference
Exam Strategy
When studying Network Connectivity Center, focus on mapping legacy on-premises or basic VPC peering designs to GCP's managed networking constructs. Always visualize the logical hierarchy first: identify your centralized controller as the center group and distribute endpoints across the edge group before selecting a topology.
Related Analysis
Practice All PCNE Questions
Access 80 questions with complete answers and detailed explanations.
View Full PCNE Practice Test →