Question 880
An insurance company monitors an indexer node outage. Observed: Analysts expect the cluster to remain permanently under-replicated after one peer fails. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Replication factor returns to target with no unsupported filesystem changes) to the original warning (Analysts expect the cluster to remain permanently under-replicated after one peer fails). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
The proposed check applies to: Peer replacement must preserve capacity for replication and search-factor repair. The current failure was: Analysts expect the cluster to remain permanently under-replicated after one peer fails. Its validation must test: Replication factor returns to target with no unsupported filesystem changes.
This is an unrelated recovery test. It is connected to: The archival procedure relies on manually copying an arbitrary single copy of a bucket under active mutation. The present source situation requires: Replication factor returns to target with no unsupported filesystem changes.
That gate watches a different case: A runbook assumes every replicated bucket copy can receive new live writes simultaneously. It does not detect the current warning: Analysts expect the cluster to remain permanently under-replicated after one peer fails. The necessary confirmation is: Replication factor returns to target with no unsupported filesystem changes.