Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization is scaling from 10 to 60 application teams, each deploying development and production workloads in separate projects. Your architecture must meet these requirements:
Which VPC architecture should you implement?
A single Shared VPC network consolidates all participating service projects into one global virtual network inside a single host project. Google Cloud's software-defined networking (SDN) automatically establishes full-mesh IP reachability across every subnet in that VPC network, relying on VPC firewall rules or firewall policies to restrict traffic between subnets.
compute.networkAdmin and compute.securityAdmin are enforced at the project level. With a single host project and single VPC, administrators who manage development networking also gain permissions over production networking.All 120 projects belonged to a single environment with uniform administrative policies, shared compliance boundaries, and no requirement for network-layer separation or independent quotas between development and production.
Even when using Shared VPC, standard landing zone best practices recommend provisioning a separate Shared VPC network in its own host project for each deployment environment (such as development, staging, and production) to enforce strict security, quota, and IAM boundaries.
A multi-host Shared VPC architecture designates a dedicated host project for each deployment environment (development and production), with each host project containing a single Shared VPC network. Individual team projects are attached as service projects to the corresponding environment's host project, allowing workloads across projects to communicate over private internal IP addresses within a centrally managed network.
compute.networkUser role at the subnet level enforces least privilege.compute.networkAdmin and compute.securityAdmin) per environment, while supporting up to 1,000 service projects per host project.Unlike standalone VPC topologies connected via VPC Network Peering or Network Connectivity Center (NCC), Shared VPC eliminates per-team network administration and inter-VPC transit fees. Unlike consolidating both environments into a single Shared VPC network, using two host projects guarantees strict VPC-level network isolation, separate IAM boundaries, and independent quotas for development and production.
Network Connectivity Center (NCC) provides an orchestration control plane that connects multiple VPC networks as VPC spokes and hybrid connections (such as Cloud Interconnect VLAN attachments) as hybrid spokes to a central NCC hub. In a mesh topology, NCC establishes full-mesh transitive connectivity across up to 250 active VPC spokes per hub, avoiding the 25-peering limit and peering-group scaling constraints of VPC Network Peering.
The organization needed to interconnect dozens of pre-existing or autonomous standalone VPC networks across different business units or organizations, required transitive Private Service Connect propagation, and could accept inter-VPC transit costs.
In large enterprise landing zones, Shared VPC is commonly used to consolidate teams into environment-level networks first, minimizing both operational complexity and inter-VPC data transfer charges. NCC is best reserved for connecting the resulting environment or business-unit VPCs when cross-VPC connectivity is genuinely required.
In a hub-and-spoke VPC Network Peering design, each team operates an autonomous standalone VPC network inside its own project and peers that VPC to a central routing (hub) VPC network hosting the Dedicated Interconnect VLAN attachments. VPC Network Peering exchanges subnet routes over Google's private backbone with the same latency, bandwidth, and low egress pricing as intra-VPC traffic.
Spoke A -> Hub -> Spoke B).The organization had only a few projects (two to three) belonging to autonomous teams or separate organizations that required independent network administration and did not need spoke-to-spoke communication.
While VPC Network Peering avoids inter-VPC transit fees, it is designed for connecting a small number of independent networks rather than scaling dozens of internal teams under centralized control. For sharing Cloud Interconnect across many projects within one organization, Shared VPC is easier to configure, manage, and scale.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated