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 designing a Network Connectivity Center (NCC) hub-and-spoke architecture. Two regional on-premises sites connect via Cloud Interconnect VLAN attachments in a global-routing transit-vpc with site-to-site data transfer enabled. You must integrate shared-vpc (10.20.0.0/16), bu1-vpc (10.10.0.0/16 and 10.11.0.0/24), and bu2-vpc (10.30.0.0/16) under these constraints:
bu1-vpc and bu2-vpc, while allowing both to reach shared-vpc and on-premises.10.11.0.0/24 from reaching shared-vpc or on-premises.shared-vpc to reach 10.30.0.0/16, but prevent on-premises routers from learning 10.30.0.0/16.Which NCC topology, spoke placement, and route filter configuration should you implement?
shared-vpc in the center spoke group, and place bu1-vpc, bu2-vpc, and the VLAN attachment hybrid spokes in the edge spoke group. Configure an export filter on bu1-vpc to exclude 10.11.0.0/24, and configure import filters on the hybrid spokes to exclude 10.30.0.0/16.This approach attempts to use the NCC star topology and spoke filters, but places the Cloud Interconnect VLAN attachment hybrid spokes (which have site-to-site data transfer enabled) into the edge spoke group alongside bu1-vpc and bu2-vpc.
center spoke group. Attempting to place them in the edge spoke group is unsupported.edge-to-hybrid connectivity: The edge spoke group route table only permits routes toward spokes in the center group and explicitly prohibits routes between different spokes within the edge group. Consequently, bu1-vpc and bu2-vpc would be unable to reach the on-premises networks if both were placed in the edge group.edge placement, edge-to-edge isolation would prevent the two regional hybrid spokes from exchanging transit dynamic routes with each other.edge group behavior: Spokes in the edge group only propagate their routes to the center route table and only learn routes belonging to center spokes.edge spoke group.excludeImportRanges on a hybrid spoke, you must also ensure includeImportRanges is set (such as ALL_IPV4_RANGES) so desired hub routes are wholly contained in an include range.The hybrid spokes were moved into the center spoke group alongside shared-vpc, and includeImportRanges was explicitly configured to ALL_IPV4_RANGES alongside excludeImportRanges for 10.30.0.0/16.
shared-vpc and the VLAN attachment hybrid spokes in the center spoke group, and place bu1-vpc and bu2-vpc in the edge spoke group. Configure an import filter on shared-vpc to exclude 10.11.0.0/24, and configure an export filter on bu2-vpc to exclude 10.30.0.0/16.This configuration correctly selects the NCC star topology and assigns spokes to the proper center and edge groups, but attempts to apply an import filter to a VPC spoke (shared-vpc) and an export filter to bu2-vpc.
includeExportRanges and excludeExportRanges). A VPC spoke automatically imports all routes present in its spoke group's hub route table, so you cannot configure an import filter on shared-vpc to drop 10.11.0.0/24.10.11.0.0/24 from on-premises: Even if an import filter existed on shared-vpc, bu1-vpc would still export 10.11.0.0/24 into the center route table, allowing the hybrid spokes to import and advertise it to on-premises.shared-vpc access to bu2-vpc: Applying an export filter on bu2-vpc to exclude 10.30.0.0/16 removes 10.30.0.0/16 from the center hub route table completely. While this prevents on-premises from learning 10.30.0.0/16, it also prevents shared-vpc from reaching bu2-vpc.The 10.11.0.0/24 exclusion was placed as an export filter on bu1-vpc, bu2-vpc exported 10.30.0.0/16 normally to the center route table, and the hybrid spokes used import filters (includeImportRanges with ALL_IPV4_RANGES and excludeImportRanges with 10.30.0.0/16) to prevent BGP advertisement to on-premises.
bu1-vpc in prod, bu2-vpc in non-prod, shared-vpc in services, and the VLAN attachment hybrid spokes in gateways. Configure export filters on bu1-vpc and bu2-vpc to exclude 10.11.0.0/24 and 10.30.0.0/16, respectively.The NCC hybrid inspection topology provides four preset spoke groups—prod, non-prod, services, and gateways—designed to isolate production from non-production workloads while steering traffic through third-party Security Service Edge (SSE) inspection checkpoints.
gateways group: The gateways spoke group exclusively supports NCC Gateway spokes (which integrate with Secure Access Connect attachments for SSE packet inspection). Standard Cloud Interconnect VLAN attachment hybrid spokes cannot be placed in the gateways group; they must be placed in prod, non-prod, or services.shared-vpc connectivity to bu2-vpc: Configuring an export filter on bu2-vpc to exclude 10.30.0.0/16 suppresses the subnet from the hub entirely, blocking both on-premises and shared-vpc (in services) from reaching bu2-vpc.services, relying on bu2-vpc export filters rather than hybrid spoke import filters cannot selectively allow shared-vpc access while denying on-premises route advertisement.prod and non-prod are mutually isolated, while services and gateways can communicate with all groups.gateways group, not traffic routed through standard hybrid spokes.The architecture specifically required third-party SSE packet inspection via NCC Gateway spokes in the gateways group, and bu2-vpc allowed 10.30.0.0/16 export while gateway or hybrid import/advertisement controls filtered routes to on-premises.
shared-vpc and the VLAN attachment hybrid spokes in the center spoke group, and place bu1-vpc and bu2-vpc in the edge spoke group. Configure an export filter on bu1-vpc to exclude 10.11.0.0/24, and configure import filters on the hybrid spokes with includeImportRanges set to ALL_IPV4_RANGES and excludeImportRanges set to 10.30.0.0/16.The NCC star topology creates two separate routing domains—a center spoke group and an edge spoke group—each with its own managed hub route table. Pairing this topology with VPC spoke export filters and hybrid spoke import filters provides granular control over which subnet routes enter the hub and which routes are re-advertised over BGP to external networks.
bu1-vpc and bu2-vpc in the edge spoke group guarantees routing isolation between them, because NCC prohibits routes in the edge route table that provide connectivity between different edge spokes.shared-vpc and the Cloud Interconnect VLAN attachment hybrid spokes in the center spoke group allows full communication between center spokes and all edge spokes, while satisfying the mandatory rule that hybrid spokes with site-to-site data transfer enabled must reside in the center group.10.11.0.0/24: Applying an exclude export filter (excludeExportRanges) on bu1-vpc prevents 10.11.0.0/24 from ever being propagated to the center hub route table, making it unreachable from both shared-vpc and on-premises.10.30.0.0/16: Because bu2-vpc exports 10.30.0.0/16 to the center route table, shared-vpc imports and reaches it normally. Meanwhile, configuring the hybrid spokes with includeImportRanges set to ALL_IPV4_RANGES and excludeImportRanges set to 10.30.0.0/16 ensures the hybrid spokes import 10.10.0.0/16, 10.20.0.0/16, and transit dynamic routes between on-premises sites, while blocking 10.30.0.0/16 from BGP re-advertisement.ALL_IPV4_RANGES with a targeted exclusion preserves transit dynamic route exchange across regional on-premises sites.transit-vpc uses global dynamic routing mode, cross-region site-to-site traffic and dynamic route programming work across all regions.Unlike mesh topology or firewall-only isolation, the star topology natively enforces edge-to-edge isolation in the hub route tables, and combining VPC export filters with hybrid import filters selectively shapes BGP announcements without breaking shared-vpc connectivity.
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