Which two cloud providers support Load Balancers as next hop configurations for outbound connections? (Choose two.)

Question

Options

• AGoogle Cloud Platform
• BMicrosoft Azure
• COracle Cloud
• DAmazon Web Services

• A
  94% (47)
• C
  4% (2)
• D
  2% (1)

Explanation

Google Cloud Platform and Microsoft Azure both natively support configuring an internal load balancer as a next hop in custom/static routes, enabling outbound traffic to be distributed across backend appliances (such as firewalls or NVAs) transparently. GCP exposes this through its "Internal TCP/UDP Load Balancer as Next Hop" route feature, while Azure enables it via User Defined Routes (UDRs) pointing to an Internal Load Balancer frontend IP.

Oracle Cloud (C) uses different routing constructs for directing traffic through appliances and does not support a load balancer directly as a route next hop in the same manner. AWS (D) routes traffic through appliances using Gateway Load Balancer endpoints placed in route tables - not a load balancer IP as a next hop - making its architecture fundamentally different from the GCP/Azure model.

Memory tip: Think "GA = Google + Azure" - the two providers whose names begin with letters in "GA" are the ones supporting this feature. If you remember that AWS takes the Gateway Load Balancer endpoint approach instead, you can eliminate D by recalling that AWS does it differently.

No community discussion yet for this question.