mediumMultiple ChoiceObjective-mapped
SPLK-1001 Practice Question: Refer to the exhibit
Exhibit
props.conf: [web_access] DATETIME_CONFIG = /etc/datetime.xml MAX_TIMESTAMP_LOOKAHEAD = 20 TIME_PREFIX = ^ TIME_FORMAT = %d/%b/%Y:%H:%M:%S
Refer to the exhibit. A data model named 'Web' is built on sourcetype 'web_access'. A user reports that the timestamp field is not being extracted correctly in the data model. What is the most likely issue?
⚠ Common exam trap
A common pitfall in Splunk exams is overlooking that the TIME_PREFIX setting can be too restrictive. Candidates often assume a missing DATETIME_CONFIG or incorrect TIME_FORMAT is the root cause, but in data models, an incorrectly anchored TIME_PREFIX (like `^`) frequently prevents proper timestamp extraction from events where the timestamp is not at the very beginning.
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 TIME_PREFIX is set to `^` which may not match the timestamp location.
The TIME_PREFIX set to `^` anchors the timestamp extraction to the very beginning of the event. If the actual timestamp appears later in the event (e.g., after a leading field like an IP address or a date), this prefix will fail to match, causing Splunk to fall back to the event's ingestion time or extract no timestamp at all. In a data model, timestamp extraction relies on the same props.conf settings as search-time field extraction, so an incorrect TIME_PREFIX directly breaks the expected timestamp field.
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 TIME_PREFIX is set to `^` which may not match the timestamp location.
Why this is correct
A caret `^` matches the start of the event, but timestamps often appear later.
- ✗
The DATETIME_CONFIG file is missing.
Why it's wrong here
The config file is specified and likely exists.
- ✗
The TIME_FORMAT does not match the data.
Why it's wrong here
The format %d/%b/%Y:%H:%M:%S is common for web logs.
- ✗
The MAX_TIMESTAMP_LOOKAHEAD is too high.
Why it's wrong here
20 is a reasonable value; high values are not problematic.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SPLK-1001 question from scratch — 502 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.