Question 740
A public pension office uses `eventstats` in a compliance query. Observed: Analysts switch to `stats` and lose the individual events needed for audit evidence. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Audit outputs contain the original event fields alongside appropriate aggregate totals) to the original warning (Analysts switch to `stats` and lose the individual events needed for audit evidence). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: `stats` produces millions of groups that exceed expected memory headroom. It does not detect the current warning: Analysts switch to `stats` and lose the individual events needed for audit evidence. The necessary confirmation is: Audit outputs contain the original event fields alongside appropriate aggregate totals.
This is an unrelated recovery test. It is connected to: `timechart` silently changes its default bucket span with the selected interval. The present source situation requires: Audit outputs contain the original event fields alongside appropriate aggregate totals.
The proposed check applies to: transaction retains full grouped events and can cost more than equivalent summary aggregation. The current failure was: Analysts switch to `stats` and lose the individual events needed for audit evidence. Its validation must test: Audit outputs contain the original event fields alongside appropriate aggregate totals.