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 Network Connectivity Center (NCC) to connect VPC spokes (vpc-prod-a, vpc-prod-b) and regional VLAN attachment spokes (spoke-east in us-east4, spoke-west in us-west1) to a central hub. After adding subnet 10.50.4.0/24 to vpc-prod-a in us-east4, on-premises hosts behind spoke-east cannot reach it, though existing vpc-prod-a subnets remain reachable.
You inspect the telemetry:
us-east4 show no LINK_DOWN, CONFIG_DISABLED, or route_quota_events entries, and the BGP session is Established.10.50.4.0/24 as ACTIVE.gcloud compute routers get-status omits 10.50.4.0/24 from the peer's advertisedRoutes.What is the most likely cause of this issue, and how should you resolve it?
VPC spoke export filters (include-export and exclude-export) control which subnet CIDR ranges from an attached VPC network are propagated into the Network Connectivity Center (NCC) hub route table. Administrators use these filters to prevent overlapping or restricted internal subnets from being shared with other spokes in the hub.
Export filters operate at the boundary between the VPC spoke and the NCC hub. If an exclude-export or include-export filter were blocking 10.50.4.0/24, the prefix would never enter the NCC control plane:
vpc-prod-a successfully exported 10.50.4.0/24 into NCC.advertisedRoutes on individual Cloud Router BGP peers.This would be the correct diagnosis if inspecting the hybrid spoke group's hub route table showed that 10.50.4.0/24 was completely missing from the hub route table rather than listed as ACTIVE.
When troubleshooting missing hub subnets on-premises, always check the hub route table first to isolate whether filtering occurs at the VPC spoke boundary (absent from hub route table) or at the Cloud Router BGP boundary (present in hub route table, absent from advertisedRoutes).
Cloud Router dynamic route quotas limit the number of unique destination prefixes that a VPC network can learn inbound from BGP peers (CLOUD-ROUTER-PREFIXES-FROM-OWN-REGION-Per-Region-Per-VPC and CLOUD-ROUTER-PREFIXES-FROM-OTHER-REGIONS-Per-Region-Per-VPC). Additionally, if an external peer advertises more than 5,000 prefixes, Cloud Router closes the BGP session with a CEASE/MAX_PREFIXES_REACHED notification.
The observed telemetry directly contradicts a route quota or prefix-limit failure:
routeStatus: DROPPED in bestRoutesForRouter), whereas 10.50.4.0/24 is an outbound VPC spoke subnet missing from advertisedRoutes.WARNING events at 75% quota usage and ERROR entries in route_quota_events when routes are dropped. The logs here show no route_quota_events entries.Established, whereas exceeding the 5,000-prefix BGP session ceiling terminates the session until manually disabled and re-enabled.router.googleapis.com/dynamic_routes/learned_routes/used_unique_destinations and any_dropped_unique_destinations.Established.This would be the correct diagnosis if Cloud Logging reported route_quota_events errors or CEASE/MAX_PREFIXES_REACHED, and bestRoutesForRouter showed on-premises prefixes marked as routeStatus: DROPPED.
A VPC network's dynamic routing mode (regional or global) determines how Cloud Routers share subnet and learned dynamic routes across Google Cloud regions. In regional mode, Cloud Router only advertises subnets located in its own region and installs learned dynamic routes exclusively in that region. In global mode, Cloud Router advertises subnets across all regions.
Changing the dynamic routing mode does not resolve this failure for two key reasons:
10.50.4.0/24 and the us-east4 Cloud Router reside in us-east4. Even under regional dynamic routing mode, a Cloud Router advertises routes in its local region.ACTIVE in the hybrid spoke group's hub route table yet explicitly missing from advertisedRoutes on the us-east4 BGP peer, pointing to prefix-level filtering rather than regional visibility.global dynamic routing mode does not bypass an outbound BGP route policy that drops a specific CIDR block.global mode is primarily required so traffic between different regions (such as us-west1 and us-east4) or cross-region failover paths can exchange routes.This answer would be correct if 10.50.4.0/24 were deployed in a different region (such as us-west1) and failed to propagate across regions to the us-east4 Cloud Router due to regional dynamic routing mode.
While global dynamic routing mode is a best practice for multi-region Network Connectivity Center topologies and 99.99% availability designs, it does not explain why a same-region subnet present in the hub route table is excluded from a peer's advertisedRoutes.
A BGP route policy on Cloud Router provides granular, rule-based control over which routes are accepted inbound from or advertised outbound to a specific BGP peer. Within a Network Connectivity Center (NCC) architecture, hybrid spokes rely on Cloud Router BGP sessions to advertise active hub prefixes to on-premises routers.
Every piece of observed telemetry narrows the fault specifically to outbound BGP filtering on the us-east4 Cloud Router:
LINK_DOWN or CONFIG_DISABLED log entries, combined with an Established BGP state, confirms that the VLAN attachment, IKE/link layer, and BGP neighbor session are operating normally.10.50.4.0/24 as ACTIVE in the hybrid spoke group's hub route table proves that vpc-prod-a exported the subnet and NCC distributed it to the hybrid spoke.advertisedRoutes in gcloud compute routers get-status, which happens when an outbound BGP route policy matches and drops the newly added prefix before sending BGP UPDATE messages to the on-premises peer.accept or drop) on export or import.vpc-prod-a continue working because they match earlier accept terms, whereas 10.50.4.0/24 hits an explicit drop rule or a default deny.advertisedRoutes with gcloud compute routers get-status immediately reveals whether Cloud Router is withholding an otherwise active hub prefix.Unlike VPC spoke export filters (which act before the hub route table) or dynamic routing mode (which governs cross-region distribution), updating the outbound BGP route policy directly restores advertisement of 10.50.4.0/24 to spoke-east without disrupting existing traffic or tearing down the established BGP session.
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