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 with two workload VPC spokes (vpc-a, vpc-b) and a single routing-vpc (currently set to regional dynamic routing). You deployed HA VPN gateways and regional Cloud Routers (ASN 65000) in us-east1 for Site-East (peer ASN 65001) and us-west1 for Site-West (peer ASN 65002). Each gateway reports CONNECTION_REDUNDANCY_MET with two active tunnels and ESTABLISHED BGP sessions.
You must attach these tunnels as hybrid spokes to meet these requirements:
Site-East and Site-West.vpc-a and vpc-b subnet routes to both sites without manually maintaining custom IP advertisements.Which configuration should you implement?
routing-vpc dynamic routing mode to global and update both peer gateways to use the same peer ASN (65001). Create two regional Cloud VPN spokes without --site-to-site-data-transfer, set --include-import-ranges=ALL_IPV4_RANGES on each, and attach routing-vpc as a VPC spoke to transit dynamic routes between Site-East and Site-West.This configuration enables global dynamic routing and sets --include-import-ranges=ALL_IPV4_RANGES, but it assigns the same peer ASN (65001) to both sites, omits --site-to-site-data-transfer on the VPN spokes, and adds routing-vpc as a VPC spoke to act as a transit path.
65000), different hybrid spokes must use different peer ASNs. If Site-East and Site-West both advertise prefixes with ASN 65001, AS path loop detection on each site's peer router will reject all prefix advertisements originating from the other site.--site-to-site-data-transfer enabled on the hybrid spokes, NCC does not update Cloud Router BGP sessions to re-advertise dynamic routes learned from one hybrid spoke to another.routing-vpc as a VPC spoke only exports local subnet routes inside routing-vpc (and enables Private Service Connect propagation); VPC spokes cannot export dynamic routes learned over hybrid attachments.--site-to-site-data-transfer, you cannot enable it via an update; the spoke must be deleted and recreated.Site-East and Site-West can reach vpc-a and vpc-b, but cannot communicate with each other.The two sites retained distinct peer ASNs (65001 and 65002) and both regional VPN spokes were created with --site-to-site-data-transfer enabled.
routing-vpc dynamic routing mode to global and configure both Cloud Routers to use standard best path selection mode. Create one Cloud VPN spoke in us-east1 for Site-East and one in us-west1 for Site-West with --site-to-site-data-transfer enabled, and omit --include-import-ranges so both hybrid spokes automatically import all hub subnet and transit routes.This configuration enables global dynamic routing on routing-vpc and creates properly separated regional Cloud VPN hybrid spokes with site-to-site data transfer enabled. However, it sets the Cloud Routers to the standard best path selection mode and omits the --include-import-ranges filter flag under the assumption that all NCC hub routes are imported by default.
standard mode is incompatible with NCC hybrid spoke route processing and prevents proper route exchange.--site-to-site-data-transfer is enabled and --include-import-ranges is omitted, the default import filter only includes transit dynamic routes learned from other hybrid spokes—it does not include VPC spoke subnet ranges from vpc-a or vpc-b.includeImportRanges value, non-data-transfer hybrid spokes default to an empty import list, while data-transfer hybrid spokes only import dynamic routes from other data-transfer hybrid spokes.site-to-site-data-transfer setting and linked VPN tunnels cannot be edited after spoke creation, though includeImportRanges can be updated later using gcloud network-connectivity spokes linked-vpn-tunnels update.Tunnel is up and running and CONNECTION_REDUNDANCY_MET, on-premises routers will only receive Site-East and Site-West transit prefixes unless VPC subnet ranges are explicitly included.Both Cloud Routers remained on legacy best path selection mode and --include-import-ranges=ALL_IPV4_RANGES was configured on both hybrid spokes.
routing-vpc in regional dynamic routing mode and configure Cloud Router custom learned routes on both Cloud Routers for the vpc-a and vpc-b CIDRs. Create a single Cloud VPN spoke in us-east1 that attaches all four HA VPN tunnels from both sites with --site-to-site-data-transfer enabled.This option attempts to consolidate all four HA VPN tunnels across two regions into a single regional spoke in us-east1, leaves routing-vpc in regional dynamic routing mode, and relies on Cloud Router custom learned routes to handle vpc-a and vpc-b prefixes.
us-west1 tunnels cannot be attached to a us-east1 spoke. Additionally, tunnels connecting to different external sites (Site-East and Site-West) must belong to separate spokes so each spoke has a distinct peer ASN.routing-vpc in regional dynamic routing mode prevents Cloud Routers in us-east1 and us-west1 from distributing learned dynamic routes across regions, breaking site-to-site connectivity.--include-import-ranges for importing VPC spoke subnets from the NCC hub.vpc-a or vpc-b subnets change.gcloud network-connectivity spokes describe and the NCC hub route table will fail to show end-to-end cross-region forwarding paths.Only one region was used, each site had its own spoke in its matching region, routing-vpc used global routing, and --include-import-ranges=ALL_IPV4_RANGES replaced custom learned routes.
routing-vpc dynamic routing mode to global and ensure both Cloud Routers use legacy best path selection mode. Create one Cloud VPN spoke in us-east1 (attaching both Site-East tunnels) and one in us-west1 (attaching both Site-West tunnels), enabling --site-to-site-data-transfer and setting --include-import-ranges=ALL_IPV4_RANGES on both spokes.Cloud VPN hybrid spokes attach High Availability (HA) Cloud VPN tunnels to a Network Connectivity Center (NCC) hub. By placing all tunnels for a given physical location in a dedicated regional spoke inside a shared routing-vpc, NCC integrates regional Cloud Router BGP sessions with the global NCC hub route table to support both site-to-cloud and site-to-site connectivity.
routing-vpc to global dynamic routing mode allows dynamic routes learned by us-east1 and us-west1 Cloud Routers to be distributed across regions. Enabling --site-to-site-data-transfer on both regional spokes instructs NCC to re-advertise each site's dynamic prefixes over the other site's BGP sessions using Google's backbone.Site-East (CONNECTION_REDUNDANCY_MET) into one us-east1 spoke and both tunnels for Site-West into one us-west1 spoke preserves 99.99% availability and matches distinct peer ASNs (65001 and 65002) per spoke.--include-import-ranges=ALL_IPV4_RANGES permits the hybrid spokes to import all IPv4 subnet routes from vpc-a and vpc-b in the hub route table and automatically advertise them via BGP to both on-premises routers.vpc-a or vpc-b automatically update the NCC hub route table and propagate to both sites via BGP.ESTABLISHED BGP sessions, traffic distributes evenly across tunnels.gcloud compute vpn-gateways get-status and verify propagated prefixes in the read-only NCC hub route table.This design satisfies all NCC architectural constraints—global routing, legacy path selection, per-site regional spokes, site-to-site data transfer, and explicit subnet import filtering—while preserving full HA VPN redundancy without manual custom route advertisements.
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