- A
The `amount<50` filter is applied before the transaction, which excludes amounts exactly $50.
Why wrong: The filter is correct; amounts under $50 are included.
- B
The search lacks a `fields` command to include `user_id`, so the transaction fails.
Why wrong: `user_id` is implicitly available.
- C
The `maxspan=1h` is too short; users might spread transactions over more than 1 hour.
Why wrong: The pattern is within 1 hour, so it should capture.
- D
The `where sum(amount) > 200` does not work as expected because `sum()` is not an aggregation function in that context; you need to use `stats sum(amount)` or `eval total=mvsum(amount)` first.
`sum()` in `where` does not aggregate multivalue fields; it returns the sum of the first value.
Quick Answer
The answer is that the search fails because `sum(amount)` in the `where` clause cannot aggregate a multivalue field created by the `transaction` command. When you use `transaction user_id maxspan=1h`, Splunk groups events into a single result where the `amount` field becomes a multivalue list of all individual amounts. The `where` clause does not natively sum multivalue fields; instead, you must first compute the total with `eval total=mvsum(amount)` and then filter with `where total > 200`. This question tests your understanding of how the `transaction` command differs from `stats` on the Splunk Core Certified Power User SPLK-1003 exam—a common trap is assuming `sum()` works like SQL aggregation in a `where` clause. Remember the key distinction: `transaction` creates multivalue fields, while `stats` produces single-value aggregations. A useful memory tip is "transaction makes lists, stats makes totals"—so always use `mvsum()` or `stats sum()` to sum after a transaction.
SPLK-1003 Transactions and Event Correlation Practice Question
This SPLK-1003 practice question tests your understanding of transactions and event correlation. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 financial services company uses Splunk to detect fraudulent transactions. Each transaction event has fields: `user_id`, `amount`, `merchant`, `timestamp`. The fraud detection team wants to identify users who make multiple small transactions (under $50) totaling over $200 within a 1-hour window, which may indicate testing stolen credit cards. They write the following search:
`index=transactions sourcetype=payment amount<50 | transaction user_id maxspan=1h | where sum(amount) > 200`
This search runs but returns no results, even though manual inspection shows users with such patterns. What is the primary reason the search fails?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"primary"Why it matters: Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
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 `where sum(amount) > 200` does not work as expected because `sum()` is not an aggregation function in that context; you need to use `stats sum(amount)` or `eval total=mvsum(amount)` first.
Option D is correct because the `transaction` command creates a single multivalue field `amount` containing all amounts from the grouped events. The `where` clause cannot directly aggregate multivalue fields with `sum()`; it requires an explicit `eval` to compute the sum (e.g., `eval total=mvsum(amount)`) or a `stats` command. Without this, the `where` clause evaluates `sum(amount)` as a string operation or fails silently, returning no results.
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.
- ✗
The `amount<50` filter is applied before the transaction, which excludes amounts exactly $50.
Why it's wrong here
The filter is correct; amounts under $50 are included.
- ✗
The search lacks a `fields` command to include `user_id`, so the transaction fails.
Why it's wrong here
`user_id` is implicitly available.
- ✗
The `maxspan=1h` is too short; users might spread transactions over more than 1 hour.
Why it's wrong here
The pattern is within 1 hour, so it should capture.
- ✓
The `where sum(amount) > 200` does not work as expected because `sum()` is not an aggregation function in that context; you need to use `stats sum(amount)` or `eval total=mvsum(amount)` first.
Why this is correct
`sum()` in `where` does not aggregate multivalue fields; it returns the sum of the first value.
Clue confirmation
The clue word "primary" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume `sum(amount)` works directly in a `where` clause after `transaction`, but Splunk requires explicit multivalue field aggregation functions like `mvsum()` to compute totals from grouped events.
Detailed technical explanation
How to think about this question
The `transaction` command groups events into a single event with multivalue fields, where each field (e.g., `amount`) contains a list of values from the grouped events. The `where` clause in Splunk operates on single values, not multivalue fields; to aggregate multivalue fields, you must use `eval` with functions like `mvsum()` or `mvcount()`. In real-world fraud detection, this distinction is critical because failing to properly aggregate multivalue fields can silently produce empty results, leading to missed alerts.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Transactions and Event Correlation practice questions
Targeted practice on this topic area only
- →
All SPLK-1003 questions
500 questions across all exam domains
- →
Splunk Core Certified Power User SPLK-1003 study guide
Full concept coverage aligned to exam objectives
- →
SPLK-1003 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SPLK-1003 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Advanced Searching and Statistics practice questions
Practise SPLK-1003 questions linked to Advanced Searching and Statistics.
Macros, Saved Searches and CIM practice questions
Practise SPLK-1003 questions linked to Macros, Saved Searches and CIM.
Advanced Visualization and Lookups practice questions
Practise SPLK-1003 questions linked to Advanced Visualization and Lookups.
Transactions and Event Correlation practice questions
Practise SPLK-1003 questions linked to Transactions and Event Correlation.
SPLK-1003 fundamentals practice questions
Practise SPLK-1003 questions linked to SPLK-1003 fundamentals.
SPLK-1003 scenario practice questions
Practise SPLK-1003 questions linked to SPLK-1003 scenario.
SPLK-1003 troubleshooting practice questions
Practise SPLK-1003 questions linked to SPLK-1003 troubleshooting.
Practice this exam
Start a free SPLK-1003 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SPLK-1003 question test?
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: The `where sum(amount) > 200` does not work as expected because `sum()` is not an aggregation function in that context; you need to use `stats sum(amount)` or `eval total=mvsum(amount)` first. — Option D is correct because the `transaction` command creates a single multivalue field `amount` containing all amounts from the grouped events. The `where` clause cannot directly aggregate multivalue fields with `sum()`; it requires an explicit `eval` to compute the sum (e.g., `eval total=mvsum(amount)`) or a `stats` command. Without this, the `where` clause evaluates `sum(amount)` as a string operation or fails silently, returning no results.
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.
Are there clue words in this question I should notice?
Yes — watch for: "primary". Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
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 →
Last reviewed: Jun 11, 2026
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.