SPLK-1001 Using Fields and Lookups Practice Question
A Splunk user wants to create a lookup that maps a field 'status_code' to a human-readable 'status_description'. The lookup data is small and changes infrequently. Which TWO methods are appropriate for creating this lookup? (Choose two.)
⚠ Common exam trap
A common mix-up: candidates confuse KV Store (designed for dynamic, writable data) with static CSV lookups, or think the `lookup` command can create mappings on the fly, when in fact it only applies pre-defined lookup definitions from configuration files.
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
✓
Create a lookup definition file (transforms.conf) with the mapping inline
A lookup definition file (transforms.conf) can contain an inline mapping using the `filename` or `external_type` settings, but more specifically for small static data, you can define a lookup with a `table` or `static` definition that directly maps values without an external file. This is efficient for small, infrequently changing data as it avoids file management overhead. Option E is correct because saving a CSV file with the mapping and defining a lookup from that file is the standard method for small, static lookup data in Splunk, using the `lookup` command or automatic lookup to enrich events.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a lookup definition file (transforms.conf) with the mapping inline
Why this is correct
A lookup definition file can include inline data or reference a file; it's a standard method.
- ✗
Create a KV Store collection to store the mapping
Why it's wrong here
KV Store is better for large, frequently updated data, not for a small static mapping.
- ✗
Use the 'lookup' command in a search to create a temporary mapping each time
Why it's wrong here
The lookup command uses existing lookups; it does not create persistent mappings.
- ✗
Use a calculated field in props.conf to derive the description from the code
Why it's wrong here
A calculated field in props.conf applies a static transformation at search time based on existing field values, but it cannot perform a dynamic key-value lookup from an external mapping table. The scenario requires a lookup that maps each status_code to its corresponding status_description, which demands a lookup table file or KV Store, not a formula. This option is tempting because calculated fields are useful for deriving new fields via simple expressions or concatenations, such as extracting a domain from a URL, where no external reference data is needed.
- ✓
Save a CSV file with the mapping and define a lookup from that file
Why this is correct
A CSV file is ideal for small, static lookup data.
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.