1Z0-1067-25 Question 137
Select 2You have configured an HTTP health check on the path /health for a backend server in your Oracle Cloud Infrastructure (OCI) Load Balancer. The health check interval is set to 30 seconds with 3 retries. After deployment, you notice that one of your backend servers remains in an 'Unhealthy' state in the OCI Console, even though running 'curl http://
- A
Ensure the load balancer is allowed to reach the backend port in the relevant security list or network security group rules
- B
Change the Health Check protocol from HTTP to TCP to reuse the same /health path
- C
Enable advanced traffic routing to automatically redirect health check requests to a different port
- D
Verify that the /health endpoint returns HTTP status code 200 when invoked directly from the backend instance itself
- E
Increase the health check interval to 300 seconds to allow more time for the server to respond
Show answer and explanation
Correct answers: A, D
Explanation
In OCI, load balancer health checks ensure traffic is only directed to healthy backend servers. Verifying that the load balancer has network access to the correct ports and that the application returns an HTTP 200 response on the specified path is crucial. Refer to Oracle documentation (https://docs.oracle.com/en-us/iaas/Content/Balance/Tasks/managinghealthchecks.htm) for best practices on configuring health checks, including proper network security rules and validating successful endpoint responses to maintain accurate health statuses.
- A. Correct.
Correct. If your backend remains unhealthy, one common cause is that the load balancer cannot connect to the backend on the configured port. Ensuring that the backend server allows inbound health check traffic from the load balancer subnets in its security list or network security group rules is essential.
- B. Incorrect.
Incorrect. Simply switching from HTTP to TCP does not necessarily address the root cause (e.g., network access, incorrect path, or missing 200 response). TCP health checks only verify the ability to establish a TCP connection, not that the /health endpoint is returning valid HTTP responses.
- C. Incorrect.
Incorrect. Advanced routing or redirection is not always required for basic health checks, and there is no guarantee that redirecting to a different port will solve a connectivity or endpoint misconfiguration issue.
- D. Correct.
Correct. Verifying whether the application is truly returning HTTP 200 from within the backend environment helps confirm that the endpoint is functional. If the server responds correctly from within its own network environment, you can narrow down the problem to the load balancer configuration, network rules, or a mismatch in the health check settings.
- E. Incorrect.
Incorrect. Increasing the interval to 300 seconds might mask the underlying problem (e.g., security or path misconfiguration) and unnecessarily delay detection of genuine failures. It is more important to verify connectivity and correct responses than to lengthen the health check interval.