Question 570
A Splunk Enterprise administrator must verify a correction for this problem: Application logs use UTC but dashboards show events shifted by several hours because Splunk guesses local time. Which result is the strongest acceptance evidence?
Explanation
Correct Answer
A known UTC timestamp indexes at the expected absolute event time. This is the discriminating acceptance check, not merely an indication that a configuration file exists. Event-time correctness depends on the timestamp format and timezone assigned during parsing.
Incorrect Answers
This option serves the scenario “A sourcetype uses a date format ambiguous between day-first and month-first, causing events to land in the wrong period”. Known date samples are indexed into the intended days and time zones. The present scenario is distinguished by “A known UTC timestamp indexes at the expected absolute event time”.
The proposed proof checks A device log contains no parsable event-time field and the administrator treats search-time formatting as a complete fix. The current failure instead needs an outcome showing A known UTC timestamp indexes at the expected absolute event time.
The related but distinct situation is “A team approves an input after one preview line even though production includes nested JSON and stack traces”. Sample results agree with expected event and timestamp outputs across all known formats. For the stated problem, “A known UTC timestamp indexes at the expected absolute event time” addresses the central condition.