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 configured with a mesh topology to interconnect two workload VPC spokes and two VLAN attachment hybrid spokes. Both hybrid spokes reside in the same routing-vpc network with global dynamic routing and site-to-site data transfer enabled, and Cloud Router subnet route advertisement is configured.
The current IP allocation and BGP advertisements are:
vpc-prod: Subnets 10.10.0.0/20, 10.10.16.0/20, and an isolated legacy subnet 10.20.0.0/16vpc-shared: Subnets 10.20.10.0/24 and 10.30.0.0/16hybrid-dc1: Receives BGP routes 172.16.0.0/17 (corporate servers) and 172.16.128.0/17 (local lab) from Data Center 1hybrid-dc2: Connects to Data Center 2, which uses 172.16.128.0/17 locally for its own labYou must satisfy these routing requirements:
10.10.0.0/20 and 10.10.16.0/20 from vpc-prod and all subnets from vpc-shared.172.16.0.0/17 from hybrid-dc1 to the hub while preventing 172.16.128.0/17 from being exported.hybrid-dc2 imports and re-advertises 172.16.0.0/17, 10.10.0.0/20, 10.20.10.0/24, and 10.30.0.0/16, while excluding 10.10.16.0/20.Which NCC spoke filter configuration meets all requirements?
This configuration tries to explicitly exclude 10.20.0.0/16 on vpc-prod alongside a specific /19 include list, while relying on default hybrid import behavior on hybrid-dc2 and adding an exclusion for 10.10.16.0/20.
vpc-prod, --include-export-ranges is restricted to 10.10.0.0/19, which does not contain 10.20.0.0/16. NCC requires that every CIDR in --exclude-export-ranges be fully contained within the CIDRs or keywords in --include-export-ranges. Because 10.20.0.0/16 is outside 10.10.0.0/19, Google Cloud rejects this configuration.hybrid-dc2: When a hybrid spoke has site-to-site data transfer enabled and --include-import-ranges is omitted, NCC defaults to importing only transit dynamic routes learned from other hybrid spokes (172.16.0.0/17). It does not import any VPC spoke subnet routes (10.10.0.0/20, 10.20.10.0/24, or 10.30.0.0/16), breaking connectivity between Data Center 2 and Google Cloud workloads.--include-import-ranges defaults only to transit dynamic routes and not ALL_IPV4_RANGES, 10.10.16.0/20 is not contained within the effective include import set.--include-import-ranges produces different defaults depending on whether site-to-site data transfer is enabled, and never includes VPC spoke subnets automatically.vpc-prod omitted --include-export-ranges (defaulting to ALL_PRIVATE_IPV4_RANGES, which contains 10.20.0.0/16) and hybrid-dc2 explicitly set --include-import-ranges=ALL_IPV4_RANGES.
This configuration applies CIDR aggregation, export prefix filtering, and explicit hybrid import filtering across VPC and hybrid spokes in Network Connectivity Center (NCC). By defining exact containment boundaries on each spoke, it prevents overlapping subnet collisions in the hub route table and establishes deterministic route propagation across on-premises and cloud networks.
vpc-prod, the aggregated prefix 10.10.0.0/19 encompasses both 10.10.0.0/20 (10.10.0.0–10.10.15.255) and 10.10.16.0/20 (10.10.16.0–10.10.31.255). Both subnets are wholly contained within 10.10.0.0/19 and are exported to the hub. Because 10.20.0.0/16 falls outside 10.10.0.0/19, it is withheld from the hub, eliminating any overlap with vpc-shared's 10.20.10.0/24 subnet when vpc-shared uses the default ALL_PRIVATE_IPV4_RANGES.hybrid-dc1, setting --include-export-ranges=172.16.0.0/16 and --exclude-export-ranges=172.16.128.0/17 satisfies the requirement that every excluded CIDR must be fully contained within an included CIDR. The 172.16.0.0/17 route is wholly contained in 172.16.0.0/16 and does not intersect 172.16.128.0/17, so it is exported; 172.16.128.0/17 matches the exclude list and is blocked.hybrid-dc2, explicitly specifying ALL_IPV4_RANGES in --include-import-ranges ensures the spoke imports both VPC spoke subnet routes and transit dynamic routes (172.16.0.0/17) from the hub, while --exclude-import-ranges=10.10.16.0/20 blocks only 10.10.16.0/20./20 subnets into a single /19 preserve scarce export filter slots (up to 16 CIDRs per VPC spoke).Unlike relying on default hybrid import behavior—which omits VPC spoke subnets when site-to-site data transfer is enabled—or attempting partial subnet exclusions that Google Cloud blocks, this design adheres strictly to NCC validation rules and minimizes filter list complexity.
This option attempts to block the conflicting subnet using a narrower exclude prefix on vpc-prod, apply an import filter on vpc-shared, and specify both a summary and more-specific prefix in hybrid-dc1's include export list.
vpc-prod, omitting --include-export-ranges defaults to ALL_PRIVATE_IPV4_RANGES, which wholly contains subnet 10.20.0.0/16. However, setting --exclude-export-ranges=10.20.0.0/17 causes the subnet 10.20.0.0/16 to intersect with, without being wholly contained by, the exclude range. Google Cloud actively prevents creating an exclude export range or subnet in this intersecting state.--exclude-import-ranges=10.20.0.0/16 on vpc-shared is invalid because VPC spokes do not support import filters. Only hybrid spokes support includeImportRanges and excludeImportRanges.hybrid-dc1, listing both 172.16.0.0/16 and 172.16.0.0/17 in --include-export-ranges violates the NCC rule that no CIDR in an include export list can match or contain another CIDR in the same list.vpc-prod excluded the entire 10.20.0.0/16 subnet, vpc-shared omitted import filters altogether, and hybrid-dc1 used a single non-overlapping CIDR (172.16.0.0/16) in --include-export-ranges.
This option uses explicit include lists without exclude filters by specifying /21 prefixes on vpc-prod, a /18 prefix on hybrid-dc1, and explicit VPC subnet CIDRs on hybrid-dc2.
vpc-prod, the subnets 10.10.0.0/20 and 10.10.16.0/20 are larger than /21 (10.10.0.0/21 and 10.10.16.0/21). Because each subnet intersects with—but is not wholly contained in—the /21 include export ranges, Google Cloud rejects the filter configuration.hybrid-dc1, Data Center 1 advertises 172.16.0.0/17. With --include-export-ranges=172.16.0.0/18, the dynamic route 172.16.0.0/17 intersects with 172.16.0.0/18 without being wholly contained in it. Under hybrid spoke export rules, intersecting routes that are not wholly contained are not sent to the hub, breaking reachability to Data Center 1's corporate servers.hybrid-dc2: Listing only VPC spoke subnets (10.10.0.0/20, 10.20.10.0/24, 10.30.0.0/16) in hybrid-dc2's --include-import-ranges causes 172.16.0.0/17 to be omitted from import, preventing site-to-site transit communication between Data Center 1 and Data Center 2.ALL_IPV4_RANGES with explicit import CIDRs, both VPC subnets and hybrid transit prefixes must be included.vpc-prod used --include-export-ranges=10.10.0.0/19, hybrid-dc1 used --include-export-ranges=172.16.0.0/17, and hybrid-dc2 added 172.16.0.0/17 to its --include-import-ranges 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