SPLK-1002 Advanced Searching and Statistics Practice Question
A large e-commerce company uses Splunk to monitor their web application. They have a query that uses the transaction command to group related events into transactions based on session ID and a 30-minute max pause. The query runs slowly and often times out. The environment has 10 indexers with 4 CPU cores each. The search is run over the last 7 days. Which of the following is the best course of action to improve performance?
⚠ Common exam trap
Splunk often tests the misconception that reducing the max pause or adding hardware (more indexers) is the best fix, when the real issue is replacing the inefficient `transaction` command with more scalable streaming commands like `stats` and `streamstats`.
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
✓
Replace the transaction command with a combination of stats and streamstats commands.
The `transaction` command is resource-intensive because it groups events by a field (session ID) and a max pause, requiring significant memory and processing to correlate events across the entire search time range. Replacing it with `stats` and `streamstats` is more efficient because `stats` can aggregate events by session ID without the overhead of transaction boundaries, and `streamstats` can compute running totals or windows within each session, leveraging distributed processing across indexers. This approach reduces memory pressure and avoids the timeout issue by using streaming operations that scale better with large datasets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the eval command to create a transaction ID field and then use stats to group events.
Why it's wrong here
Creating a transaction ID with eval does not handle pause-based grouping; stats alone cannot replicate transaction's logic without streamstats.
- ✗
Reduce the max pause to 15 minutes to limit the number of events in each transaction.
Why it's wrong here
This reduces transaction size but still uses the resource-intensive transaction command.
- ✓
Replace the transaction command with a combination of stats and streamstats commands.
Why this is correct
Using stats and streamstats is more efficient than transaction and can achieve similar grouping results.
- ✗
Increase the number of indexers to 20 to distribute the load.
Why it's wrong here
While more indexers can help, the bottleneck is likely the transaction command itself, not indexer capacity. This is costly and may not resolve the issue.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SPLK-1002 question from scratch — 475 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-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.