Google Professional Cloud Network Engineer Question 258
Single answerGoogle Cloud PlatformYou are designing a private network architecture in Google Cloud where traffic from multiple Compute Engine VM instances needs to be routed through an internal load balancer for centralized processing before being sent to other internal services. How can you implement the internal load balancer as the next hop in this scenario?
- A
Configure a custom static route with the internal load balancer's IP address as the next hop.
- B
Use the internal load balancer's forwarding rule as the next hop in a custom static route.
- C
Set up a custom static route with the internal backend service as the next hop.
- D
Configure a custom static route using the 'next hop ILB' option provided in Cloud Router.
Show answer and explanation
Correct answer: A
Explanation
To implement an internal load balancer as the next hop in a Google Cloud network, you must define a custom static route that uses the internal load balancer's IP address as the next hop. This ensures that traffic is directed through the internal load balancer, enabling centralized processing before reaching other services. Other options, such as forwarding rules or backend services, do not serve as valid next hops for routes.
- A. Correct.
This is the correct option. In Google Cloud, to set an internal load balancer as the next hop, you configure a custom static route with the internal load balancer's IP address as the next hop.
- B. Incorrect.
This is incorrect. Forwarding rules are used to direct traffic to a load balancer, but they cannot be directly set as the next hop for a route.
- C. Incorrect.
This is incorrect. The backend service is a component of the load balancer but cannot be used as a next hop in a static route.
- D. Incorrect.
This is incorrect. Google Cloud does not provide a specific 'next hop ILB' option in Cloud Router. Static routes are used to define the next hop for traffic.