Google Professional Cloud Network Engineer Question 444
Single answerGoogle Cloud PlatformYou are managing a GKE cluster that needs to serve web traffic globally with minimal latency. The application runs as a set of stateless pods in multiple regions. You are tasked with configuring load balancing to ensure traffic is routed to the nearest backend while enabling advanced traffic management capabilities. Which solution should you implement?
- A
Use the GKE Ingress controller with a Network Endpoint Group (NEG) backend.
- B
Use the GKE Gateway controller with a global external HTTP(S) load balancer.
- C
Configure a regional HTTP(S) load balancer with the GKE Gateway controller.
- D
Use a TCP/UDP load balancer with GKE Ingress.
Show answer and explanation
Correct answer: B
Explanation
The GKE Gateway controller, when paired with a global external HTTP(S) load balancer, enables advanced traffic management and global load balancing. This setup allows traffic to be routed to the closest backend, reducing latency and meeting the requirements of a multi-regional GKE deployment. Other options either lack global load balancing capabilities or do not support advanced HTTP(S) traffic management features, which are essential for this scenario.
- A. Incorrect.
The GKE Ingress controller with NEG can route traffic to backend services running on GKE, but it does not provide global load balancing capabilities needed for minimizing latency across multiple regions.
- B. Correct.
The GKE Gateway controller with a global external HTTP(S) load balancer is the correct choice as it supports advanced traffic management, global load balancing, and routing traffic to the closest backend.
- C. Incorrect.
A regional HTTP(S) load balancer is limited to a single region and does not meet the requirement of serving traffic globally with minimal latency.
- D. Incorrect.
A TCP/UDP load balancer does not provide the advanced traffic management or HTTP(S) features required for routing web traffic effectively.