Configuring Health Check for HTTP(S) Load Balancer

B.

When creating an HTTP(S) load balanced service, it is important to ensure that the backend instances are responding properly. This is done by configuring a health check for the backend instances. The health check is a request that is periodically sent to the backend instances to verify that they are still responding to requests.

There are different parameters that can be set when configuring the health check, but for this question, we are given four possible configurations to choose from:

A. Set request-path to a specific URL used for health checking, and set proxy-header to PROXY_V1. B. Set request-path to a specific URL used for health checking, and set host to include a custom host header that identifies the health check. C. Set request-path to a specific URL used for health checking, and set response to a string that the backend service will always return in the response body. D. Set proxy-header to the default value, and set host to include a custom host header that identifies the health check.

Option A sets the request path to a specific URL used for health checking, and sets the proxy header to PROXY_V1. The PROXY_V1 header is used to pass client connection information to the backend instance, and it is not relevant for the health check. Therefore, this option is not the correct answer.

Option B sets the request path to a specific URL used for health checking and includes a custom host header that identifies the health check. This is a valid configuration for a health check, as it allows the backend instance to identify the request as a health check request and respond accordingly. Therefore, option B could be the correct answer.

Option C sets the request path to a specific URL used for health checking, and sets the response to a string that the backend service will always return in the response body. This option is not recommended for health checks because it relies on the backend instance to always return the expected string, which may not always be the case. Therefore, this option is not the correct answer.

Option D sets the proxy header to the default value and includes a custom host header that identifies the health check. This is also a valid configuration for a health check, as it allows the backend instance to identify the request as a health check request and respond accordingly. Therefore, option D could also be the correct answer.

In conclusion, both options B and D are valid configurations for a health check, and the correct answer will depend on the specific requirements of the load balanced service.