1Z0-1067-25 Question 134
Single answerYou manage an e-commerce application running behind an OCI Load Balancer using a TCP-based health check for back-end compute instances. The logs show that the application is serving requests normally, yet the load balancer intermittently marks some instances as unhealthy. Which action would most effectively resolve these false health check failures?
- A
Implement an HTTP-based health check that returns a 2xx status on a dedicated endpoint
- B
Use a custom route table entry for the load balancer to bypass network filters
- C
Decrease the health check timeout to quickly recycle unhealthy instances
- D
Switch to an HTTPS-based health check without modifying the back-end application
Show answer and explanation
Correct answer: A
Explanation
When configuring health checks on OCI, the type of health check (TCP vs. HTTP vs. HTTPS) must match the application� protocol and expected behavior. For an HTTP-based application, using an HTTP health check with a valid path and 2xx status code verification ensures that only truly unresponsive or misconfigured instances are marked unhealthy. Refer to the �Using Health Checks� section of the Oracle Cloud Infrastructure Load Balancer documentation for additional best practices.
- A. Correct.
Option 1: Implementing an HTTP-based health check with a dedicated endpoint that returns a 2xx status is the most direct way to verify application-level health. This reduces false positives by ensuring the health check aligns closely with the application� actual response.
- B. Incorrect.
Option 2: Altering routing might address connectivity issues but does not help if the core issue is an incorrect protocol or health check type. A custom route table entry would only be relevant if network connectivity was entirely failing.
- C. Incorrect.
Option 3: Decreasing the health check timeout can cause more frequent marking of back ends as unhealthy if they experience temporary slowdowns. This likely increases false positives rather than resolving them.
- D. Incorrect.
Option 4: Switching to HTTPS without configuring the back-end application for SSL would result in a mismatch between the load balancer� health check requirements and the back-end� capabilities, leading to health check failures.