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 designing an active-active high-availability topology for stateful multi-NIC Network Virtual Appliances (NVAs) in us-west1 to inspect bidirectional traffic between two workload environments (env-a and env-b). Your design must meet the following requirements:
--can-ip-forward enabled) must actively process traffic.Which network topology and internal passthrough Network Load Balancer configuration should you implement?
This topology attempts to place two subnets (subnet-a and subnet-b) inside a single VPC network (vpc-shared), attach two network interfaces of each NVA to different subnets of that same VPC, and use custom static routes to steer intra-VPC traffic through two internal passthrough Network Load Balancers (ilb-a and ilb-b).
subnet-a or subnet-b) is rejected with an invalid destination range error.The two environments were isolated into separate VPC networks (vpc-a and vpc-b) rather than subnets within vpc-shared, allowing nic0 and nic1 to reside in distinct VPCs and enabling each VPC's static route to target the remote VPC's CIDR without conflicting with local subnet routes.
A common misconception is treating Google Cloud VPCs like traditional on-premises VLANs where a firewall sits between two subnets in the same routing domain. In Google Cloud, network segmentation for NVA inspection requires VPC-level separation rather than subnet-level separation.
This topology separates nic0 and nic1 into vpc-a and vpc-b, divides the NVAs into two independent unmanaged instance groups behind two internal passthrough Network Load Balancers per VPC, and defines equal-priority static routes in each VPC pointing to both local load balancers in an attempt to achieve equal-cost multipath (ECMP) distribution.
vpc-a and vpc-b. Forward traffic might route through ilb-a1 (hitting the first group) while return traffic routes through ilb-b2 (hitting the second group), breaking stateful inspection without SNAT.next-hop-instance routes or VPN tunnels, multiple routes differing only in their next-hop internal load balancer never load-share traffic.All NVA instances were placed into a single regional managed instance group serving as the backend for one internal passthrough Network Load Balancer in vpc-a (ilb-a) and one in vpc-b (ilb-b), relying on symmetric hashing (CLIENT_IP_PORT_PROTO) and a single static route per VPC to distribute traffic active-active across all NVAs.
This configuration separates the NVA interfaces into distinct VPC networks (vpc-a and vpc-b) and pairs them with two internal passthrough Network Load Balancers (ilb-a and ilb-b), but configures the forwarding rules with --purpose=SHARED_LOADBALANCER_VIP and sets the backend services' session affinity to CLIENT_IP_NO_DESTINATION.
CLIENT_IP_NO_DESTINATION hashes solely on the client source IP and omits destination IP information, ilb-a and ilb-b will often hash forward and return packets to different NVA instances, causing stateful firewalls to drop return traffic.--purpose=SHARED_LOADBALANCER_VIP are mutually exclusive features. Traffic sent to a static route whose next hop is a shared-VIP forwarding rule is silently dropped.CLIENT_IP, CLIENT_IP_PROTO, and CLIENT_IP_PORT_PROTO because each incorporates destination IP information into the hash calculation.PER_CONNECTION or PER_SESSION), idle timeout, and health check state.The forwarding rules used unique internal IP addresses (without --purpose=SHARED_LOADBALANCER_VIP) and both backend services were configured with CLIENT_IP, CLIENT_IP_PROTO, or CLIENT_IP_PORT_PROTO session affinity along with matching connection tracking and health check settings.
Although --purpose=SHARED_LOADBALANCER_VIP is useful when sharing a single internal IP across multiple forwarding rules for mixed TCP/UDP application services, next-hop routing cannot resolve multiple backend services behind a shared VIP and explicitly prohibits it.
Deploying multi-NIC Network Virtual Appliances (NVAs) across separate VPC networks with an internal passthrough Network Load Balancer acting as a static route next hop in each VPC enables active-active, bump-in-the-wire traffic inspection. Because each NVA has nic0 attached to vpc-a and nic1 attached to vpc-b, traffic leaving vpc-a is steered to ilb-a (which delivers packets to nic0), inspected by the NVA, and forwarded out nic1 into vpc-b—and vice versa for return traffic.
CLIENT_IP_PORT_PROTO (or CLIENT_IP / CLIENT_IP_PROTO, but never CLIENT_IP_NO_DESTINATION), configuring identical health checks, and using the same connection tracking mode (PER_CONNECTION or PER_SESSION) on both ilb-a and ilb-b guarantees both load balancers select the same eligible NVA backend without requiring SNAT.--can-ip-forward enabled ensures all healthy instances across zones actively process traffic, while health checks automatically remove failed appliances from the eligible backend pool.env-a and env-b into distinct VPC networks (vpc-a and vpc-b) allows static routes for the remote VPC CIDR to take effect without conflicting with local subnet routes.us-west1 without complex overlay tunnels.This design satisfies active-active throughput, preserves client IP visibility without SNAT, and enforces strict stateful flow symmetry across both load balancers—unlike single-VPC topologies (which cannot override subnet routes), CLIENT_IP_NO_DESTINATION configurations (which break symmetric hashing), or multi-ILB ECMP routes (which are unsupported).
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