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.
You are architecting a global hybrid network using multi-NIC SD-WAN Network Virtual Appliances (NVAs) spanning a routing VPC (nic0) and a transit VPC (nic1). Your design must satisfy these requirements:
Which configuration should you implement?
nic0 to NCC Hub 1 in star topology without site-to-site data transfer, and connect workload VPCs to the transit VPC using VPC Network Peering with custom route export enabled while advertising exact workload subnet prefixes from nic1.This design attempts to place the multi-NIC SD-WAN NVAs inside a Shared VPC service project, disables site-to-site data transfer on a star-topology Hub 1, and uses VPC Network Peering with exact subnet prefix advertisements instead of an NCC Hub 2 star topology with a summarized supernet.
nic1. Because VPC Network Peering is non-transitive, peered workload VPCs cannot transit the transit VPC dynamically without explicit custom supernet routing or NCC star-topology orchestration.nic1 so workload spokes route inter-VPC traffic toward the NVA instead of relying on non-transitive peering.The NVAs were deployed in the Shared VPC host project, site-to-site data transfer was enabled on a mesh Hub 1 for branch-to-branch traffic, and workload VPCs connected via an NCC Hub 2 star topology receiving an aggregated supernet route from nic1.
nic0, nic1, and all workload VPCs to a single NCC hub configured in mesh topology with site-to-site data transfer enabled, and enable BGP Bidirectional Forwarding Detection (BFD) on all Router Appliance BGP sessions for sub-second failover.This configuration places every hybrid connection, both NVA network interfaces, and all workload VPCs into a single NCC hub using a mesh topology, while attempting to accelerate BGP failure detection using Bidirectional Forwarding Detection (BFD) on Router Appliance sessions.
nic0 (routing VPC) and nic1 (transit VPC) to the same mesh hub merges the untrusted and trusted routing domains, undermining multi-NIC security segmentation and risking routing loops.The organization wanted unrestricted any-to-any connectivity among workload VPCs without inline NVA inspection, used Cloud NGFW directly at the VPC boundary instead of NVAs, and deployed BFD solely on supported Cloud Interconnect VLAN attachment BGP sessions rather than Router Appliance spokes.
nic0 to NCC Hub 1 (mesh topology, site-to-site data transfer enabled), and connect nic1 (center group) and workload VPCs (edge group) to NCC Hub 2 (star topology). Peer each NVA interface with both interfaces of its regional Cloud Router, set distinct BGP MEDs (10 and 20) per regional NVA, and advertise an aggregated supernet route for workload VPCs from nic1.This design combines Network Connectivity Center (NCC), multi-NIC SD-WAN Network Virtual Appliances (NVAs), and global dynamic routing to separate external hybrid routing from internal workload inspection while guaranteeing regional affinity and cross-regional failover.
nic0 Router Appliance spokes in the routing VPC. This allows branch offices to exchange traffic over Google's backbone and reach the NVAs.nic1 Router Appliance spokes in the center group and workload VPCs in the edge group. Edge spokes cannot communicate directly with one another; instead, advertising an aggregated supernet route from nic1 forces all inter-VPC traffic through the NVAs.10 for the primary NVA and 20 for the secondary NVA) ensures a single active NVA per region handles both directions of a stateful flow. Enabling global dynamic routing on both VPCs allows regional Cloud Routers to automatically reroute traffic to healthy NVAs in the secondary region if all NVAs in a region fail, while peering with both Cloud Router interfaces provides zonal redundancy.nic0) from trusted internal transit (nic1).Unlike a single mesh hub, this dual-hub design prevents workload VPCs from bypassing centralized inspection while preserving full site-to-site transit and deterministic regional failover.
nic0 to NCC Hub 1 (mesh topology), and attach nic1 (center group) and workload VPCs (edge group) to NCC Hub 2 (star topology). Configure identical BGP MED values on both NVAs for ECMP load balancing, and enforce micro-segmentation across NCC spokes using IAM-governed Tags in Cloud NGFW rules.This approach separates the routing and transit domains across two NCC hubs, but restricts all NVAs to a single region with regional dynamic routing, uses identical BGP MEDs for Equal-Cost Multipath (ECMP) routing, and attempts to apply IAM-governed Tags across NCC-connected networks.
The architecture only required single-region availability, used stateless routing or NVA session synchronization for ECMP, and enforced cross-spoke Cloud NGFW policies using IP CIDR ranges instead of Tags.
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