SPLK-1001 Practice Question: Creating Reports, Dashboards and Visualizations
Exhibit
| tstats summariesonly=t count where index=main by _time, sourcetype span=1h | timechart count by sourcetype
Refer to the exhibit. The timechart returns only partial results for some sourcetypes, and there are gaps in the timeline. Which is the most likely reason?
⚠ Common exam trap
Splunk often tests the misconception that `tstats` behaves like `search` or `stats` and can access all raw events, but the trap here is that candidates overlook the fact that `tstats` is limited to summary data and may not cover all time ranges if acceleration is incomplete or not configured.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The tstats command only uses summary data, which may not cover all time ranges
The `tstats` command in Splunk operates on indexed-time summary data stored in the tsidx files, not on raw events. This summary data is generated during indexing based on the data model acceleration or summary indexing configuration, and it may not cover all time ranges if the acceleration has not been built for those periods or if the data model is not fully accelerated. As a result, `tstats` can return partial results and gaps in the timeline, especially when the time range extends beyond the accelerated data coverage.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The timechart span=1h conflicts with the tstats span
Why it's wrong here
Both use 1-hour spans; there is no conflict; the timechart simply uses the aggregated data.
- ✓
The tstats command only uses summary data, which may not cover all time ranges
Why this is correct
summariesonly=t restricts tstats to precomputed summaries; if the summary is incomplete, results will have gaps.
- ✗
The sourcetype field is not summarized
Why it's wrong here
Sourcetype is a common field and is typically included in summary data models.
- ✗
The where clause is invalid
Why it's wrong here
The where clause is valid syntax for tstats.
Go deeper
Related to this question
About these practice questions
This SPLK-1001 question is part of Courseiva's 502-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SPLK-1001 practice question is part of Courseiva's free Splunk certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SPLK-1001 exam.