Question 660
A bank calculates distinct account IDs over one month. Observed: A count of raw events is confused with a count of distinct account identifiers. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Results reconcile to known distinct account IDs in a controlled data sample) to the original warning (A count of raw events is confused with a count of distinct account identifiers). 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: Search Job Inspector shows expensive raw event retrieval after an unconstrained wildcard search. The present source situation requires: Results reconcile to known distinct account IDs in a controlled data sample.
That gate watches a different case: The search still performs full raw scans because its SPL is not eligible for the chosen acceleration mode. It does not detect the current warning: A count of raw events is confused with a count of distinct account identifiers. The necessary confirmation is: Results reconcile to known distinct account IDs in a controlled data sample.
The proposed check applies to: Subsearch failure or truncation can compromise the intended outer search semantics. The current failure was: A count of raw events is confused with a count of distinct account identifiers. Its validation must test: Results reconcile to known distinct account IDs in a controlled data sample.