Question 1020
A transport ministry changes site replication factors. Observed: The new policy references a recovery site that does not exist yet. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Site copy reports show the intended replica counts after rollout) to the original warning (The new policy references a recovery site that does not exist yet). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: The archival procedure relies on manually copying an arbitrary single copy of a bucket under active mutation. It does not detect the current warning: The new policy references a recovery site that does not exist yet. The necessary confirmation is: Site copy reports show the intended replica counts after rollout.
The proposed check applies to: Manager controls cluster metadata and coordination; peer nodes store indexed bucket data. The current failure was: The new policy references a recovery site that does not exist yet. Its validation must test: Site copy reports show the intended replica counts after rollout.
This is an unrelated recovery test. It is connected to: The master index configuration is changed only on one peer and other members retain old retention rules. The present source situation requires: Site copy reports show the intended replica counts after rollout.