SPLK-1002 Transactions and Event Correlation Practice Question
Consider the following search: 'index=web | transaction sessionid maxspan=30m | where eventcount > 5 | stats avg(duration)'. An analyst notices that the search takes a long time and uses excessive memory. Which change would most likely improve performance?
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
✓
Use the stats command with values(sessionid) instead of transaction.
Using the stats command with values(sessionid) replaces the resource-intensive transaction command. The transaction command buffers all events belonging to the same session within the maxspan window, consuming memory and CPU. The stats command processes events in a more efficient streaming manner, reducing resource usage. Moreover, by using stats, the search can directly aggregate events by sessionid without requiring a maxspan window or a subsequent where clause, thereby improving performance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Change maxspan to 1h to allow more events.
Why it's wrong here
Increasing maxspan to 1h would allow more events to be grouped into each transaction, which actually increases memory usage and worsens performance, not improves it.
- ✓
Use the stats command with values(sessionid) instead of transaction.
Why this is correct
Using the stats command with values(sessionid) is a more efficient alternative to transaction because it processes events in a streaming manner without buffering all events of a session in memory. This reduces memory and CPU usage significantly, leading to better performance. While the original query calculates average duration, the stats approach can achieve similar results with less resource consumption.
- ✗
Remove the where clause and use stats after transaction.
Why it's wrong here
Removing the where clause would not help performance; the transaction command is still used, which is the main performance bottleneck. The where clause filters out small transactions, which actually reduces the data processed later.
- ✗
Add a filter before transaction to reduce events.
Why it's wrong here
Adding a filter before transaction could reduce the number of events entering the transaction command, which would improve performance, but it is not the most effective change. Using stats instead of transaction is a more direct and significant improvement.
Go deeper
Related to this question
About these practice questions
One of 475 original SPLK-1002 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.