The answer is that the `search stage="*"` command is filtering out all transactions because stage is a multivalue field. In Splunk, when the `transaction` command groups events, it creates multivalue fields like `stage` that hold multiple values per transaction. Using `search stage="*"` with quotes treats the asterisk as a literal character, not a wildcard, so it only matches events where `stage` is a single asterisk string, not any value in the multivalue field. On the Splunk SPLK-1003 exam, this tests your understanding of how multivalue fields behave differently from single-value fields, especially in transaction searches for patterns like brute-force attacks. A common trap is assuming wildcards work the same on multivalue fields, but they do not—you must use `search stage=*` without quotes or `mvcount(stage)>0` to check for any value. Memory tip: think of multivalue fields as lists; a quoted wildcard checks for the word "star," not the list contents.
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.
Exhibit
Refer to the exhibit.
```
index=main sourcetype=linux_secure
| eval stage=case(
like(_raw,"%Failed password%"),"failed",
like(_raw,"%Accepted password%"),"success")
| transaction src maxspan=5m
| search stage="*"
| eval attack=if(mvcount(stage)>2 AND mvcount(stage)>=2 AND mvfind(stage,"failed")!=-1 AND mvfind(stage,"success")!=-1,"yes","no")
| where attack="yes"
```
Refer to the exhibit. The search aims to detect brute-force attacks where there are at least 2 failed logins followed by a successful login from the same source IP within 5 minutes. However, the search returns no results even though such attacks exist. What is the most likely error in the search logic?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Clue: "least"
Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The `search stage="*"` command is filtering out all transactions because stage is a multivalue field.
The `search stage="*"` command filters out all transactions because `stage` is a multivalue field created by the `transaction` command. In Splunk, a multivalue field cannot be matched with a simple wildcard search like `stage="*"`; this search only returns events where `stage` is a single literal asterisk. To search for any value in a multivalue field, you must use `mvcount(stage)>0` or `search stage=*` (without quotes).
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 transaction should group by user instead of src.
Why it's wrong here
Grouping by src (source IP) is appropriate for detecting brute-force from an IP.
✗
The case statement does not set stage for events that don't match either pattern.
Why it's wrong here
All events should match at least one condition; if not, stage is null, but that would be filtered by the search stage="*" anyway.
✗
The mvcount(stage) condition is incorrectly checking for >2 and >=2 simultaneously.
Why it's wrong here
The condition is redundant but not incorrect; it requires at least 3 events (2 fails + 1 success).
✓
The `search stage="*"` command is filtering out all transactions because stage is a multivalue field.
Why this is correct
Searching stage="*" does not match multivalue fields; it matches a literal asterisk. Should use `where isnotnull(stage)`.
Clue confirmation
The clue words "most likely", "least" 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
Splunk often tests the subtle difference between `field="*"` (literal asterisk) and `field=*` (wildcard) in the context of multivalue fields, tricking candidates into thinking a quoted wildcard works the same as an unquoted one.
Detailed technical explanation
How to think about this question
When Splunk's `transaction` command groups events, it creates a multivalue field (e.g., `stage`) that holds all values from the constituent events. Searching with `stage="*"` treats the asterisk as a literal string, not a wildcard, because the field is multivalue; Splunk's search language requires `stage=*` (without quotes) to match any value in a multivalue field. This is a common pitfall where the wildcard behavior differs between single-value and multivalue fields, and the `search` command's implicit field-value matching does not expand multivalue fields for wildcard comparisons.
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 — 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 `search stage="*"` command is filtering out all transactions because stage is a multivalue field. — The `search stage="*"` command filters out all transactions because `stage` is a multivalue field created by the `transaction` command. In Splunk, a multivalue field cannot be matched with a simple wildcard search like `stage="*"`; this search only returns events where `stage` is a single literal asterisk. To search for any value in a multivalue field, you must use `mvcount(stage)>0` or `search stage=*` (without quotes).
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: "most likely", "least". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.