Question 1130
A publishing company monitors member raft logs. Observed: Repeated election attempts occur because several members cannot communicate over the cluster management network. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Captain election stabilizes and logs stop showing repeated lost votes. It provides case-specific verification that the observed behavior (Repeated election attempts occur because several members cannot communicate over the cluster management network) has changed appropriately.
Incorrect Answers
This result checks another issue, for which the observed symptom is: The architecture requires a large search head cluster despite no concurrency, outage or shared knowledge-object need. It does not verify recovery for this situation: Repeated election attempts occur because several members cannot communicate over the cluster management network. The relevant success check is: Captain election stabilizes and logs stop showing repeated lost votes.
Option B would be useful evidence if the observed failure were “One member contains untracked local apps whose contents conflict with the planned deployer bundle”: it checks “Each member presents the expected dashboards after the migration” after the action “Inventory, reconcile and package app content before forming the cluster” addresses “Unmanaged local knowledge objects can create inconsistent SHC migration results”. But the current failure is “Repeated election attempts occur because several members cannot communicate over the cluster management network”, linked to “RAFT-style leader election requires consistent inter-member connectivity and eligible participant status”. Here the targeted action is “Resolve the supported management-port and certificate reachability problem”, and the required proof is “Captain election stabilizes and logs stop showing repeated lost votes”.
The proposed signal relates to: The design increases the number of SHC members without assessing per-member concurrent-search limits and scheduler load. The evidence for this Splunk source case must instead show: Captain election stabilizes and logs stop showing repeated lost votes.