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.
Exhibit
Refer to the exhibit.
# /opt/splunk/etc/system/local/transforms.conf
[user_lookup]
filename = users.csv
match_type = WILDCARD(user_name)
# /opt/splunk/etc/system/local/props.conf
[source::/var/log/auth.log]
LOOKUP-user = user_lookup user_name AS username OUTPUTNEW department
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?
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.
Exhibit
Refer to the exhibit.
# /opt/splunk/etc/system/local/transforms.conf
[user_lookup]
filename = users.csv
match_type = WILDCARD(user_name)
# /opt/splunk/etc/system/local/props.conf
[source::/var/log/auth.log]
LOOKUP-user = user_lookup user_name AS username OUTPUTNEW department
A
The LOOKUP- stanza requires a numeric priority.
Why wrong: Priority is optional and not required.
B
The transforms.conf file is not in the correct directory.
Why wrong: system/local is a valid directory for custom configs.
C
The user_lookup.csv file does not exist in the lookups directory.
Why wrong: The file might exist; the issue is not file existence.
D
The match_type syntax is incorrect and the field mapping is mismatched.
WILDCARD expects quotes and the field names must match.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The match_type syntax is incorrect and the field mapping is mismatched.
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.
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 LOOKUP- stanza requires a numeric priority.
Why it's wrong here
Priority is optional and not required.
✗
The transforms.conf file is not in the correct directory.
Why it's wrong here
system/local is a valid directory for custom configs.
✗
The user_lookup.csv file does not exist in the lookups directory.
Why it's wrong here
The file might exist; the issue is not file existence.
✓
The match_type syntax is incorrect and the field mapping is mismatched.
Why this is correct
WILDCARD expects quotes and the field names must match.
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume the lookup file is missing or misconfigured (options A, B, or C) when the real issue is a subtle mismatch in field names or match_type syntax, which Splunk does not flag with an obvious error but simply returns no results.
Detailed technical explanation
How to think about this question
Automatic lookups in Splunk rely on the transforms.conf file to define the lookup table filename, match fields, and output fields. The match_type setting (e.g., EXACT, WILDCARD, CIDR) must align with the data type and format of the source field; for example, using WILDCARD when the source field contains exact values will cause no matches. Additionally, the field mapping in the lookup stanza must match the CSV header names exactly, including case sensitivity, or Splunk will not populate the output fields.
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 match_type syntax is incorrect and the field mapping is mismatched. — 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.
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 →
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 admin notices that a lookup is not matching fields correctly. The lookup file has a header row with field names. The search uses `lookup usernames.csv user_id OUTPUT username`. Some events have `user_id` values that exist in the lookup but no match occurs. What is the most likely cause?
hard
A.The lookup file is missing the header row.
✓ B.The lookup file has leading or trailing spaces in the matching column.
C.The lookup is case-sensitive and the search field has different case.
D.The lookup file has quotes around field values that are not stripped.
Why B: Option B is correct because leading or trailing spaces in the lookup file's matching column prevent exact string matching. When Splunk performs a lookup, it compares the field value from the event with the lookup file value using an exact string match. If the lookup file contains spaces (e.g., '123 ' instead of '123'), the values will not match even though the event's `user_id` appears correct. This is a common data quality issue in CSV files.
Variation 2. An admin notices that a lookup is not returning any results for some events even though matching keys exist. What is the most likely cause?
medium
A.The lookup field name is different from the event field name
B.The lookup is defined with the wrong field order
C.The time range of the search is too narrow
✓ D.The lookup is case-sensitive and the key values have different cases
Why D: Option D is correct because lookups in Splunk are case-sensitive by default. If the lookup file contains key values in a different case (e.g., 'ABC') than the event field values (e.g., 'abc'), the lookup will not match, even though the underlying data is logically equivalent. This is a common cause of lookup failures when the data sources have inconsistent casing.
Variation 3. 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?
hard
A.Splunk needs to be restarted after adding the automatic lookup
B.The lookup file is stored in the wrong directory but referenced correctly
C.The lookup field is case-sensitive and the data doesn't match
✓ D.The lookup table is defined in transforms.conf incorrectly
Why D: 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.
Variation 4. A Splunk administrator notices that a lookup definition named 'assets' is not returning any results in searches even though the CSV file exists and has data. The lookup definition uses the filename 'assets.csv' and the matching field 'ip' matches the event field 'dest_ip'. The search query 'index=main | lookup assets ip AS dest_ip OUTPUT asset_name' returns no asset_name values. What is the most likely cause?
hard
A.The lookup command syntax is incorrect; it should be 'lookup assets dest_ip AS ip'
B.The lookup command is missing the 'name' field; it should be 'lookup assets name AS ip'
✓ C.The user may not have permissions to access the lookup definition; check the knowledge object permissions
D.The command should use 'inputlookup' instead of 'lookup' to load the CSV data
Why C: Option C is correct because the lookup definition exists and the CSV file has data, but the search returns no results, indicating a permissions issue. In Splunk, knowledge objects like lookups have permissions that restrict which roles can use them; if the user's role lacks read access to the 'assets' lookup definition, the lookup command will silently return no results. The syntax and command structure are otherwise correct, so the most likely cause is that the lookup definition's permissions are not set to allow the user's role.
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.