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.
You are managing a hybrid network in Google Cloud using Network Connectivity Center (NCC) to connect two workload VPC networks (vpc-app-a in us-central1 and vpc-app-b in us-east1) to an on-premises data center through a centralized routing-vpc in the hub project. You have verified the following configuration and diagnostic findings:
vpc-app-a and vpc-app-b are attached as VPC spokes, while two Partner Interconnect VLAN attachments in us-east1 (in separate edge availability domains) are attached as a hybrid spoke.routing-vpc uses global dynamic routing mode, and its Cloud Routers use legacy best path selection without BGP route policies.What should you do to resolve the missing route advertisements and validate end-to-end connectivity?
VPC spoke export filters (--include-export-ranges and --exclude-export-ranges) define which local subnet ranges a VPC spoke advertises into the NCC hub route table. Meanwhile, a VPC network's dynamic routing mode (regional or global) determines how Cloud Routers residing inside that VPC program and advertise dynamic routes.
vpc-app-a and vpc-app-b) do not host the Cloud Routers or VLAN attachments for hybrid connectivity. Only the dynamic routing mode of routing-vpc determines how hybrid dynamic routes are programmed across regions in the workload VPC spokes.vpc-app-a and vpc-app-b, proving that both VPC spokes are successfully exporting their subnets to the hub.routing-vpc.--include-import-ranges) or Cloud Router custom advertisements to re-advertise hub routes externally.The workload VPC subnets were missing from the NCC hub route table because overly restrictive --include-export-ranges or --exclude-export-ranges filters on vpc-app-a or vpc-app-b were blocking them from entering the hub.
VPC Network Peering establishes direct Layer 3 connectivity between two VPC networks, allowing custom route exchange when explicitly configured on both sides of the peering relationship. Network Topology is a Network Intelligence Center visualization tool that displays network entities (such as VPCs, Cloud Interconnect connections, and VLAN attachments) alongside traffic and packet-loss metrics.
You were migrating away from NCC VPC spokes to a VPC Network Peering hub-and-spoke design (for instance, to insert third-party network virtual appliances without NCC) after first deleting the VPC spokes from the NCC hub.
In Network Connectivity Center (NCC), hybrid spoke import filters (includeImportRanges) control which routes from the NCC hub route table are imported by a hybrid spoke and re-advertised over its Cloud Router BGP sessions. By default, a hybrid spoke does not automatically import and re-advertise subnet routes learned from VPC spokes unless explicitly configured to do so.
--include-import-ranges=ALL_IPV4_RANGES on the Partner Interconnect hybrid spoke instructs NCC to import all IPv4 subnet routes present in the hub route table (vpc-app-a and vpc-app-b) into the hybrid spoke's BGP sessions so the Cloud Routers in routing-vpc advertise them to the on-premises peers.routing-vpc already uses global dynamic routing mode and has no blocking BGP route policies, both us-central1 and us-east1 workload subnets are immediately eligible for advertisement.The diagnostic findings show that the workload VPC subnets are already in the NCC hub route table and Cloud Logging confirms healthy BGP sessions without route policy drops. Therefore, the missing link is strictly the hybrid spoke's import filter, making --include-import-ranges=ALL_IPV4_RANGES the cleanest and most scalable fix compared to manually maintaining custom route advertisements on every Cloud Router.
Site-to-site data transfer is an NCC feature that allows external networks (such as branch offices, data centers, or other clouds) connected via hybrid spokes in the same VPC to exchange BGP-learned routes with one another over Google's backbone. Attaching routing-vpc as a VPC spoke adds routing-vpc's own local subnets to the hub route table.
--site-to-site-data-transfer instructs Cloud Routers to re-advertise dynamic routes learned from other hybrid spokes—it does not cause a hybrid spoke to import and advertise VPC spoke subnet routes to an on-premises network.routing-vpc do not require routing-vpc itself to be added as a VPC spoke for route exchange between workload VPC spokes and on-premises networks.--include-import-ranges=ALL_IPV4_RANGES (or configuring custom route advertisements on the Cloud Routers), the hybrid spoke still will not re-advertise the workload VPC subnets.routing-vpc must be a VPC spoke: Adding routing-vpc as a VPC spoke is only required when enabling Private Service Connect connection propagation with hybrid spokes, or when workloads inside routing-vpc subnets must communicate directly with workload VPCs.You were connecting two separate on-premises data centers (for example, via Partner Interconnect and HA VPN hybrid spokes in routing-vpc) so they could route traffic to each other across Google's backbone, or needed Private Service Connect propagation into routing-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