Question 760
A hospital search head is under CPU pressure. Observed: Administrators increase dispatch concurrency before investigating a pathological unbounded search. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Interactive query latency improves without increased job failures) to the original warning (Administrators increase dispatch concurrency before investigating a pathological unbounded search). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
The proposed check applies to: Distributed search completeness depends on availability and status of targeted search peers. The current failure was: Administrators increase dispatch concurrency before investigating a pathological unbounded search. Its validation must test: Interactive query latency improves without increased job failures.
That gate watches a different case: A subsearch's output contains extra columns and produces unexpected search-filter semantics when expanded. It does not detect the current warning: Administrators increase dispatch concurrency before investigating a pathological unbounded search. The necessary confirmation is: Interactive query latency improves without increased job failures.
This is an unrelated recovery test. It is connected to: A search uses `dedup` without deterministic ordering and returns a different example event on each execution. The present source situation requires: Interactive query latency improves without increased job failures.