Google Professional Cloud Network Engineer Question 585
Single answerGoogle Cloud PlatformYour organization has a web application hosted on Google Cloud and uses an HTTP(S) Load Balancer to distribute traffic to backend instances. Users have reported that long-running requests are being terminated prematurely. You are tasked with customizing the timeout settings to ensure these requests are handled properly. Which timeout setting should you modify to resolve this issue?
- A
The backend service's timeout setting
- B
The HTTP(S) Load Balancer's idle timeout setting
- C
The TCP proxy timeout setting for the load balancer
- D
The instance-level timeout setting in the Compute Engine VM
Show answer and explanation
Correct answer: A
Explanation
To address prematurely terminated long-running requests, you need to adjust the backend service's timeout setting. This setting allows you to configure the maximum duration the HTTP(S) Load Balancer waits for a response from backend instances. Other settings, such as idle timeout or TCP proxy, are unrelated to this specific issue.
- A. Correct.
Correct. The backend service's timeout setting determines how long the load balancer waits for a response from the backend before timing out. Increasing this timeout resolves issues with long-running requests.
- B. Incorrect.
Incorrect. The idle timeout setting only affects how long a connection can remain idle, not the duration of processing a request.
- C. Incorrect.
Incorrect. The TCP proxy timeout is unrelated to HTTP(S) Load Balancers and applies to TCP-based load balancing, which is not used in this scenario.
- D. Incorrect.
Incorrect. Compute Engine VM instance settings do not include customizable timeout settings specific to this problem.