SPLK-1002 Advanced Visualization and Lookups Practice Question
A company's security team uses Splunk to monitor firewall logs. They have a lookup file named 'threat_intel.csv' containing 10,000 IP addresses classified by threat level. The lookup is used in a dashboard that shows the number of blocked connections from high-threat IPs over the past 24 hours. Recently, the dashboard has become slow, taking over 30 seconds to load. The lookup file is updated every 15 minutes via a script that replaces the entire file. The search currently uses: `index=firewall | lookup threat_intel.csv src_ip OUTPUT threat_level | where threat_level="high" | stats count`. Which of the following is the MOST efficient way to improve dashboard performance?
⚠ Common exam trap
Candidates often assume reducing the time range or caching will fix performance, but the real bottleneck is the file-based lookup's linear scan of 10,000 rows, which is only resolved by switching to an indexed KV Store collection.
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
✓
Convert the lookup to a KV store collection with an index on src_ip.
Converting the lookup to a KV Store collection with an index on `src_ip` allows Splunk to perform efficient key-value lookups without loading the entire 10,000-row CSV into memory on every search. The KV Store uses an indexed data structure, which dramatically reduces lookup time compared to a file-based lookup that must be fully scanned each time, especially when the file is replaced every 15 minutes and the search runs over a 24-hour window.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Restrict the search to a smaller time range, such as the last hour.
Why it's wrong here
Reducing the time range may decrease data volume but does not address the lookup performance bottleneck.
- ✗
Use the lookup with local=t to force it to run on the search head only.
Why it's wrong here
Running locally may reduce network overhead but does not address the underlying lookup file contention.
- ✓
Convert the lookup to a KV store collection with an index on src_ip.
Why this is correct
KV store handles concurrent reads and writes efficiently, ideal for frequently updated lookups.
- ✗
Increase the lookup cache size in limits.conf.
Why it's wrong here
Caching may help but the frequent file replacement (every 15 minutes) invalidates the cache, limiting its effectiveness.
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.