Google Professional Cloud Network Engineer Question 589
Single answerGoogle Cloud PlatformYou are managing a Google Cloud project that uses a public-facing load balancer to handle incoming HTTP traffic for a web application. Users have reported that connections stay open for too long on idle sessions, causing resource exhaustion on backend instances. How can you customize the connection timeout behavior to address this issue?
- A
Configure the backend service's 'connection draining timeout' to close idle connections more quickly.
- B
Set the 'timeoutSec' property in the backend service to define a shorter timeout for idle connections.
- C
Modify the 'sessionAffinity' setting in the backend service to remove the stickiness of user sessions.
- D
Adjust the timeout setting in the frontend HTTP load balancer to close idle connections promptly.
Show answer and explanation
Correct answer: B
Explanation
To address the issue of idle connections staying open for too long, the 'timeoutSec' property in the backend service should be configured. This property specifies the timeout duration for connections, including idle connections, and ensures that resources are not unnecessarily consumed. Other options like connection draining, session affinity, or frontend load balancer settings do not directly address idle connection timeouts.
- A. Incorrect.
This is incorrect. Connection draining timeout is used when removing backends from a load balancer but does not control idle connection timeouts.
- B. Correct.
This is correct. The 'timeoutSec' property in a backend service specifies the maximum time a backend can take to respond to a request, and it can also be used to set an idle connection timeout.
- C. Incorrect.
This is incorrect. Session affinity determines whether user requests are routed to the same backend instance but does not affect connection timeouts.
- D. Incorrect.
This is incorrect. While the frontend load balancer has timeout settings, idle connection timeouts are typically managed at the backend service level.