- A
The props.conf LOOKUP-1 syntax is incorrect; the definition should be `LOOKUP-1 = devices` only, and the match/output fields should be defined in transforms.conf.
In props.conf, after LOOKUP-<class> = you just specify the lookup name; field mappings go in transforms.conf under that stanza.
- B
The CSV file is too large and the lookup is not being loaded.
Why wrong: Size doesn't prevent loading; it might be slow but would still populate fields.
- C
The 'ip' field is not properly extracted from the sourcetype.
Why wrong: The problem states events have the 'ip' field.
- D
The lookup file is not accessible from the search head because it is stored on a different host.
Why wrong: If the search head is not the indexer, the lookup must be on the search head or in a shared location.
Quick Answer
The answer is that the props.conf LOOKUP-1 syntax is incorrect because it includes the match and output fields directly. The correct configuration for automatic lookup requires that props.conf only reference the lookup name, as in `LOOKUP-1 = devices`, while the match field (`ip`) and output fields (`building`, `floor`) must be defined exclusively in the transforms.conf stanza under `[devices]` using `external_type = csv` and `match_type = WILDCARD(ip)`. This tests your understanding of how Splunk separates lookup definition from field mapping, a common trap on the SPLK-1002 exam where candidates mistakenly combine all parameters in props.conf. The admin’s error causes Splunk to ignore the lookup entirely, so no fields are added to events. Remember the memory tip: “props only names the lookup; transforms does the mapping work.”
SPLK-1002 Using Fields and Lookups Practice Question
This SPLK-1002 practice question tests your understanding of using fields and lookups. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A Splunk admin configured a CSV-based lookup to map device IP addresses to location data. The lookup 'devices.csv' has columns 'ip', 'building', 'floor'. In props.conf, they set: `LOOKUP-1 = devices ip OUTPUT building floor`. In transforms.conf: `[devices] filename = devices.csv`. The search over sourcetype 'network_logs' returns events with the 'ip' field, but 'building' and 'floor' are missing. The admin confirms the CSV file exists and has data. What is the most likely issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 props.conf LOOKUP-1 syntax is incorrect; the definition should be `LOOKUP-1 = devices` only, and the match/output fields should be defined in transforms.conf.
Option A is correct because the `LOOKUP-1` definition in `props.conf` incorrectly includes the match and output fields. The correct syntax is `LOOKUP-1 = devices` only, with the match field (`ip`) and output fields (`building`, `floor`) defined in the `transforms.conf` stanza under `[devices]` using `external_type = csv`, `filename = devices.csv`, `match_type = WILDCARD(ip)`, and `default_match = NONE`. The admin's syntax causes Splunk to ignore the lookup configuration entirely, so no fields are added.
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.
- ✓
The props.conf LOOKUP-1 syntax is incorrect; the definition should be `LOOKUP-1 = devices` only, and the match/output fields should be defined in transforms.conf.
Why this is correct
In props.conf, after LOOKUP-<class> = you just specify the lookup name; field mappings go in transforms.conf under that stanza.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The CSV file is too large and the lookup is not being loaded.
Why it's wrong here
Size doesn't prevent loading; it might be slow but would still populate fields.
- ✗
The 'ip' field is not properly extracted from the sourcetype.
Why it's wrong here
The problem states events have the 'ip' field.
- ✗
The lookup file is not accessible from the search head because it is stored on a different host.
Why it's wrong here
If the search head is not the indexer, the lookup must be on the search head or in a shared location.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the `props.conf` LOOKUP syntax with the `| lookup` SPL command, mistakenly thinking match and output fields can be specified inline in `props.conf`.
Detailed technical explanation
How to think about this question
In Splunk, the `LOOKUP-<name>` attribute in `props.conf` only specifies the lookup table name (the stanza name in `transforms.conf`). The match and output fields must be defined in `transforms.conf` using `external_type`, `filename`, `match_type`, and `max_matches` (optional). If the `LOOKUP-1` line includes extra tokens like `ip OUTPUT building floor`, Splunk treats the entire string as the lookup name, fails to find a matching stanza, and silently skips the lookup. This is a common pitfall because the syntax resembles the `| lookup` command in SPL, but in `props.conf` it is strictly a reference to the transforms stanza.
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 props.conf LOOKUP-1 syntax is incorrect; the definition should be `LOOKUP-1 = devices` only, and the match/output fields should be defined in transforms.conf. — Option A is correct because the `LOOKUP-1` definition in `props.conf` incorrectly includes the match and output fields. The correct syntax is `LOOKUP-1 = devices` only, with the match field (`ip`) and output fields (`building`, `floor`) defined in the `transforms.conf` stanza under `[devices]` using `external_type = csv`, `filename = devices.csv`, `match_type = WILDCARD(ip)`, and `default_match = NONE`. The admin's syntax causes Splunk to ignore the lookup configuration entirely, so no fields are added.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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.