Google Professional Cloud Network Engineer Question 255
Single answerGoogle Cloud PlatformYou are tasked with designing a network in Google Cloud where VM instances in one subnet must route traffic through an internal load balancer before reaching VM instances in another subnet. How can you configure the internal load balancer to act as the next hop for traffic between these subnets?
- A
Configure the internal load balancer's frontend IP as the next hop in a custom static route.
- B
Use a global external HTTP(S) load balancer as the next hop for the traffic.
- C
Configure a Google Cloud firewall rule to allow traffic to the internal load balancer.
- D
Set the internal load balancer's backend service as the next hop in a custom static route.
Show answer and explanation
Correct answer: A
Explanation
To use an internal load balancer as a next hop, you must configure a custom static route with the load balancer's frontend IP as the next hop. This ensures that traffic is routed through the load balancer before reaching the destination. Other options, such as external load balancers or backend services, are either invalid or unrelated to the specific routing requirement.
- A. Correct.
Correct. You can configure the internal load balancer's frontend IP as the next hop in a custom static route. Internal load balancers provide a frontend IP that can be used as a gateway for traffic.
- B. Incorrect.
Incorrect. A global external HTTP(S) load balancer cannot be used as a next hop because it is designed for external traffic, not internal routing within a VPC.
- C. Incorrect.
Incorrect. While firewall rules are necessary to allow traffic, they do not configure the internal load balancer as a next hop.
- D. Incorrect.
Incorrect. A backend service is not used as a next hop in Google Cloud. Backend services are tied to load balancers but cannot act as next hops.