The answer is a mismatch between the lookup key field name in the event and the field name in the lookup file. When you use the lookup command in Splunk, it attempts to match a field from your search results—the lookup key—against a corresponding field in the lookup table. If these field names do not match exactly, even due to a simple typo or case difference, no match occurs, and the output field like 'status' remains empty despite the lookup file containing all possible mappings. On the Splunk Core Certified User SPLK-1002 exam, this question tests your understanding of how lookups perform field-based joins, and a common trap is assuming the lookup file’s data is missing rather than recognizing a key field name mismatch. A helpful memory tip: think of the lookup key as a key to a lock—if the key’s shape (field name) doesn’t perfectly fit the lock (lookup file field), the door stays shut, leaving your enrichment empty.
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.
A search uses a lookup to enrich results with a field 'status'. After the lookup, some events have empty status values. The lookup file contains a mapping for all possible status codes. What is a likely reason for empty values?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The lookup field name in the event does not match the lookup key.
Option D is correct because the lookup command matches a field in the event (the lookup key) against a field in the lookup file. If the field name in the event does not exactly match the lookup key field name in the lookup file, no match occurs, and the output field (e.g., 'status') remains empty. This is a common misconfiguration when the lookup key field is misspelled or has a different case.
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 events are not indexed.
Why it's wrong here
If events are not indexed, they wouldn't appear in search results at all.
✗
The lookup command uses output_fields incorrectly.
Why it's wrong here
Incorrect output_fields may cause no output, but typically would not cause empty fields.
✗
The lookup file has duplicate keys.
Why it's wrong here
Duplicates would cause multiple matches, not empty values.
✓
The lookup field name in the event does not match the lookup key.
Why this is correct
Mismatch prevents matching, resulting in no enrichment.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Splunk often tests the distinction between a lookup that returns no match (empty values) versus a lookup that fails due to syntax or data issues, and candidates mistakenly blame duplicate keys or output_fields instead of recognizing a key field mismatch.
Trap categories for this question
Command / output trap
Incorrect output_fields may cause no output, but typically would not cause empty fields.
Detailed technical explanation
How to think about this question
The lookup command performs a left join-like operation: for each event, it searches the lookup file for a row where the key field matches the event's field value. If no match is found, the output fields are set to null (empty). This behavior is analogous to an SQL LEFT JOIN where the right table has no matching row. In Splunk, the lookup file is typically a CSV or KV store, and the key field must be an exact string match (case-sensitive by default).
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 — 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 field name in the event does not match the lookup key. — Option D is correct because the lookup command matches a field in the event (the lookup key) against a field in the lookup file. If the field name in the event does not exactly match the lookup key field name in the lookup file, no match occurs, and the output field (e.g., 'status') remains empty. This is a common misconfiguration when the lookup key field is misspelled or has a different case.
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 →
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. Refer to the exhibit. The search returns no results from the lookup. What is the most likely issue?
medium
A.The FIELDALIAS syntax is incorrect
B.The lookup table is not defined in transforms.conf
C.The lookup file 'error_codes.csv' does not exist
✓ D.The lookup command references 'error_id' but the alias changed the field to 'error_code'
Why D: The correct answer is D because the search uses `lookup error_codes.csv error_id` but the FIELDALIAS in props.conf has renamed the field `error_id` to `error_code`. Since the lookup command references the original field name `error_id`, which no longer exists in the events after alias processing, the lookup cannot match any values and returns no results.
Last reviewed: Jun 30, 2026
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.
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.