SPLK-1002 Transactions and Event Correlation Practice Question
Exhibit
Refer to the exhibit. ``` index=security sourcetype=linux_secure | eval session_id=if(like(_raw,"Accepted publickey"), _raw, null()) | transaction session_id maxpause=5m | table _time, session_id, duration ```
Refer to the exhibit. A security analyst runs this search to group SSH login events into sessions based on a session_id that is extracted only from 'Accepted publickey' events. However, the resulting transactions contain only the 'Accepted publickey' event and none of the subsequent commands or logouts. What is the most likely cause?
⚠ Common exam trap
Candidates often assume `maxpause` or timing is the culprit, but the real issue is that the `transaction` command requires all events in the group to share the same value for the specified field(s), and if the field is missing or null on other events, they cannot be correlated.
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 session_id field is only populated for the 'Accepted publickey' event, so other events have a different or null session_id and do not join the transaction.
The `transaction` command groups events by the `session_id` field. If `session_id` is only extracted from 'Accepted publickey' events (e.g., via a `rex` or `eval` command), subsequent commands and logout events will have a null or different `session_id`. Since `transaction` requires all events in the group to share the same `session_id` value, those other events cannot join the transaction, resulting in a transaction containing only the single 'Accepted publickey' event.
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 maxpause=5m is too short, causing the transaction to close before other events occur.
Why it's wrong here
Even if maxpause were longer, other events lack the session_id to join.
- ✓
The session_id field is only populated for the 'Accepted publickey' event, so other events have a different or null session_id and do not join the transaction.
Why this is correct
Only the start event gets a session_id; other events have null, so they are not grouped.
- ✗
The transaction command requires that all events have a non-null session_id to be grouped.
Why it's wrong here
Transaction groups events with the same session_id; null values are treated as a group, but only events with null session_id would group together.
- ✗
The sourcetype filter is too restrictive.
Why it's wrong here
The sourcetype is correctly set to linux_secure.
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.