Question 100
A payment provider isolates its monitoring console behind a firewall. Observed: No health data arrives from search heads although the console itself is healthy. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (A peer reachability test and updated Monitoring Console views both succeed) to the original warning (No health data arrives from search heads although the console itself is healthy). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
This is an unrelated recovery test. It is connected to: The Monitoring Console cannot show one remote indexer because it was never added as a search peer. The present source situation requires: A peer reachability test and updated Monitoring Console views both succeed.
That gate watches a different case: The operator misreads a general indexer throughput dip as a cluster replication failure. It does not detect the current warning: No health data arrives from search heads although the console itself is healthy. The necessary confirmation is: A peer reachability test and updated Monitoring Console views both succeed.
The proposed check applies to: Alert definitions that lack baselines and response ownership are difficult to triage reliably. The current failure was: No health data arrives from search heads although the console itself is healthy. Its validation must test: A peer reachability test and updated Monitoring Console views both succeed.