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 configuring Network Connectivity Center (NCC) site-to-site data transfer within a single VPC network that uses global dynamic routing mode and Cloud Router ASN 65000:
Region A via Dedicated Interconnect VLAN attachments in an NCC spoke, and has a redundant non-NCC VLAN attachment pair in an unsupported region that is closer to Region B.Region B via HA VPN tunnels in a second NCC spoke.65100, and Site A advertises 10.10.0.0/16 with a MED of 100 to both Region A and the unsupported region.Site A and Site B cannot exchange routes for transit communication over Google's backbone. Which configuration changes should you implement to enable deterministic site-to-site data transfer?
Network Connectivity Center (NCC) site-to-site data transfer uses Cloud Routers within a single global dynamic routing VPC network to dynamically learn external prefixes from one hybrid spoke and readvertise them to all other participating hybrid spokes on the same hub. Achieving deterministic transit requires both valid BGP Autonomous System Number (ASN) separation and explicit Multi-Exit Discriminator (MED) path preference.
65101 for Site A and 65102 for Site B) and updating the bgpPeers.peerAsn values on each Cloud Router, routes learned from Site A (AS_PATH: 65000 65101) are accepted by Site B's router (AS 65102). Previously, sharing 65100 caused BGP AS path loop detection on the peer routers to reject incoming routes containing their own ASN.100) toward Region A and a higher MED (20000) toward the unsupported region ensures that all Cloud Routers—including the Cloud Router in Region B—select the Region A NCC spoke as the optimal path for 10.10.0.0/16, overriding the closer geographic proximity of the unsupported region.10.10.0.0/16 originates from an NCC-enabled spoke (Region A), the Cloud Router in Region B readvertises the prefix across the HA VPN tunnels to Site B.Region A fails.65000).Unlike disabling loop detection, injecting static custom learned routes, or splitting VPCs, aligning unique per-spoke peer ASNs with MED-based route prioritization directly satisfies BGP and NCC transit rules without sacrificing redundancy or routing stability.
This approach attempts to bypass the shared-ASN conflict by disabling BGP AS path loop detection on the external routers and manually injecting 10.10.0.0/16 via Cloud Router custom learned routes on the Region B Cloud Router.
10.10.0.0/16 as a custom learned route will not propagate Site A's prefix to Site B.65100 on both spokes violates spoke isolation requirements and introduces severe routing instability if any intermediate device inspects AS_PATH.100 on both Site A paths means the Region B Cloud Router still selects the geographically closer unsupported region as its best path, preventing NCC transit readvertisement.allowas-in without strict route filtering) exposes multi-homed sites to persistent Layer 3 routing loops.Cloud Router custom learned routes would only be appropriate for influencing internal VPC routing toward a specific non-NCC BGP peer when the peer cannot dynamically advertise a prefix, and never as a substitute for NCC spoke route exchange.
This option proposes splitting the hybrid connectivity resources into separate VPC networks connected via NCC VPC spokes, switching Cloud Router ASNs to 16550, and advertising equal MED values (100) across Site A's Region A and unsupported-region connections.
Each part of this design conflicts with core NCC site-to-site data transfer and Cloud Router requirements:
16550): ASN 16550 is strictly reserved for Partner Interconnect VLAN attachments. Dedicated Interconnect VLAN attachments and HA VPN tunnels must use a private ASN from the RFC 6996 range (such as 64512–65534 or 4200000000–4294967294).10.10.0.0/16 with an identical MED (100) to both Region A and the closer unsupported region causes the Region B Cloud Router to break the tie by choosing the geographically closer unsupported region, which blocks NCC readvertisement.65100 on both sites still triggers AS path loop detection drops.16550) can only share a hub with other Partner Interconnect spokes, whereas Dedicated Interconnect, HA VPN, and Router appliance spokes can mix in the same hub using a shared private ASN.Using ASN 16550 would only be valid if all hybrid spokes on the hub were Partner Interconnect VLAN attachments located inside a single VPC network, alongside distinct peer ASNs and a lower MED on the NCC-supported path.
This configuration resolves the Autonomous System Number (ASN) conflict by giving Site A and Site B unique peer ASNs, which prevents BGP AS path loop detection from dropping readvertised routes. However, it reverses the Multi-Exit Discriminator (MED) values across Site A's two egress paths, instructing Google Cloud to prefer the non-NCC path in the unsupported region.
In Border Gateway Protocol (BGP) and Cloud Router route selection, a lower numeric MED value is preferred over a higher numeric MED value:
10.10.0.0/16 with MED 100 to the unsupported region and MED 20000 to Region A forces the Cloud Router in Region B to select the unsupported region's VLAN attachment as the best path to Site A.Region B will not readvertise 10.10.0.0/16 to Site B's HA VPN peer.0 is highest priority and larger numbers are lower priority.This MED assignment (100 toward the unsupported region) would only be intentional if your primary goal were to optimize site-to-cloud latency between Google Cloud VMs in Region B and Site A while accepting that site-to-site data transfer between Site A and Site B is not required.
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