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 connecting 60 workload VPC networks across multiple projects to two regional on-premises data centers (us-west1 and us-east1) using Dedicated Interconnect VLAN attachments in a dedicated routing VPC network. To simplify routing management, you deploy a Network Connectivity Center (NCC) hub in mesh topology with the workload VPCs as VPC spokes and the VLAN attachments as hybrid spokes.
Your architecture has the following requirements and observations:
us-central1.10.10.0.0/16 and 10.20.0.0/16).us-central1 workload subnets lack routes to on-premises prefixes.Which configuration changes should you implement to resolve these issues and meet all requirements?
An NCC star topology segments a hub into two separate routing domains—a center group and an edge group—to restrict east-west traffic between edge spokes, while static routes manually define next hops inside a single VPC network's routing table.
East-west communication between the 60 workload VPCs were strictly prohibited by security policy and you were deploying a brand-new hub from scratch using star topology with custom route advertisements on the center-group hybrid Cloud Routers.
Combining global dynamic routing on the routing VPC network with Cloud Router custom route advertisements and BGP Multi-Exit Discriminator (MED) tuning establishes full multi-region hybrid reachability across all Network Connectivity Center (NCC) spokes while minimizing BGP routing table overhead on external edge routers.
us-central1: The dynamic routing mode of the routing VPC network determines where NCC dynamic routes are programmed in workload VPC spokes. Switching the routing VPC from regional to global dynamic routing propagates learned on-premises prefixes from us-west1 and us-east1 hybrid spokes to every region of every attached VPC spoke, including us-central1.ALL_IPV4_RANGES (which exports every individual subnet route), configuring Cloud Router custom route advertisements to announce only the aggregated regional supernets (10.10.0.0/16 and 10.20.0.0/16) respects the edge routers' prefix limits.100) and remote-region prefixes with a higher MED (such as 200) ensures traffic uses the closest local Interconnect while failing over automatically across regions.N*(N-1)/2 VPC peering meshes.Unlike exporting all individual subnet routes via import filters or deploying separate VLAN attachments per VPC, this approach delivers scalable multi-VPC connectivity, protects constrained on-premises routing tables through BGP summarization, and satisfies NCC's strict requirement for legacy best path selection on hybrid spokes.
Standard best path selection mode changes how Cloud Router evaluates BGP attributes like AS-path length across regions, site-to-site data transfer turns Google Cloud into a transit WAN between external sites, and custom learned routes manually inject or override prefixes learned from external BGP peers inside a Cloud Router.
us-central1 routes.No valid NCC hybrid spoke scenario supports standard best path selection mode or uses custom learned routes to advertise VPC spoke subnets outbound; outbound summarization always requires custom route advertisements in legacy mode.
ALL_IPV4_RANGES, change the dynamic routing mode of all 60 workload VPC networks to global, and leave the routing VPC network in regional dynamic routing mode.Setting includeImportRanges to ALL_IPV4_RANGES instructs Cloud Router sessions in NCC hybrid spokes to automatically re-advertise every individual IPv4 subnet route present in the NCC hub route table to on-premises BGP peers, while changing dynamic routing on workload VPCs alters only local Cloud Router behavior within those VPCs.
ALL_IPV4_RANGES advertises every individual subnet from all 60 workload VPCs directly to the on-premises edge routers rather than summarizing them into the contiguous 10.10.0.0/16 and 10.20.0.0/16 blocks, risking BGP table exhaustion or dropped routes.us-central1 connectivity: The dynamic routing mode of workload VPC networks has no effect on how NCC dynamic routes are programmed across regions. Because the routing VPC network hosts the Cloud Routers managing the Interconnect BGP sessions, leaving it in regional mode restricts hybrid routes exclusively to us-west1 and us-east1.ALL_IPV4_RANGES dynamically tracks subnet additions and deletions across spokes without manual Cloud Router updates, but provides no prefix aggregation.On-premises routers had ample BGP route capacity to accept every individual workload subnet prefix without summarization, and global dynamic routing were enabled on the routing VPC network rather than on the workload VPC networks.
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