SPLK-1001 Using Fields and Lookups Practice Question
A company uses Splunk to monitor its e-commerce platform. They have a lookup file (user_geo.csv) that maps user_id to city, state, and country. The search `index=ecommerce sourcetype=access_combined | lookup user_geo user_id OUTPUT city, state, country | stats count by country` is used to analyze user locations. Recently, the lookup stopped returning results for many events. The lookup file is updated daily via a script that pulls from an external API. The Splunk administrator checks the lookup definition and finds that the lookup is configured to automatically reload every 24 hours. The last successful load was 23 hours ago. The events still contain the 'user_id' field. Which course of action should the administrator take first?
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
✓
Manually reload the lookup using the `| inputlookup user_geo.csv | outputlookup user_geo.csv` technique or the UI reload button.
The correct first action is to manually reload the lookup (Option C). Although the lookup is set to auto-reload every 24 hours, the last successful load was 23 hours ago and the lookup file is updated daily. The timing gap means the lookup might still contain old data until the next scheduled reload. Manually reloading forces the lookup to load the latest file immediately. Option A is unnecessary because the search already uses `user_id` and results were working before; the `user_id` field is present. Option B (increasing reload frequency) would only help if the issue were timing, but the immediate fix is to manually reload. Option D (using `inputlookup`) would load the lookup as events, not enrich the search, so it would not solve the enrichment problem.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Verify that the events contain the `user_id` field by running `index=ecommerce sourcetype=access_combined | head 10`.
Why it's wrong here
The stem states the events still have user_id, so this check is unnecessary and wastes time.
- ✗
Increase the auto-reload interval to 12 hours to ensure more frequent updates.
Why it's wrong here
The issue is that the last reload was 23 hours ago and an update occurred after that. The auto-reload will eventually happen, but the immediate fix is to manually reload.
- ✓
Manually reload the lookup using the `| inputlookup user_geo.csv | outputlookup user_geo.csv` technique or the UI reload button.
Why this is correct
A manual reload forces Splunk to use the latest lookup data, which may have been updated after the last automatic reload.
- ✗
Modify the search to use `| inputlookup user_geo.csv` instead of the lookup command.
Why it's wrong here
`inputlookup` returns the lookup table as events, not as an enrichment; this would change the analysis completely.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SPLK-1001 question from scratch — 502 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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-1001 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-1001 exam.