Question 1120
A travel booking company places an HTTP load balancer before SHC. Observed: The health check sends users to a member that is still starting and not ready to serve searches. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (User sessions land only on healthy search heads during rolling restarts) to the original warning (The health check sends users to a member that is still starting and not ready to serve searches). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
This is an unrelated recovery test. It is connected to: The runbook instructs changing captain by merely switching the application load-balancer primary. The present source situation requires: User sessions land only on healthy search heads during rolling restarts.
The proposed check applies to: Cluster resilience needs a client access mechanism that can reach healthy members. The current failure was: The health check sends users to a member that is still starting and not ready to serve searches. Its validation must test: User sessions land only on healthy search heads during rolling restarts.
That gate watches a different case: New SHC members lack required local unmanaged lookup files despite dashboard definitions being replicated. It does not detect the current warning: The health check sends users to a member that is still starting and not ready to serve searches. The necessary confirmation is: User sessions land only on healthy search heads during rolling restarts.