The correct transaction syntax is `transaction startswith="GET" endswith="POST"`. This works because the `transaction` command groups sequential events into a single logical unit, and the `startswith` and `endswith` arguments explicitly define the boundary events that open and close the transaction—here, a GET request marks the beginning of a user visit, and a POST request marks its end. On the Splunk SPLK-1003 exam, this question tests your understanding of how to implement sessionization without overcomplicating the syntax; a common trap is adding unnecessary options like `maxevents` or `by` fields when the basic boundary logic is all that’s required. To remember the correct transaction syntax with startswith and endswith, think of it as a sandwich: the startswith is the top slice of bread, the endswith is the bottom slice, and all events in between are the filling—no extra ingredients needed for a simple visit.
SPLK-1003 Transactions and Event Correlation Practice Question
This SPLK-1003 practice question tests your understanding of transactions and event correlation. 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 Splunk user wants to group web server logs into transactions representing a single user visit, where a visit starts with a 'GET' request and ends with a 'POST' request. Which transaction command syntax correctly implements this logic?
Why wrong: maxevents=2 limits to two events per transaction, but the visit may have more events.
B
transaction startswith="POST" endswith="GET"
Why wrong: This would start with POST and end with GET, opposite of the requirement.
C
transaction startswith="GET" endswith="POST"
Correctly sets start and end conditions.
D
transaction by src_ip startswith="GET" endswith="POST"
Why wrong: This is valid but adds an unnecessary 'by' clause if not needed; however it is not incorrect. But the simplest correct answer without extra fields is A.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
transaction startswith="GET" endswith="POST"
Option C is correct because the `transaction` command with `startswith="GET"` and `endswith="POST"` groups events into a single transaction that begins with a GET request and ends with a POST request, which matches the requirement for a user visit. The `startswith` and `endswith` arguments define the boundary events for the transaction, and no additional constraints like `maxevents` or `by` fields are needed to implement the basic logic.
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.
maxevents=2 limits to two events per transaction, but the visit may have more events.
✗
transaction startswith="POST" endswith="GET"
Why it's wrong here
This would start with POST and end with GET, opposite of the requirement.
✓
transaction startswith="GET" endswith="POST"
Why this is correct
Correctly sets start and end conditions.
Related concept
Read the scenario before looking for a memorised answer.
✗
transaction by src_ip startswith="GET" endswith="POST"
Why it's wrong here
This is valid but adds an unnecessary 'by' clause if not needed; however it is not incorrect. But the simplest correct answer without extra fields is A.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Splunk often tests the misconception that `maxevents` is required to limit transaction size, but here the trap is that candidates add unnecessary constraints (like `maxevents=2` or `by src_ip`) that alter the intended grouping logic, or they reverse the `startswith` and `endswith` values, failing to match the required visit flow.
Detailed technical explanation
How to think about this question
The `transaction` command in Splunk uses a state-machine approach to group events: it starts a new transaction when it encounters an event matching `startswith`, then accumulates all subsequent events until it finds an event matching `endswith`. Under the hood, Splunk evaluates these conditions against the raw event text or a specified field, and the transaction is closed either by the endswith event or by other constraints like `maxspan` or `maxpause`. In real-world web server logs, a user visit may include multiple GET requests (e.g., for images, CSS, JavaScript) and a final POST (e.g., form submission), so limiting to two events or adding a `by` clause could break the transaction grouping.
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-1003 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.
Transactions and Event Correlation — This question tests Transactions and Event Correlation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: transaction startswith="GET" endswith="POST" — Option C is correct because the `transaction` command with `startswith="GET"` and `endswith="POST"` groups events into a single transaction that begins with a GET request and ends with a POST request, which matches the requirement for a user visit. The `startswith` and `endswith` arguments define the boundary events for the transaction, and no additional constraints like `maxevents` or `by` fields are needed to implement the basic logic.
What should I do if I get this SPLK-1003 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 →
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. A security team needs to group all login events from the same user session. Events include 'login' and 'logout' with a common session_id field. Which command should be used to combine these events into a single event per session?
easy
A.join session_id
B.stats by session_id
✓ C.transaction session_id
D.append session_id
Why C: The `transaction` command is designed to group related events based on common fields and time constraints, making it ideal for combining login and logout events by session_id.
Last reviewed: Jun 30, 2026
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.
This SPLK-1003 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-1003 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.