Question 1010
A public broadcaster experiences manager-to-peer partition. Observed: Operators assume the manager partition means indexed data on peers was immediately erased. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Peer bucket files remain present and manager coordination recovers without re-ingestion. It provides case-specific verification that the observed behavior (Operators assume the manager partition means indexed data on peers was immediately erased) has changed appropriately.
Incorrect Answers
The proposed signal relates to: The architecture sets replication factor three but assumes any one copy guarantees immediately searchable data. The evidence for this Splunk source case must instead show: Peer bucket files remain present and manager coordination recovers without re-ingestion.
Option B would be useful evidence if the observed failure were “The engineer sets an RF higher than the number of available eligible peers”: it checks “No permanently unsatisfiable replication-factor warning remains” after the action “Align replication target and peer count, including failure tolerance, before enabling the policy” addresses “Cluster replication objectives must be achievable with available peer capacity and topology”. But the current failure is “Operators assume the manager partition means indexed data on peers was immediately erased”, linked to “Management connectivity loss and physical indexed-bucket loss are different failure conditions”. Here the targeted action is “Diagnose control-plane connectivity before making data-restoration changes”, and the required proof is “Peer bucket files remain present and manager coordination recovers without re-ingestion”.
This result checks another issue, for which the observed symptom is: An archived bucket is restored with a conflicting identity into a running clustered index. It does not verify recovery for this situation: Operators assume the manager partition means indexed data on peers was immediately erased. The relevant success check is: Peer bucket files remain present and manager coordination recovers without re-ingestion.