Question 460
A hospital is assessing why events were placed in the wrong timezone. Observed: The indexed _time differs from source time despite a correctly configured search display timezone. Which ongoing verification would best guard against the same failure?
Explanation
Correct Answer
This check ties the expected state (Test events have the intended indexed epoch and search display adjusts per user setting) to the original warning (The indexed _time differs from source time despite a correctly configured search display timezone). It is a source-case regression control, not an independently Splunk-certified testing procedure.
Incorrect Answers
That gate watches a different case: Corrupted event text appears after indexing because the source encoding was interpreted incorrectly. It does not detect the current warning: The indexed _time differs from source time despite a correctly configured search display timezone. The necessary confirmation is: Test events have the intended indexed epoch and search display adjusts per user setting.
This is an unrelated recovery test. It is connected to: A proposed search-time dashboard edit leaves the original sensitive bytes in the index. The present source situation requires: Test events have the intended indexed epoch and search display adjusts per user setting.
The proposed check applies to: Incorrect timestamp anchor selection changes the indexed event timeline. The current failure was: The indexed _time differs from source time despite a correctly configured search display timezone. Its validation must test: Test events have the intended indexed epoch and search display adjusts per user setting.