Question 70
A banking platform adds a new indexer cluster to a Monitoring Console. Observed: An administrator adds every clustered indexer manually as a search peer despite the cluster topology integration. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: The Monitoring Console displays cluster peer inventory through its configured manager connection. It provides case-specific verification that the observed behavior (An administrator adds every clustered indexer manually as a search peer despite the cluster topology integration) has changed appropriately.
Incorrect Answers
The proposed verification result is “Each instance appears once under the intended role and health dashboard”. That tests the different scenario “The monitoring dashboards show outdated topology roles after changing instance names and groups”, whose underlying issue is “Monitoring Console topology metadata may require refreshed role and group assignments after structural changes” and whose remedy is “Review and update the Monitoring Console distributed environment groups and rebuild assets”. This question instead reports “An administrator adds every clustered indexer manually as a search peer despite the cluster topology integration”, indicating “Clustered indexer monitoring uses the cluster manager relationship rather than individual peer registration”. The appropriate response is “Integrate the cluster manager according to the Monitoring Console distributed deployment procedure”, confirmed by the case-specific result “The Monitoring Console displays cluster peer inventory through its configured manager connection”.
The proposed signal relates to: The operator misreads a general indexer throughput dip as a cluster replication failure. The evidence for this Splunk source case must instead show: The Monitoring Console displays cluster peer inventory through its configured manager connection.
This result checks another issue, for which the observed symptom is: The monitoring rollout begins before validating supported configuration of the monitoring instance. It does not verify recovery for this situation: An administrator adds every clustered indexer manually as a search peer despite the cluster topology integration. The relevant success check is: The Monitoring Console displays cluster peer inventory through its configured manager connection.