Google Professional Cloud Network Engineer Question 588
Single answerGoogle Cloud PlatformYour team has deployed an application on Google Kubernetes Engine (GKE) with an HTTP(S) Load Balancer to handle user traffic. Users report that the application occasionally takes longer than expected to respond, causing some requests to fail. You suspect the default timeout settings are too short for certain requests. Which specific timeout setting can you customize on the HTTP(S) Load Balancer to address this issue?
- A
Backend service timeout
- B
Session affinity timeout
- C
Idle timeout for TCP connections
- D
Health check timeout
Show answer and explanation
Correct answer: A
Explanation
To address long-running requests failing due to timeouts, you can increase the backend service timeout on the HTTP(S) Load Balancer. This setting controls the maximum time the load balancer waits for a response from the backend service before timing out. The other timeout settings do not directly address request-response time handling for user traffic.
- A. Correct.
The backend service timeout defines the amount of time the load balancer waits for a response from the backend before timing out. Customizing this setting can allow longer-running requests to complete successfully, making it the correct choice.
- B. Incorrect.
Session affinity timeout defines how long the load balancer maintains a session between a client and a specific backend instance. This does not affect the time allowed for individual requests to complete.
- C. Incorrect.
The idle timeout for TCP connections determines how long a connection can remain idle before being closed. This is unrelated to the application request-response time.
- D. Incorrect.
Health check timeout defines how long the load balancer waits for a health check response from a backend. This is used for health monitoring and does not affect user request timeouts.