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 deploying a Network Connectivity Center (NCC) hub to centralize access to third-party managed services published via Private Service Connect (PSC) across multiple Google Cloud VPCs and an on-premises data center. Your architecture has the following setup and requirements:
psc-hub-vpc): Hosts shared PSC endpoints in 10.10.1.0/24 (with Accepted status) that must be reachable from all workload VPCs and on-premises networks, plus restricted PSC endpoints in 10.10.2.0/24 that must remain local to psc-hub-vpc.workload-vpc): Contains a non-overlapping subnet (10.20.1.0/24) that needs access to the shared PSC endpoints, and an overlapping subnet (192.168.1.0/24) that uses a Private NAT gateway to reach the NCC hub.transit-vpc-a and HA VPN tunnels in transit-vpc-b, both attached as hybrid spokes to the same NCC hub.After enabling --export-psc on the hub and adding psc-hub-vpc and workload-vpc as VPC spokes, workloads in 10.20.1.0/24 and on-premises clients still cannot reach the shared PSC endpoints, and you must prevent 10.10.2.0/24 from propagating. Which configuration changes should you implement?
transit-vpc-a, add transit-vpc-a to the hub as a VPC spoke with --include-import-ranges=ALL_IPV4_RANGES on the hybrid spokes, add 10.10.2.0/24 to --exclude-export-ranges on psc-hub-vpc, and configure Private NAT in workload-vpc using --nat-custom-subnet-ip-ranges for 192.168.1.0/24 only.Private Service Connect (PSC) connection propagation in Network Connectivity Center (NCC) makes PSC endpoints in one VPC spoke transitively reachable from other VPC spokes and, when properly architected, from on-premises networks connected through hybrid spokes.
transit-vpc-a and adding transit-vpc-a as a VPC spoke satisfies this rule. Setting --include-import-ranges=ALL_IPV4_RANGES on the hybrid spokes ensures the Cloud Routers advertise the imported NCC hub IPv4 routes (including propagated PSC endpoint prefixes) to on-premises BGP peers.10.10.2.0/24: Adding 10.10.2.0/24 to --exclude-export-ranges on the psc-hub-vpc VPC spoke prevents NCC from exporting that subnet and propagating any PSC endpoints hosted within it to other spokes.10.20.1.0/24 access alongside Private NAT: When a subnet uses Private NAT to reach the NCC hub, traffic from that subnet to a propagated PSC service is dropped. By configuring Private NAT with --nat-custom-subnet-ip-ranges targeting only the overlapping 192.168.1.0/24 subnet, the non-overlapping 10.20.1.0/24 subnet bypasses Private NAT and reaches the propagated PSC endpoints directly.This design resolves both the multi-routing-VPC restriction for hybrid PSC propagation and the Private NAT packet-drop behavior while enforcing strict subnet-level isolation for restricted endpoints.
transit-vpc-a with --include-import-ranges=ALL_IPV4_RANGES without adding transit-vpc-a as a VPC spoke, configure psc-hub-vpc as a producer VPC spoke with 10.10.2.0/24 in --exclude-export-ranges, and configure Private NAT in workload-vpc using --nat-custom-subnet-ip-ranges for 192.168.1.0/24 only.This option consolidates hybrid spokes into a single routing VPC network (transit-vpc-a) without adding it as a VPC spoke, and converts psc-hub-vpc into a producer VPC spoke while attempting to use --exclude-export-ranges and targeted Private NAT.
psc-hub-vpc is a consumer VPC hosting PSC endpoints rather than a peered producer network.transit-vpc-a: Even with a single routing VPC network, hybrid spokes cannot receive propagated PSC connections unless that routing VPC network is also added as a VPC spoke to the NCC hub.--nat-custom-subnet-ip-ranges on 192.168.1.0/24 is valid for workload-vpc, but cannot compensate for the unsupported spoke configuration.psc-hub-vpc remained a standard VPC spoke (not a producer VPC spoke) and transit-vpc-a were explicitly attached to the NCC hub as a VPC spoke alongside its hybrid spokes.Administrators frequently confuse producer VPC spokes (for private services access over VPC Network Peering) with PSC connection propagation (for PSC forwarding-rule endpoints in standard VPC spokes).
transit-vpc-a and transit-vpc-b as separate routing VPCs, attach both to the hub as VPC spokes with --include-import-ranges=ALL_IPV4_RANGES on the hybrid spokes, add 10.10.2.0/24 to --exclude-export-ranges on psc-hub-vpc, and configure Private NAT in workload-vpc using --nat-all-subnet-ip-ranges.This approach attempts to preserve two separate routing VPC networks (transit-vpc-a and transit-vpc-b) while attaching both as VPC spokes, and applies Private NAT across all subnets in workload-vpc using --nat-all-subnet-ip-ranges.
--nat-all-subnet-ip-ranges breaks 10.20.1.0/24: Traffic sent from a subnet configured with Private NAT toward the NCC hub is dropped when targeting a propagated PSC service. Using --nat-all-subnet-ip-ranges applies Private NAT to every subnet in workload-vpc, breaking propagated PSC connectivity for the non-overlapping 10.20.1.0/24 subnet.--exclude-export-ranges on psc-hub-vpc correctly isolates 10.10.2.0/24, but cannot fix downstream routing or NAT drops.--nat-all-subnet-ip-ranges should never be used in a spoke VPC that has non-overlapping subnets needing access to propagated PSC endpoints.--nat-custom-subnet-ip-ranges for 192.168.1.0/24 only.When designing hybrid transit with NCC PSC propagation, Cloud Interconnect VLAN attachments and HA VPN tunnels must share a single routing VPC network if on-premises clients need direct reachability to propagated endpoints.
transit-vpc-a and add transit-vpc-a as a VPC spoke without setting --include-import-ranges on the hybrid spokes, add 10.10.2.0/24 to --exclude-export-ranges on psc-hub-vpc, and configure Private NAT in workload-vpc using --nat-custom-subnet-ip-ranges targeting 10.20.1.0/24.This configuration correctly consolidates hybrid spokes into transit-vpc-a as a single routing VPC and VPC spoke, and excludes 10.10.2.0/24 from export, but omits import route configuration on the hybrid spokes and targets the wrong subnet (10.20.1.0/24) with Private NAT.
10.20.1.0/24 drops PSC traffic: Traffic originating from any subnet configured with Private NAT toward the NCC hub is dropped when destined for a propagated PSC endpoint. Targeting 10.20.1.0/24 with --nat-custom-subnet-ip-ranges directly breaks PSC reachability for 10.20.1.0/24 while failing to translate the overlapping 192.168.1.0/24 subnet.--include-import-ranges=ALL_IPV4_RANGES (or configuring custom route advertisements on the Cloud Routers), the hybrid spokes in transit-vpc-a will not automatically import and re-advertise the NCC hub's subnet and propagated PSC routes to on-premises BGP neighbors.192.168.1.0/24), leaving non-overlapping subnets (10.20.1.0/24) un-translated.ALL_IPV4_RANGES) or Cloud Router custom advertisements to propagate hub routes externally.--include-import-ranges=ALL_IPV4_RANGES were configured on the hybrid spokes and --nat-custom-subnet-ip-ranges targeted 192.168.1.0/24 instead of 10.20.1.0/24.In hybrid NCC deployments, route exchange is bidirectional: VPC spokes automatically import routes from their hub group, whereas hybrid spokes rely on import filters to control which hub routes are advertised over BGP.
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