- A
Splunk needs to be restarted after adding the automatic lookup
Why wrong: A restart might be needed only if index-time configs changed; for search-time, a reload is usually enough.
- B
The lookup file is stored in the wrong directory but referenced correctly
Why wrong: If referenced correctly, location is fine; might be in default vs local.
- C
The lookup field is case-sensitive and the data doesn't match
Why wrong: Case sensitivity is a matching issue, not a configuration issue.
- D
The lookup table is defined in transforms.conf incorrectly
Both props.conf and transforms.conf must be configured correctly.
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.
SPLK-1002 Using Fields and Lookups Practice Question
This SPLK-1002 practice question tests your understanding of using fields and lookups. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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?
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
Option D is correct because 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.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that 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.
Detailed technical explanation
How to think about this question
Under the hood, Splunk processes automatic lookups by reading the [automatic_lookup] stanza in props.conf, which references a stanza name in transforms.conf. The transforms.conf stanza must define the lookup_table (filename), input_fields (source fields), and output_fields (target fields). A common subtlety is that the lookup file must be in the lookups directory of the same app that contains the transforms.conf, or Splunk will silently fail to load it. In real-world scenarios, administrators often forget to add the transforms.conf stanza or misname the lookup_table filename, causing the automatic lookup to be ignored without any visible error in the UI.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the SPLK-1002 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Using Fields and Lookups — study guide chapter
Learn the concepts, then practise the questions
- →
Using Fields and Lookups practice questions
Targeted practice on this topic area only
- →
All SPLK-1002 questions
510 questions across all exam domains
- →
Splunk Core Certified User SPLK-1002 study guide
Full concept coverage aligned to exam objectives
- →
SPLK-1002 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SPLK-1002 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Splunk Basics and Interface Navigation practice questions
Practise SPLK-1002 questions linked to Splunk Basics and Interface Navigation.
Basic Searching and Transforming Commands practice questions
Practise SPLK-1002 questions linked to Basic Searching and Transforming Commands.
Using Fields and Lookups practice questions
Practise SPLK-1002 questions linked to Using Fields and Lookups.
Creating Reports, Dashboards and Visualizations practice questions
Practise SPLK-1002 questions linked to Creating Reports, Dashboards and Visualizations.
Data Models and Best Practices practice questions
Practise SPLK-1002 questions linked to Data Models and Best Practices.
SPLK-1002 fundamentals practice questions
Practise SPLK-1002 questions linked to SPLK-1002 fundamentals.
SPLK-1002 scenario practice questions
Practise SPLK-1002 questions linked to SPLK-1002 scenario.
SPLK-1002 troubleshooting practice questions
Practise SPLK-1002 questions linked to SPLK-1002 troubleshooting.
Practice this exam
Start a free SPLK-1002 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SPLK-1002 question test?
Using Fields and Lookups — This question tests Using Fields and Lookups — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The lookup table is defined in transforms.conf incorrectly — Option D is correct because 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.
What should I do if I get this SPLK-1002 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more ways this is tested on SPLK-1002
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: Option D is correct because 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.
Last reviewed: Jun 24, 2026
This SPLK-1002 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-1002 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.