SPLK-1001 Practice Question: Creating Reports, Dashboards and Visualizations
A dashboard uses tokens for time range selection. The admin wants to ensure that when a user changes the time range picker from 'Last 24 hours' to 'Last 7 days', all panels in the dashboard update accordingly. What is the correct way to define the token in Simple XML?
⚠ Common exam trap
Splunk often tests the misconception that custom tokens or explicit event handlers are required to propagate time range changes, when in fact the default $earliest$ and $latest$ tokens are automatically bound to the time picker and update all panels seamlessly.
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
✓
Use the default time range tokens $earliest$ and $latest$ without additional definition.
Splunk's Simple XML automatically provides the default time range tokens $earliest$ and $latest$ that are updated whenever the time range picker is changed. These tokens are implicitly bound to the dashboard's time picker, so no additional definition or event handler is needed for all panels to reflect the new time range.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Define a token $range$ in the time range picker's onChange event.
Why it's wrong here
$range$ is not a standard token.
- ✓
Use the default time range tokens $earliest$ and $latest$ without additional definition.
Why this is correct
The default tokens are automatically updated by the time range picker.
- ✗
Define a custom token $time_range$ and bind the time range picker to it, then reference $time_range$ in each panel's search.
Why it's wrong here
Defining a custom token for the time range picker is incorrect because it captures the *label* (e.g., 'Last 24 hours') rather than the specific `earliest` and `latest` time values required for search commands to filter events by time. Splunk's time range picker automatically manages dedicated `earliest` and `latest` tokens for this purpose. This option is tempting as custom tokens are used to pass arbitrary string values from inputs to searches, making it suitable for scenarios like selecting a hostname or an index.
- ✗
Set the token $timePicker$ in the dashboard's init block.
Why it's wrong here
$timePicker$ is not a valid token; it's a component.
Go deeper
Related to this question
About these practice questions
One of 502 original SPLK-1001 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.