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 Network Connectivity Center (NCC) to enable cross-region site-to-site data transfer across three external sites:
us-east4 across separate edge availability domainsus-west1 paired with an HA VPN gateway in us-west1 for redundancyeurope-west2 advertising identical prefixes via ECMPHow should you configure the VPC network and NCC hybrid spokes to satisfy all topology and high availability requirements?
This design isolates regional hybrid attachments into separate regional routing VPC networks and relies on NCC VPC spokes to interconnect those VPCs through the central NCC hub.
The organization only needed site-to-cloud connectivity (where external sites communicate exclusively with workloads inside Google Cloud VPCs without transiting between New York, AWS, and London), and the hybrid spokes did not enable site-to-site data transfer.
In a standard Cross-Cloud Network architecture, engineers use one centralized transit (routing) VPC network with global dynamic routing for all site-to-site hybrid spokes, while optionally attaching separate application or workload VPCs as VPC spokes to the same hub.
Attempting to combine a Cloud Interconnect VLAN attachment and HA VPN tunnels into a single NCC hybrid spoke tries to represent all connectivity for a single geographic endpoint as one logical spoke resource.
LinkedInterconnectAttachments and LinkedVpnTunnels. Attempting to create or update a spoke with mixed backing resource types fails validation.The AWS site in us-west1 used two redundant Cross-Cloud Interconnect VLAN attachments across separate edge availability domains instead of one VLAN attachment paired with HA VPN. In that case, both same-region VLAN attachments could be grouped into a single spoke, resulting in three hybrid spokes total.
Even when separated into two spokes in us-west1, NCC ensures each spoke uses a distinct BGP ASN on its external peers and automatically handles route propagation and ECMP or preference-based failover between the VLAN attachment spoke and the HA VPN spoke.
Network Connectivity Center (NCC) provides a centralized hub-and-spoke transit control plane that turns Google's private backbone into a wide area network (WAN) for external sites. When site-to-site data transfer is enabled, NCC automatically re-advertises dynamic BGP routes learned from any participating hybrid spoke to all other participating hybrid spokes attached to the same hub.
global allows Cloud Routers in us-east4, us-west1, and europe-west2 to exchange learned prefixes across regions.us-east4 Dedicated Interconnect VLAN attachments reside in the same region and connect to the same site, so they belong in a single VLAN attachment spoke. Conversely, the us-west1 Cross-Cloud Interconnect VLAN attachment and the us-west1 HA VPN tunnels use different resource types and must be placed in two separate hybrid spokes.europe-west2 Router appliance VMs reside in the same region and advertise identical prefixes with equal MEDs, so they operate in a single Router appliance spoke.Respecting NCC's strict spoke boundaries—one resource type per spoke, one region per VLAN or Router appliance spoke, and a single global-routing VPC in the hub project—prevents spoke creation errors and guarantees resilient cross-region data plane forwarding.
This approach attempts to consolidate all Cloud Interconnect VLAN attachments across multiple regions into one logical spoke while relying on Cloud Router custom learned routes to control prefix propagation between external locations.
us-east4 and us-west1 must be configured as separate spokes.us-east4 and us-west1 into one spoke violates NCC's regional spoke model and fails validation.No valid NCC configuration supports combining cross-region VLAN attachments into a single spoke or propagating Cloud Router custom learned routes across site-to-site data transfer spokes.
To influence path selection or restrict which dynamic routes are shared across sites in NCC, administrators must use BGP MED attributes, spoke export/import filters (--include-import-ranges / --exclude-import-ranges), or BGP route policies rather than Cloud Router custom learned routes.
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