Question 1040
A public hospital is removing a failed peer permanently. Observed: The old peer still appears as participating, leaving bucket fixup assumptions unresolved. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (The cluster inventory and replication status converge without orphaned peer references) to the original warning (The old peer still appears as participating, leaving bucket fixup assumptions unresolved). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: Operations restart all indexers repeatedly, adding instability without addressing blocked repair capacity. It does not detect the current warning: The old peer still appears as participating, leaving bucket fixup assumptions unresolved. The necessary confirmation is: The cluster inventory and replication status converge without orphaned peer references.
This is an unrelated recovery test. It is connected to: New site peers are added without the proper site identifier. The present source situation requires: The cluster inventory and replication status converge without orphaned peer references.
The proposed check applies to: Cluster upgrades require controlled sequencing and checking of replication health. The current failure was: The old peer still appears as participating, leaving bucket fixup assumptions unresolved. Its validation must test: The cluster inventory and replication status converge without orphaned peer references.