Exam Professional Cloud Network Engineer topic 1 question 134 discussion

D is the correct. Use an internal TCP/UDP load balancer as the next hop. https://cloud.google.com/architecture/architecture-centralized-network-appliances-on-google-cloud#choosing_a_high_availability_option

https://cloud.google.com/load-balancing/docs/internal/setting-up-ilb-next-hop

the traffic is from VPC to on-prem which is internal flow, therefore if we apply Google's best practice, it should be TCP/UDP lb. Yes, NLB can direct traffic to 2 NVAs but its not the ideal choice for this scenario since NLB is best use for external load balancing.

https://cloud.google.com/load-balancing/docs/passthrough-network-load-balancer#next-hops Answer is C

https://cloud.google.com/architecture/architecture-centralized-network-appliances-on-google-cloud#choosing_a_high_availability_option

Answer is C Network Load balancer https://cloud.google.com/architecture/architecture-centralized-network-appliances-on-google-cloud#choosing_a_high_availability_option Use an internal passthrough Network Load Balancer as the next hop. In this approach, you place multiple virtual appliances in a managed instance group behind an internal passthrough Network Load Balancer. This load balancer is used as the next hop for a default route that replaces the default route in the VPC networks connected to the appliances. You can use appliances either in an active/active configuration, which is the standard configuration, or in an active/passive configuration, by employing failover for internal passthrough Network Load Balancers. Health checks direct traffic to healthy instances.

I suspect that the name Load Balancer in this question refers to the one before the change. In that case, Network Load Balancer specifically indicates Reagional External TCP/UDP Network Load Balancer. Sorry for the Japanese, but here are the documents. https://blog.g-gen.co.jp/entry/external-https-load-balancing-explained

https://cloud.google.com/architecture/architecture-centralized-network-appliances-on-google-cloud#choosing_a_high_availability_option

TCP LB as next hop.

Actually, from the documentation https://cloud.google.com/architecture/architecture-centralized-network-appliances-on-google-cloud#choosing_a_high_availability_option It seems to be C. "Use an internal passthrough Network Load Balancer as the next hop. In this approach, you place multiple virtual appliances in a managed instance group behind an internal passthrough Network Load Balancer. This load balancer is used as the next hop for a default route that replaces the default route in the VPC networks connected to the appliances."

D is correct

• D. Configure an internal TCP/UDP ******* load balancer with the two network virtual appliances as backends. Configure a route for 10.0.0.0/8 with the internal load balancer as the next hop.

D. Configure an internal TCP/UDP load balancer with the two network virtual appliances as backends. Configure a route for 10.0.0.0/8 with the internal load balancer as the next hop

it's D.

I also vote for D

In my opinion is C, I did this setup on azure cloud, but honestly never make this setup in GCP. LB layer 7 don't work here. we need NLB