SPLK-1002 Advanced Visualization and Lookups Practice Question
Exhibit
transforms.conf: [lookup_user_info] filename = user_info.csv max_matches = 1 default_match = UNKNOWN user_info.csv headers: User_ID, Department Events have field: user_id (lowercase)
Refer to the exhibit. The lookup 'lookup_user_info' is used in a search: `| lookup lookup_user_info user_id OUTPUT department`. Users report that many events show 'UNKNOWN' as department even though the user_id exists in the CSV. What is the most likely cause?
⚠ Common exam trap
Watch out — candidates often assume Splunk field matching is case-insensitive, but Splunk treats field names in lookups as case-sensitive, leading to silent failures when the CSV header case does not match the event field case.
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 field name in the CSV header is 'User_ID' (capital U), while the event field is 'user_id' (lowercase). Splunk field matching is case-sensitive.
Splunk lookups are case-sensitive when matching field values. The exhibit shows the CSV header uses 'User_ID' (capital U), while the search references 'user_id' (lowercase). Since the lookup field name in the definition must exactly match the event field name, the mismatch causes the lookup to fail, returning 'UNKNOWN' for all events even when the user_id exists in the CSV.
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 file is not distributed to all indexers.
Why it's wrong here
There is no evidence of distribution issues; the exhibit does not mention indexing peers.
- ✓
The field name in the CSV header is 'User_ID' (capital U), while the event field is 'user_id' (lowercase). Splunk field matching is case-sensitive.
Why this is correct
Splunk field names are case-sensitive; the mismatch causes no match, returning the default 'UNKNOWN'.
- ✗
The match_type is not specified, defaulting to EXACT, but the CSV contains case variations.
Why it's wrong here
Case variations are handled by exact matching but the field name mismatch (case) is the issue.
- ✗
The max_matches should be set to 0.
Why it's wrong here
max_matches=0 would return all matches, but doesn't address the case sensitivity issue.
- ✗
The lookup definition is missing the default_match setting, which should be set to 'no_match'.
Why it's wrong here
The default_match is already set to 'UNKNOWN'; changing it won't fix the mismatch.
Go deeper
Related to this question
About these practice questions
This SPLK-1002 question is part of Courseiva's 475-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.