Question 580
A city hospital monitors retention by event age. Observed: Capacity graphs show ample disk but events still expire due to an intentionally short frozen-time setting. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (A controlled test demonstrates the expected earliest bucket retirement rule) to the original warning (Capacity graphs show ample disk but events still expire due to an intentionally short frozen-time setting). 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 index is created but historical data imports vanish from searches because the assigned role excludes the index. The present source situation requires: A controlled test demonstrates the expected earliest bucket retirement rule.
That gate watches a different case: Historical and new events use different field extraction behavior because the sourcetype changes midstream. It does not detect the current warning: Capacity graphs show ample disk but events still expire due to an intentionally short frozen-time setting. The necessary confirmation is: A controlled test demonstrates the expected earliest bucket retirement rule.
The proposed check applies to: Aggressive bucket rollover increases bucket counts and overhead without improving retention. The current failure was: Capacity graphs show ample disk but events still expire due to an intentionally short frozen-time setting. Its validation must test: A controlled test demonstrates the expected earliest bucket retirement rule.