SPLK-1002 Transactions and Event Correlation Practice Question
Exhibit
Refer to the exhibit. ``` index=main sourcetype=access_combined | transaction clientip maxspan=30m maxevents=5 | stats count by clientip ```
Refer to the exhibit. A Splunk user runs the search shown. The search returns results, but the user notices that some clientip values appear multiple times in the stats output, even though they should have been grouped into a single transaction. What is the most likely reason for this?
⚠ Common exam trap
Test-takers frequently assume `maxevents` only limits the number of events per transaction but forget that exceeding this limit causes the creation of additional transactions for the same grouping field, leading to duplicate identifiers in aggregated output.
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
✓
The maxevents option prevents more than 5 events from being grouped into one transaction, so additional events form separate transactions.
The `transaction` command's `maxevents` option limits the maximum number of events that can be grouped into a single transaction. When more than 5 events exist for a given `clientip`, the extra events cannot be included in the first transaction and instead form separate transactions, causing the same `clientip` to appear multiple times in the `stats` output.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The sourcetype filter is excluding some events.
Why it's wrong here
The sourcetype is specified correctly; no exclusion is implied.
- ✗
The stats command is not correctly summing the counts.
Why it's wrong here
stats count by clientip is correct; the issue is upstream.
- ✗
The maxspan is too short to capture all events for each clientip.
Why it's wrong here
maxspan=30m may be insufficient, but the issue is more likely maxevents.
- ✓
The maxevents option prevents more than 5 events from being grouped into one transaction, so additional events form separate transactions.
Why this is correct
maxevents=5 limits the number of events per transaction, causing fragmentation.
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.