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 connects 12 autonomous business-unit VPCs (vpc-bu-1 through vpc-bu-12) to a central routing VPC (vpc-hub) using VPC Network Peering. As the environment grows, your network architecture must meet all of the following requirements:
172.16.0.0/12) via Cloud Interconnect VLAN attachments in vpc-hub.vpc-bu-5 and vpc-bu-6 to each use an internal 100.64.0.0/16 subnet without exposing those ranges outside their respective VPCs.Which interconnection design should you implement?
exclude-export-ranges for 100.64.0.0/16 on vpc-bu-5 and vpc-bu-6, and attach the Cloud Interconnect VLAN attachments in vpc-hub (configured with global dynamic routing) as hybrid spokes.Network Connectivity Center (NCC) is a centralized orchestration framework that connects multiple VPC spokes and hybrid spokes (such as Cloud Interconnect VLAN attachments) to a central NCC hub. Unlike traditional gateway-based hubs, NCC provides a distributed data plane directly on Google's Software-Defined Network (SDN).
vpc-hub (with global dynamic routing enabled) as hybrid spokes propagates on-premises dynamic routes (172.16.0.0/12) to all VPC spokes.100.64.0.0/16): By specifying exclude-export-ranges for 100.64.0.0/16 when attaching vpc-bu-5 and vpc-bu-6, those CIDR blocks are never exported to the NCC hub route table, preventing conflicts while keeping them strictly local.Compared to full-mesh VPC Network Peering, NCC eliminates pairwise peering complexity, supports subnet export filtering to permit isolated overlapping CIDRs, and removes peering-group VM scaling constraints—all while preserving native SDN line-rate performance that HA VPN or multi-NIC virtual appliances cannot match.
vpc-hub, and configure Cloud Router custom route advertisements to transitively exchange business-unit and on-premises routes while filtering out 100.64.0.0/16.An HA VPN hub-and-spoke architecture interconnects separate VPC networks using managed IPsec VPN tunnels paired with Cloud Routers exchanging routes dynamically via Border Gateway Protocol (BGP). Using custom route advertisements on Cloud Routers allows vpc-hub to act as a transitive router between spoke VPCs and on-premises networks.
100.64.0.0/16 from BGP announcements, allowing CIDR reuse.--export-custom-routes and --import-custom-routes on all peering connections so vpc-hub transitively exchanges routes between business-unit VPCs, and configure --no-export-custom-routes on vpc-bu-5 and vpc-bu-6 to keep 100.64.0.0/16 local.In VPC Network Peering, the --export-custom-routes and --import-custom-routes flags control whether static routes (without network tags and not targeting the default internet gateway) and dynamic routes (learned via Cloud Router) are shared between two directly peered VPC networks.
vpc-hub into a transit router; peering subnet, static, and dynamic routes learned by vpc-hub from one peer cannot be re-exported to any other peer.--no-export-custom-routes: Private IPv4 subnet routes are always exported and imported across peered VPCs and cannot be disabled. Even though vpc-bu-5 and vpc-bu-6 are not directly peered with each other, both are peered with vpc-hub, creating a conflicting 100.64.0.0/16 subnet range inside vpc-hub's routing table.vpc-hub remain bound by aggregate peering-group quotas for VMs, routes, and internal forwarding rules.--no-export-custom-routes only suppresses static and dynamic custom routes, not local IPv4 subnet routes.vpc-hub, enable custom route export only on vpc-hub with global dynamic routing mode, and disable custom route exchange between business-unit VPCs.In a full-mesh VPC Network Peering design, every VPC network maintains a direct pairwise peering connection with every other VPC network in the topology. This bypasses VPC Network Peering's non-transitivity limitation by creating single-hop paths between all peers.
vpc-bu-5 and vpc-bu-6 cannot both host 100.64.0.0/16 subnets while peered in the same mesh or even while both are peered to vpc-hub.vpc-hub plus 12 business units) requires 78 bidirectional peering pairs (156 configurations) and quickly approaches per-VPC peering limits as more business units are added.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