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 uses a Network Connectivity Center (NCC) hub in us-central1 connecting an on-premises network (via a hybrid VLAN spoke in routing-vpc) to two VPC spokes:
prod-vpc: Has subnet 10.20.0.0/16 (no export filters), which appears in the NCC hub route table, yet on-premises never receives it. The hybrid spoke uses include-import-ranges 10.20.0.0/17 and exclude-import-ranges 10.30.0.0/24.dev-vpc: Learns 192.168.10.0/24 from a local Cloud Router VPN session. The hybrid spoke also advertises 192.168.10.0/24 to the hub, yet dev-vpc ignores the NCC route.Which diagnostic findings and verification steps accurately explain both routing behaviors?
10.20.0.0/16 subnet is blocked because it overlaps with the hybrid spoke's exclude-import-ranges (10.30.0.0/24), and running Connectivity Tests from an on-premises IP to 10.20.0.0/16 will inspect the on-premises router's BGP table to confirm the drop; meanwhile, dev-vpc hides the 192.168.10.0/24 NCC route because dev-vpc uses legacy best path selection instead of standard mode.exclude-import-ranges, Connectivity Tests, and Best Path Selection DoExclude import filters block hub routes that intersect specified CIDR blocks, Connectivity Tests simulates packet forwarding paths across Google Cloud configurations, and Cloud Router best path selection mode (legacy or standard) governs how BGP attributes like AS path length and MED are evaluated.
exclude-import-ranges: The subnet 10.20.0.0/16 and the exclude filter 10.30.0.0/24 are completely disjoint IP ranges. The route fails before exclude-filter evaluation because 10.20.0.0/16 is not wholly contained inside include-import-ranges (10.20.0.0/17).dev-vpc suppresses the candidate NCC dynamic route for 192.168.10.0/24 because a local dynamic route with the exact same prefix already exists in dev-vpc. Local dynamic routes always take precedence over and suppress exact-match candidate NCC dynamic routes regardless of whether legacy or standard best path selection is enabled.10.20.0.0/16 spans 10.20.0.0–10.20.255.255, whereas 10.30.0.0/24 spans 10.30.0.0–10.30.0.255.legacy mode is actually recommended across VPCs.The exclude-import-ranges filter were 10.20.128.0/24 (which intersects 10.20.0.0/16) and you only needed Connectivity Tests to validate forwarding inside the Google Cloud VPC and NCC hub components.
10.20.0.0/16 route is not imported by the hybrid spoke because it is not wholly contained within 10.20.0.0/17, which you can confirm by inspecting outbound advertisements with gcloud compute routers list-bgp-routes; meanwhile, dev-vpc suppresses the candidate NCC dynamic route for 192.168.10.0/24 because an exact-match local dynamic route exists, which must be verified in the Google Cloud console Effective routes tab with Show suppressed routes enabled.Network Connectivity Center (NCC) hybrid spoke import filters strictly evaluate whether hub routes fit completely inside permitted CIDR boundaries before allowing Cloud Router to advertise them to on-premises peers. Simultaneously, the VPC control plane resolves prefix conflicts independently per VPC network by enforcing route precedence between local dynamic routes and candidate NCC dynamic routes.
10.20.0.0/16 advertisement to on-premises: For a hybrid spoke to import a subnet route from the NCC hub, the prefix must be wholly contained within at least one include-import-ranges CIDR and must not intersect any exclude-import-ranges CIDR. Because 10.20.0.0/16 is broader than 10.20.0.0/17, it only partially intersects the filter and is not imported into the hybrid spoke. Running gcloud compute routers list-bgp-routes with --route-direction=OUTBOUND and toggling --policy-applied versus --no-policy-applied confirms that the prefix is never presented for BGP advertisement rather than being dropped by an outbound BGP route policy.192.168.10.0/24 NCC route in dev-vpc: When a VPC spoke already has a local dynamic route (learned from a local Cloud Router VPN session) whose destination prefix exactly matches a candidate NCC dynamic route, the VPC control plane suppresses the candidate NCC dynamic route.gcloud compute routers list-bgp-routes isolates whether a missing outbound announcement is caused by NCC spoke filtering or a Cloud Router BGP route policy.router_events: Logs Advertising prefix to peers and Withdrawing prefix from peers on gce_router resources to confirm real-time BGP propagation.Unlike gcloud compute routes list—which omits dynamic and suppressed routes—or gcloud compute routers get-status—which focuses on inbound bestRoutesForRouter—combining list-bgp-routes with the console Effective routes view accurately diagnoses both CIDR filter non-containment and VPC dynamic route suppression.
10.20.0.0/16 because Cloud Router requires a matching custom IP range advertisement for 10.20.0.0/16 in addition to include-import-ranges, with the drop logged in compute.googleapis.com/router_events; meanwhile, dev-vpc ignores the 192.168.10.0/24 NCC route because dev-vpc has regional dynamic routing mode enabled instead of global dynamic routing mode.Cloud Router custom advertisements allow administrators to manually advertise specific IPv4 or IPv6 prefixes over a BGP session, while VPC dynamic routing mode (regional vs global) controls whether Cloud Routers advertise and propagate dynamic routes across regions within a VPC network.
include-import-ranges and Cloud Router custom advertisements are two separate techniques for advertising NCC hub subnets. In fact, if hybrid spoke import filters already cause an NCC-imported subnet route to be advertised, the BGP session omits any custom advertisement that exactly matches that NCC-imported subnet range.router_events: compute.googleapis.com/router_events records BGP peering state changes, router task activations, and prefixes actually advertised to or withdrawn from BGP peers—it does not log NCC spoke filter mismatches for routes never imported by the hybrid spoke.us-central1. Even in regional dynamic routing mode, routes are exchanged within the same region. dev-vpc ignores the NCC route solely because an exact-match local dynamic route (192.168.10.0/24) suppresses the candidate NCC dynamic route.You intentionally left include-import-ranges unconfigured on the hybrid spoke and relied solely on Cloud Router custom advertisements to announce 10.20.0.0/16, while dev-vpc was attempting to reach a dynamic route learned by a hybrid spoke in a different Google Cloud region.
10.20.0.0/17 to on-premises, so the missing 10.20.0.0/16 route is caused by an outbound BGP route policy visible as DROPPED in gcloud compute routers get-status; meanwhile, dev-vpc drops the 192.168.10.0/24 NCC route due to a Cloud Router learned-route quota logged in router.googleapis.com/route_quota_events, which is verified using gcloud compute routes list.gcloud compute routers get-status, Cloud Router route quota events (router.googleapis.com/route_quota_events), and gcloud compute routes list each inspect different layers of Google Cloud routing, but none of them operate in the manner described.
10.20.0.0/16 subnet route is never sliced into 10.20.0.0/17 for BGP advertisement; it is simply not imported at all.DROPPED status: In gcloud compute routers get-status, the bestRoutesForRouter.routeStatus field (ACTIVE or DROPPED) reports the state of inbound BGP routes learned by the Cloud Router from peers, not outbound hub subnet advertisements filtered by BGP route policies.gcloud compute routes list: Neither gcloud compute routes list nor the Compute Engine routes.list API displays dynamic routes, policy-based routes, or suppressed routes.gcloud compute routers list-bgp-routes with --no-policy-applied compared against --policy-applied.router.googleapis.com/route_quota_events (on gce_network_region) records when Cloud Router learned route quotas (from own region or other regions) hit 75% warning or 100% error thresholds, not when a local dynamic route suppresses an NCC dynamic route.An inbound on-premises prefix learned by Cloud Router were filtered or dropped due to exceeding a Cloud Router dynamic route prefix quota (route_quota_events), while inspecting static or NCC subnet routes via gcloud compute routes list.
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