Google Professional Cloud Network Engineer Question 587
Single answerGoogle Cloud PlatformYour team has deployed a custom API on Google Cloud that is accessed via an HTTP(S) Load Balancer. Some clients are experiencing failures when making long-running requests. After analyzing the traffic, you determine that these requests exceed the default timeout. You need to customize the timeout settings to accommodate these long-running requests. What is the correct way to set this up?
- A
Adjust the backend service timeout settings in the HTTP(S) Load Balancer configuration.
- B
Modify the timeout setting in the Google Cloud Firewall rules for the backend service.
- C
Update the client-side application to retry requests after the default timeout limit.
- D
Enable session affinity in the HTTP(S) Load Balancer to prevent timeouts.
Show answer and explanation
Correct answer: A
Explanation
To address timeout issues for long-running requests, you need to adjust the backend service timeout settings in the HTTP(S) Load Balancer configuration. This setting specifies how long the load balancer waits for a response before timing out. Other options, such as modifying firewall rules or enabling session affinity, do not directly resolve the issue of timeout customization.
- A. Correct.
Correct. The backend service timeout setting in the HTTP(S) Load Balancer configuration determines how long the load balancer waits for a response from a backend before timing out.
- B. Incorrect.
Incorrect. Google Cloud Firewall rules control access to resources, not timeout settings for requests.
- C. Incorrect.
Incorrect. While retrying requests can be a mitigation strategy, it does not address the root cause of the timeout issue. Adjusting the backend service timeout is the appropriate solution.
- D. Incorrect.
Incorrect. Session affinity ensures that requests from a client are sent to the same backend instance but does not affect timeout settings.