Question 1180
A campus IT group retires an SHC member. Observed: The member is removed from the load balancer but remains in the SHC membership inventory. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (The remaining members have stable captaincy and the retired node is absent from membership) to the original warning (The member is removed from the load balancer but remains in the SHC membership inventory). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: Search dispatch is skipped on some members because the captain is overloaded and scheduler work is poorly distributed. It does not detect the current warning: The member is removed from the load balancer but remains in the SHC membership inventory. The necessary confirmation is: The remaining members have stable captaincy and the retired node is absent from membership.
The proposed check applies to: Deployer-managed app content and user-created replicated knowledge objects have different management paths. The current failure was: The member is removed from the load balancer but remains in the SHC membership inventory. Its validation must test: The remaining members have stable captaincy and the retired node is absent from membership.
This is an unrelated recovery test. It is connected to: The backup plan captures only one member and excludes the deployer-managed configuration. The present source situation requires: The remaining members have stable captaincy and the retired node is absent from membership.