The answer is `transaction by transaction_id`. This command is correct because it groups all events sharing the same `transaction_id` field value into a single transaction, regardless of time, which directly meets the requirement of correlating events across sourcetypes without time constraints. Unlike the `transaction` command with a `maxspan` or `maxpause` option, the bare `by` clause imposes no temporal boundaries, so every event from `web_access`, `auth_log`, and `app_log` that carries the same `transaction_id` is bundled together. On the Splunk SPLK-1003 exam, this question tests your understanding of how the `transaction` command behaves by default—many candidates mistakenly add a time window or use `stats values()` instead, but the key is that `transaction` without time limits creates a single event per unique field value. A helpful memory tip: think of `transaction by` as a "bucket without a clock"—it collects everything that matches, no matter when it happened.
SPLK-1003 Transactions and Event Correlation Practice Question
This SPLK-1003 practice question tests your understanding of transactions and event correlation. Compare every option against the stated constraints before choosing — the best answer satisfies all requirements, not just the most obvious one. 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 needs to correlate events from different sourcetypes (web_access, auth_log, app_log) that share a common 'transaction_id' field. Each transaction_id may appear many times across sourcetypes. The user wants to group all events with the same transaction_id into one transaction, without any time constraints. Which transaction command is most appropriate?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
transaction by transaction_id
Option A is correct because the `transaction` command with `by transaction_id` groups all events sharing the same `transaction_id` field value into a single transaction, with no default time constraints. This matches the requirement to correlate events across `web_access`, `auth_log`, and `app_log` sourcetypes without any time window restrictions.
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.
✓
transaction by transaction_id
Why this is correct
Correctly groups by the common field without time limits.
Related concept
Read the scenario before looking for a memorised answer.
✗
transaction by sourcetype transaction_id
Why it's wrong here
Multiple fields in 'by' clause would group by combination, not just transaction_id.
✗
transaction maxspan=1d by transaction_id
Why it's wrong here
Adds a time constraint that may split events that span more than a day.
✗
transaction startswith=* endswith=* by transaction_id
Why it's wrong here
Using wildcards for startswith/endswith is invalid and unnecessary.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often add unnecessary time constraints (like `maxspan=1d`) or marker arguments (`startswith`/`endswith`) when the requirement explicitly states no time constraints, or they incorrectly include `sourcetype` in the `by` clause, which would split transactions across sourcetypes instead of grouping them.
Detailed technical explanation
How to think about this question
The `transaction` command in Splunk uses a default `maxspan=-1` (no time limit) and `maxpause=-1` (no pause limit) when no time constraints are specified, allowing events to be grouped solely by the `by` fields. Under the hood, Splunk builds transactions by collecting all events that match the field values, and the resulting transaction contains all fields from all constituent events, enabling cross-sourcetype correlation for use cases like tracking a user's journey across web, authentication, and application logs.
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 by transaction_id — Option A is correct because the `transaction` command with `by transaction_id` groups all events sharing the same `transaction_id` field value into a single transaction, with no default time constraints. This matches the requirement to correlate events across `web_access`, `auth_log`, and `app_log` sourcetypes without any time window restrictions.
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 →
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.