Question 950
A hotel chain migrates indexer hardware. Observed: The runbook removes an old peer before new peer capacity is proven available. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: After replacement the cluster reaches complete status with normal search latency. It provides case-specific verification that the observed behavior (The runbook removes an old peer before new peer capacity is proven available) has changed appropriately.
Incorrect Answers
The proposed verification result is “The site-specific copy inventory meets documented recovery constraints”. That tests the different scenario “The manager shows copies per site but analysts interpret global RF totals as proof of site resilience”, whose underlying issue is “Global replica totals can hide insufficient copies at a required recovery site” and whose remedy is “Inspect per-site placement factors and locality requirements”. This question instead reports “The runbook removes an old peer before new peer capacity is proven available”, indicating “Peer replacement must preserve capacity for replication and search-factor repair”. The appropriate response is “Add and validate the replacement peer before retiring the old one where supported”, confirmed by the case-specific result “After replacement the cluster reaches complete status with normal search latency”.
This result checks another issue, for which the observed symptom is: Analysts expect the cluster to remain permanently under-replicated after one peer fails. It does not verify recovery for this situation: The runbook removes an old peer before new peer capacity is proven available. The relevant success check is: After replacement the cluster reaches complete status with normal search latency.
The proposed signal relates to: The archival procedure relies on manually copying an arbitrary single copy of a bucket under active mutation. The evidence for this Splunk source case must instead show: After replacement the cluster reaches complete status with normal search latency.