1Z0-1067-25 Question 135
Select 2Your organization is hosting a web application behind an Oracle Cloud Infrastructure (OCI) Load Balancer. After updating the application to expose a dedicated health check endpoint at /health, you want to configure the load balancer to stop routing traffic to instances that are unresponsive or returning unhealthy responses. Which two steps will correctly implement the desired health check configuration?
- A
Configure the load balancer backend set to use an HTTP health check, specifying /health as the URL path.
- B
Increase the health check timeout to 60 seconds to guarantee fewer false positives.
- C
Create a custom route for /health in the VCN routing table to direct traffic to a management subnet.
- D
Expect an HTTP 200 status code as a successful response from the /health endpoint in the load balancer settings.
- E
Deploy a separate Load Balancer for the /health endpoint, isolating it from the primary backend set.
Show answer and explanation
Correct answers: A, D
Explanation
When implementing health checks in OCI, you typically configure an HTTP or TCP health check under the load balancer� backend set. Specifying the correct check path (e.g., /health) and an expected response code (commonly HTTP 200) ensures that only healthy instances receive traffic. For more details, refer to Oracle's Load Balancer documentation on configuring advanced health checks.
- A. Correct.
Correct. Specifying an HTTP health check with a path of /health ensures the load balancer actively checks the endpoint and identifies unresponsive instances.
- B. Incorrect.
Incorrect. Increasing timeouts arbitrarily (e.g., to 60 seconds) can delay detection of truly unhealthy instances. It's better to fine-tune timeout settings based on the application� known performance and response times.
- C. Incorrect.
Incorrect. A separate VCN route for /health is usually unnecessary. The health check traffic is handled internally by the load balancer to the backend set and typically doesn�t require a custom route.
- D. Correct.
Correct. The load balancer confirms health by checking for an expected HTTP 200 response from /health. Receiving any other status code indicates a potentially unhealthy instance.
- E. Incorrect.
Incorrect. In most cases, you configure health checks on the existing load balancer rather than deploying an entirely new one solely for the health endpoint.