- A
Split the KV Store into multiple smaller KV Stores based on threat_type
Why wrong: This adds complexity and might not improve performance if each lookup still queries a large collection.
- B
Convert the KV Store to a CSV file and use the lookup command
Why wrong: CSV lookups are loaded into memory and can be slow for large files, and updates are not as flexible.
- C
Add an index on the 'indicator' field in the KV Store collection to speed up lookup queries
Indexing the lookup field reduces search time when matching events.
- D
Increase the memory allocation for the Splunk search head
Why wrong: While more memory might help, the root cause is lack of indexing on the KV Store field.
Quick Answer
The answer is to add an index on the 'indicator' field in the KV Store collection. This works because an index creates a B-tree data structure that allows Splunk to locate matching entries in logarithmic time rather than scanning every row, which is why performance degrades sharply beyond 100,000 entries. On the SPLK-1002 exam, this tests your understanding that KV Store lookups are essentially database queries, and indexing is the standard way to improve KV Store lookup performance without sacrificing the ability to update frequently, since indexes are maintained automatically on writes. A common trap is to assume that increasing hardware resources or caching the entire lookup will solve the problem, but those approaches either don't scale or prevent real-time updates. Remember the mnemonic: "Index the key you seek, or the search will be weak."
SPLK-1002 Using Fields and Lookups Practice Question
This SPLK-1002 practice question tests your understanding of using fields and lookups. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 security team uses a KV Store lookup to track threat intelligence indicators (IPs, domains) with a field 'indicator' and a field 'threat_type'. They regularly update the KV Store with new indicators. The team notices that searches using the lookup are very slow when the KV Store contains over 100,000 entries. They want to improve lookup performance without losing the ability to update frequently. Which approach should they take?
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
Add an index on the 'indicator' field in the KV Store collection to speed up lookup queries
Option C is correct because adding an index on the 'indicator' field in the KV Store collection allows Splunk to perform faster lookups by using a B-tree or similar index structure, reducing the need for a full collection scan. This directly addresses the performance degradation seen with over 100,000 entries while still supporting frequent updates, as indexes are maintained dynamically.
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.
- ✗
Split the KV Store into multiple smaller KV Stores based on threat_type
Why it's wrong here
This adds complexity and might not improve performance if each lookup still queries a large collection.
- ✗
Convert the KV Store to a CSV file and use the lookup command
Why it's wrong here
CSV lookups are loaded into memory and can be slow for large files, and updates are not as flexible.
- ✓
Add an index on the 'indicator' field in the KV Store collection to speed up lookup queries
Why this is correct
Indexing the lookup field reduces search time when matching events.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Increase the memory allocation for the Splunk search head
Why it's wrong here
While more memory might help, the root cause is lack of indexing on the KV Store field.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Splunk often tests the misconception that splitting data or increasing hardware resources is the primary solution for performance issues, when in fact proper indexing is the correct database optimization technique for KV Store lookups.
Detailed technical explanation
How to think about this question
Splunk KV Store uses MongoDB under the hood, and adding an index on the 'indicator' field creates a B-tree index that allows logarithmic-time lookups instead of linear scans. This is especially critical when the KV Store exceeds 100,000 entries, as MongoDB's default behavior without an index is to perform a collection scan. In real-world scenarios, threat intelligence feeds can grow rapidly, and indexing ensures that lookups remain fast even as the dataset scales, without requiring manual sharding or static exports.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Using Fields and Lookups practice questions
Targeted practice on this topic area only
- →
All SPLK-1002 questions
510 questions across all exam domains
- →
Splunk Core Certified User SPLK-1002 study guide
Full concept coverage aligned to exam objectives
- →
SPLK-1002 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SPLK-1002 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Splunk Basics and Interface Navigation practice questions
Practise SPLK-1002 questions linked to Splunk Basics and Interface Navigation.
Basic Searching and Transforming Commands practice questions
Practise SPLK-1002 questions linked to Basic Searching and Transforming Commands.
Using Fields and Lookups practice questions
Practise SPLK-1002 questions linked to Using Fields and Lookups.
Creating Reports, Dashboards and Visualizations practice questions
Practise SPLK-1002 questions linked to Creating Reports, Dashboards and Visualizations.
Data Models and Best Practices practice questions
Practise SPLK-1002 questions linked to Data Models and Best Practices.
SPLK-1002 fundamentals practice questions
Practise SPLK-1002 questions linked to SPLK-1002 fundamentals.
SPLK-1002 scenario practice questions
Practise SPLK-1002 questions linked to SPLK-1002 scenario.
SPLK-1002 troubleshooting practice questions
Practise SPLK-1002 questions linked to SPLK-1002 troubleshooting.
Practice this exam
Start a free SPLK-1002 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SPLK-1002 question test?
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: Add an index on the 'indicator' field in the KV Store collection to speed up lookup queries — Option C is correct because adding an index on the 'indicator' field in the KV Store collection allows Splunk to perform faster lookups by using a B-tree or similar index structure, reducing the need for a full collection scan. This directly addresses the performance degradation seen with over 100,000 entries while still supporting frequent updates, as indexes are maintained dynamically.
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 →
Same concept, more angles
1 more ways this is tested on SPLK-1002
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. Your team uses a large CSV lookup 'users.csv' with 200,000 rows. When running searches that use this lookup via the lookup command, performance is slow. Which action would most improve performance?
medium- A.Switch to an external lookup that queries a database
- B.Increase the lookup timeout value
- ✓ C.Add an index to the lookup file by converting to KV Store
- D.Increase the max_matches setting for the lookup
Why C: Option B is correct because creating an index on the lookup fields (like using a KV Store or using a time-based lookup with indexed fields) can speed up matching. Alternatively, filtering the lookup before joining reduces rows processed. Option A is wrong because maxmatches is only useful if there are multiple matches. Option C is wrong because changing to external lookup adds overhead. Option D is wrong because increasing timeout doesn't improve performance.
Last reviewed: Jun 30, 2026
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.