Question 120
A retail chain wants predictable indexing capacity. Observed: A monitoring report lists licensed volume but omits event-processing queue saturation. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (The dashboard highlights congestion before data-delivery latency breaches its target) to the original warning (A monitoring report lists licensed volume but omits event-processing queue saturation). 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 team inspects only host CPU without correlating scheduler and search activity dashboards. The present source situation requires: The dashboard highlights congestion before data-delivery latency breaches its target.
The proposed check applies to: Site-aware troubleshooting requires tracking replica and locality relationships rather than a flat host list. The current failure was: A monitoring report lists licensed volume but omits event-processing queue saturation. Its validation must test: The dashboard highlights congestion before data-delivery latency breaches its target.
That gate watches a different case: The Monitoring Console labels all scheduled-search misses as underlying indexer outages. It does not detect the current warning: A monitoring report lists licensed volume but omits event-processing queue saturation. The necessary confirmation is: The dashboard highlights congestion before data-delivery latency breaches its target.