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 enterprise manages 60 Google Cloud workload projects across three business units (20 projects per unit) and a Dedicated Interconnect connection to your on-premises data center. You must redesign the network to meet these requirements:
Which architecture should you implement?
Network Connectivity Center (NCC) uses a central hub resource as a control plane to orchestrate connectivity among VPC spokes and hybrid spokes. In a star topology, VPC spokes are assigned to either a center group (full-mesh connectivity among center spokes) or an edge group (point-to-point paths only to center-group VPCs, blocking direct edge-to-edge communication).
The organization did not require inline Layer 7 NGFW NVA inspection between business units and on-premises networks, and only needed direct subnet-level isolation between edge-group Shared VPCs and shared services or hybrid attachments in the center group.
In a full VPC Network Peering mesh, every VPC network establishes a direct peering relationship with every other VPC network. Peered VPCs automatically exchange all subnet routes over Google's internal software-defined network (SDN), enabling direct private IPv4 and IPv6 communication at full VM bandwidth.
N*(N-1)/2 peering connections and shares aggregate peering-group quotas (such as internal forwarding rules and VM instances) across all directly peered networks.Inline Layer 7 NVA inspection was not required for either inter-unit or hybrid traffic, the transit VPC simply exported on-premises dynamic routes directly to the peered Shared VPCs, and the total number of VPCs remained small.
Combining Shared VPC with a hub-and-spoke VPC Network Peering topology and centralized network virtual appliances (NVAs) provides both centralized network governance and inline Layer 7 inspection at scale. Each business unit operates a Shared VPC host project that centralizes subnets, routes, and firewalls while delegating VM deployment to attached service projects.
This design is the recommended Google Cloud pattern when enterprises need centralized multi-project network administration, inline Layer 7 appliance inspection, and high-bandwidth private connectivity without exhausting VPC peering quotas.
An HA VPN hub-and-spoke architecture replaces VPC Network Peering with IPsec VPN tunnels and Cloud Router eBGP sessions between each spoke VPC and a central hub VPC. Because BGP dynamically exchanges prefixes across tunnels, HA VPN enables transitive routing between spokes and avoids VPC Network Peering limits.
All 60 project teams required complete administrative autonomy over their own VPC routing and firewalls, transitive spoke-to-spoke routing without centralized NVAs was needed, and the workloads could tolerate Cloud VPN tunnel throughput limits and encapsulation overhead.
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