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 is deploying a Network Connectivity Center (NCC) hub with the default mesh topology in hub-project to connect workload VPCs in separate projects (app-vpc-1 in app-project-1 and app-vpc-2 in app-project-2) to an on-premises network via Cloud Interconnect VLAN attachments in a single routing VPC (transit-vpc, configured with global dynamic routing mode).
You must meet the following requirements:
app-vpc-1 and app-vpc-2 (both configured with regional dynamic routing mode) to communicate with each other and on-premises at full VM-to-VM bandwidth.app-vpc-1 reachable from app-vpc-2 and on-premises networks.10.200.0.0/24 subnet in app-vpc-1 from hub connectivity because app-vpc-2 uses the same 10.200.0.0/24 range and must expose it across the hub.Which configuration and operational workflow satisfies all requirements?
transit-vpc solely as a routing VPC without adding it as a VPC spoke, configure import filters on app-vpc-2 and the hybrid spokes to block 10.200.0.0/24 from app-vpc-1, enable --export-psc on the hub, and switch app-vpc-1 and app-vpc-2 to global dynamic routing mode so on-premises routes propagate across all regions.This approach attempts to keep transit-vpc strictly separated as a routing VPC for hybrid spokes while relying on VPC spoke import filters to resolve overlapping subnets and changing the workload VPCs' dynamic routing mode to control cross-region hybrid route propagation.
includeExportRanges and excludeExportRanges). A VPC spoke automatically imports all routes available in its spoke group's hub route table. Even if import filtering existed, NCC prohibits two VPC spokes from exporting conflicting or identical subnet ranges (10.200.0.0/24) into the same hub route table; the conflict must be excluded at export on app-vpc-1.app-vpc-1 and app-vpc-2 to global dynamic routing mode has no effect on how NCC programs dynamic routes learned from hybrid spokes. Only the dynamic routing mode of transit-vpc (where the Cloud Routers managing the BGP sessions reside) determines whether dynamic routes are programmed globally across all regions of the workload VPC spokes.includeImportRanges) apply exclusively to hybrid spokes.transit-vpc were also added as a VPC spoke, excludeExportRanges were applied on app-vpc-1 instead of nonexistent VPC import filters, and transit-vpc (rather than the workload VPCs) were relied upon for global dynamic routing mode.
app-vpc-1 and app-vpc-2 directly to transit-vpc using VPC Network Peering with custom route export and import enabled instead of NCC VPC spokes, advertise 10.200.0.0/24 only from app-vpc-2, and rely on peering route exchange to provide transitive inter-VPC and on-premises PSC reachability.This design replaces NCC VPC spokes with a traditional hub-and-spoke VPC Network Peering topology, connecting app-vpc-1 and app-vpc-2 individually to transit-vpc and enabling custom route exchange on the peering links.
app-vpc-1 and app-vpc-2 can each communicate with transit-vpc, workloads in app-vpc-1 cannot communicate directly with workloads in app-vpc-2 through transit-vpc, failing the inter-VPC connectivity requirement.excludeExportRanges. Because both app-vpc-1 and app-vpc-2 contain 10.200.0.0/24 subnets, peering both networks to transit-vpc creates an immediate subnet IP range conflict and fails.app-vpc-1 to app-vpc-2 or to on-premises networks connected to transit-vpc. Re-advertising PSC endpoints across peered networks requires additional proxy infrastructure or HA VPN transit links.N*(N-1)/2 peering meshes for inter-VPC communication, which quickly hits peering group quotas.Inter-VPC communication between app-vpc-1 and app-vpc-2 were not required, no overlapping subnets existed, PSC endpoints resided directly in transit-vpc, or NVA insertion between VPCs was mandated instead of NCC.
hub-project for PSC traffic while keeping transit-vpc as both a routing VPC and a VPC spoke, connect app-vpc-1 and app-vpc-2 via HA VPN hybrid spokes with BGP route policies filtering 10.200.0.0/24, and avoid cross-project VPC spoke proposals.This architecture attempts to combine multiple routing VPCs with an HA VPN mesh registered as NCC hybrid spokes, using BGP route policies over IPsec tunnels instead of native NCC VPC spokes.
transit-vpc as both a routing VPC and a VPC spoke while adding a second routing VPC is an unsupported configuration.app-vpc-1 and app-vpc-2 via HA VPN tunnels subjects inter-VPC traffic to per-tunnel throughput limits, IPsec encapsulation overhead, lower MTU, and higher latency—falling short of native VM-to-VM bandwidth provided by VPC spokes.You needed to connect a legacy private services access (VPC-peered managed services) VPC that cannot participate in NCC PSC propagation, where HA VPN is specifically used to provide transitive routing to that isolated services-access VPC.
transit-vpc as a VPC spoke alongside its hybrid spokes with --export-psc enabled on the hub and --include-import-ranges=ALL_IPV4_RANGES on the hybrid spokes, create cross-project VPC spoke proposals for app-vpc-1 (with 10.200.0.0/24 in excludeExportRanges) and app-vpc-2 for hub admin approval, and keep both workload VPCs in regional dynamic routing mode.Network Connectivity Center (NCC) VPC spokes provide a distributed SDN control plane that exchanges IPv4 and IPv6 subnet routes across up to 250 VPC networks without introducing gateway bottlenecks. When combined with NCC hybrid spokes (such as Cloud Interconnect VLAN attachments) residing in a routing VPC network, NCC enables scalable any-to-any route exchange between cloud workloads and on-premises networks.
global on transit-vpc) determines where hybrid dynamic routes are programmed across VPC spokes, workloads in all regions of app-vpc-1 and app-vpc-2 receive on-premises routes even while the workload VPCs remain in regional dynamic routing mode.--export-psc on the hub propagates PSC endpoint host routes across VPC spokes. To extend those propagated PSC endpoints to on-premises networks via hybrid spokes, the hub's single routing VPC (transit-vpc) must also be added as a VPC spoke, and the hybrid spokes must include ALL_IPV4_RANGES in includeImportRanges so Cloud Router advertises hub subnet and PSC routes over BGP.excludeExportRanges to 10.200.0.0/24 on app-vpc-1 prevents that range from being exported, allowing app-vpc-2 to advertise its 10.200.0.0/24 subnet cleanly. Because app-vpc-1 and app-vpc-2 reside in different projects from hub-project, creating them generates spoke proposals that the hub administrator must approve before connectivity activates.excludeExportRanges or includeExportRanges.spokeAdmin and groupUser) from central hub approval (hubAdmin).Unlike VPC Network Peering (which is non-transitive and lacks subnet export filtering) or Cloud VPN meshes (which suffer from tunnel throughput and MTU caps), combining NCC VPC spokes with a dual-role single routing VPC satisfies every routing, PSC propagation, bandwidth, and isolation requirement natively.
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