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.
An enterprise uses Network Connectivity Center (NCC) with a central hub connecting multiple workload VPC spokes and on-premises networks via hybrid spokes. The network engineering team needs to integrate two service environments so workloads across all spokes can consume them privately:
servicenetworking-googleapis-com) in a dedicated services VPC, where peering exports only Peering subnet routes with non-overlapping CIDR ranges.Which architecture should the team implement to integrate both service environments into the NCC hub while respecting spoke constraints, mitigating IP overlap, and enforcing security isolation?
servicenetworking-googleapis-com peering in the services VPC, and deploy Private Service Connect endpoints in a services VPC spoke attached to the NCC hub for the third-party SaaS platform with explicit connection authorization, firewall policies, and VPC Service Controls.Producer VPC spokes in Network Connectivity Center (NCC) allow an enterprise hub to exchange subnet routes directly with supported Google-managed service producer VPCs connected via Private Services Access (servicenetworking-googleapis-com or sn-netapp-* peering). Private Service Connect (PSC) provides a service-centric connectivity model that lets service consumers access third-party or first-party services via private internal IP endpoints in a consumer VPC without peering networks or allocating shared IP space.
servicenetworking-googleapis-com peering connection works because AlloyDB for PostgreSQL and Cloud SQL are supported services, their peering exports only Peering subnet routes, and their non-overlapping CIDR ranges can be safely advertised across the NCC hub to workload and hybrid spokes.This hybrid pattern respects the strict operational boundary of producer VPC spokes (supported Google-managed Private Services Access only) while leveraging Private Service Connect over an NCC VPC spoke to cleanly decouple third-party multi-tenant SaaS routing, prevent IP collisions, and enforce zero-trust isolation.
This architecture uses a hybrid spoke (HA VPN with BGP) to bridge the third-party SaaS provider into the enterprise network, while attempting to expose Private Service Connect (PSC) endpoints to workload VPCs across VPC Network Peering.
servicenetworking-googleapis-com). Integrating them into NCC requires a producer VPC spoke, not PSC endpoints over VPC peering.The third-party platform were hosted in an external on-premises data center with non-overlapping IP space connected via a hybrid spoke, and workload VPCs were attached as NCC VPC spokes rather than using VPC Network Peering to reach PSC endpoints.
This design relies solely on a standard NCC VPC spoke for the services VPC and attempts to use VPC Network Peering between the services VPC and the third-party SaaS VPC to expose both Google-managed and third-party workloads to the rest of the NCC hub.
servicenetworking-googleapis-com Private Services Access peering. A dedicated producer VPC spoke is required for NCC spokes to reach those managed service subnets.Only workloads directly hosted inside the services VPC's own subnets needed to be shared with the hub, and neither Private Services Access workloads nor overlapping third-party SaaS networks were involved.
servicenetworking-googleapis-com peering and the third-party SaaS provider's VPC Network Peering connection, and configure custom route export filters on the hub to block overlapping SaaS IP ranges.This approach attempts to onboard both first-party Google Cloud managed services and a third-party SaaS vendor into Network Connectivity Center (NCC) using producer VPC spokes, while relying on hub-level route filtering to suppress conflicting vendor prefixes.
servicenetworking-googleapis-com or sn-netapp-* peering connections.servicenetworking-googleapis-com (or sn-netapp-* for NetApp Volumes) and exports only Peering subnet routes.Both environments were supported Google Cloud managed services deployed through Private Services Access with completely non-overlapping, unique RFC 1918 CIDR allocations across every tenant and producer VPC.
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