Question 140
A hospitality platform uses a clustered search tier. Observed: Monitoring Console shows too few scheduled searches after dashboards are filtered to one member. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Total scheduled-search events reconcile across the member roster) to the original warning (Monitoring Console shows too few scheduled searches after dashboards are filtered to one member). 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 server-role mapping omits the new search-head instances. The present source situation requires: Total scheduled-search events reconcile across the member roster.
The proposed check applies to: Monitoring Console topology metadata may require refreshed role and group assignments after structural changes. The current failure was: Monitoring Console shows too few scheduled searches after dashboards are filtered to one member. Its validation must test: Total scheduled-search events reconcile across the member roster.
That gate watches a different case: Operators attribute receiver-port closures to firewall policy despite corresponding blocked internal queues. It does not detect the current warning: Monitoring Console shows too few scheduled searches after dashboards are filtered to one member. The necessary confirmation is: Total scheduled-search events reconcile across the member roster.