Question 1160
A pharmaceutical company evaluates search availability. Observed: The SHC has several members but an external DNS entry points to only a failed node. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (A client can search through the shared endpoint after one member is isolated) to the original warning (The SHC has several members but an external DNS entry points to only a failed node). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
The proposed check applies to: External HTTP routing does not directly control internal RAFT captain election. The current failure was: The SHC has several members but an external DNS entry points to only a failed node. Its validation must test: A client can search through the shared endpoint after one member is isolated.
That gate watches a different case: Search app push changes protected local settings on a member unexpectedly. It does not detect the current warning: The SHC has several members but an external DNS entry points to only a failed node. The necessary confirmation is: A client can search through the shared endpoint after one member is isolated.
This is an unrelated recovery test. It is connected to: The health check sends users to a member that is still starting and not ready to serve searches. The present source situation requires: A client can search through the shared endpoint after one member is isolated.