Automatic Lookup Not Working: Transforms.conf
An administrator notices that an automatic lookup is not being applied to events from a certain sourcetype. The lookup file exists and the configuration in props.conf appears correct. What is a possible reason?
Quick Answer
The answer is that the lookup table is defined in transforms.conf incorrectly. This is the correct choice because an automatic lookup in Splunk is a two-part configuration: props.conf triggers the lookup for a specific sourcetype, but transforms.conf holds the critical details like the lookup file name, field mappings, and match type. If transforms.conf has a syntax error, a mismatched field name, or a wrong stanza name, the lookup will fail silently even when props.conf looks perfect. On the SPLK-1002 exam, this question tests your understanding of the relationship between props.conf and transforms.conf, and the common trap is assuming that a correct props.conf entry guarantees the lookup will work. A helpful memory tip is to think of props.conf as the "caller" and transforms.conf as the "callee"—if the callee is missing or broken, the call never completes.
⚠ Common exam trap
Many candidates assume a correctly written props.conf stanza is sufficient, but Splunk requires a corresponding transforms.conf stanza to define the lookup details, and many test-takers overlook this two-step configuration dependency.
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 lookup table is defined in transforms.conf incorrectly
The automatic lookup is defined in props.conf, but the actual lookup table configuration (including the lookup file name, field mappings, and match type) is specified in transforms.conf. If transforms.conf is missing, has a syntax error, or incorrectly defines the lookup (e.g., wrong filename, mismatched field names, or incorrect stanza name), the automatic lookup will fail silently, even if props.conf appears correct.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Splunk needs to be restarted after adding the automatic lookup
Why it's wrong here
A restart might be needed only if index-time configs changed; for search-time, a reload is usually enough.
- ✗
The lookup file is stored in the wrong directory but referenced correctly
Why it's wrong here
If referenced correctly, location is fine; might be in default vs local.
- ✗
The lookup field is case-sensitive and the data doesn't match
Why it's wrong here
Case sensitivity is a matching issue, not a configuration issue.
- ✓
The lookup table is defined in transforms.conf incorrectly
Why this is correct
Both props.conf and transforms.conf must be configured correctly.
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 →
Same concept, more angles
1 more way this is tested on SPLK-1001
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A Splunk administrator configured an automatic lookup as shown. When searching index=main source=/var/log/auth.log, the department field is not populated. What is the most likely cause?
hard- A.The LOOKUP- stanza requires a numeric priority.
- B.The transforms.conf file is not in the correct directory.
- C.The user_lookup.csv file does not exist in the lookups directory.
- ✓ D.The match_type syntax is incorrect and the field mapping is mismatched.
Why D: The most common cause for a lookup not populating a field is a mismatch between the field mapping in the transforms.conf stanza and the actual field names in the lookup table. If the match_type syntax is incorrect (e.g., using WILDCARD instead of EXACT or specifying the wrong field name), Splunk will fail to match events to lookup entries, leaving the department field empty.
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.