Question 560
An energy utility needs separate retention for two data classes. Observed: The index combines short-lived debug events with seven-year regulated audit records. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (A retention exercise expires debug history while preserving required audit history) to the original warning (The index combines short-lived debug events with seven-year regulated audit records). 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: A parsing rule overwrites correct host metadata with a generic relay name. The present source situation requires: A retention exercise expires debug history while preserving required audit history.
The proposed check applies to: Frozen buckets leave the active searchable index and require configured archival handling if preservation is required. The current failure was: The index combines short-lived debug events with seven-year regulated audit records. Its validation must test: A retention exercise expires debug history while preserving required audit history.
That gate watches a different case: An operator assumes fishbucket stores the complete indexed text of every monitored file. It does not detect the current warning: The index combines short-lived debug events with seven-year regulated audit records. The necessary confirmation is: A retention exercise expires debug history while preserving required audit history.