- A
`... | where avg(duration)>100 | stats count by user | where count>5`
Why wrong: The first where tries to use an aggregate function on raw events, which is invalid.
- B
`... | top user limit=0 | where avg(duration)>100`
Why wrong: Top counts events per user, does not compute average.
- C
`... | stats avg(duration) as avg_dur, count as cnt by user | where avg_dur>100 and cnt>5`
Correct: stats reduces to one row per user, then where filters.
- D
`... | eventstats avg(duration) as avg_dur, count as cnt by user | where avg_dur>100 and cnt>5`
Why wrong: eventstats adds fields to each event, does not collapse; the search would return events, not distinct users.
- E
`... | stats avg(duration) as avg_dur, count as cnt by user | having avg_dur>100 and cnt>5`
Why wrong: 'having' is not a valid Splunk command.
Quick Answer
The correct search uses `stats` with `by user` to compute the average duration and count per user, then pipes the results into a `where` command to apply post-aggregation filtering with stats and where. This is the correct pattern because `where` operates on the aggregated results after `stats` has reduced the raw events, allowing you to filter on computed fields like `avg_dur` and `cnt` that don't exist in the original data. On the Splunk Core Certified Power User SPLK-1003 exam, this question tests your understanding that you cannot use `where` before `stats` to filter on aggregate values, and that `stats` must come first to create the per-user summary. A common trap is trying to use `where` directly on raw events to check average duration, which fails because `avg()` is an aggregating function. Remember the memory tip: aggregate first, filter second—stats builds the summary, where trims the results.
SPLK-1003 Advanced Searching and Statistics Practice Question
This SPLK-1003 practice question tests your understanding of advanced searching and statistics. 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 search returns events with fields 'user', 'duration', and 'status'. The analyst wants to find users whose average duration exceeds 100 and who have more than 5 events. Which search is correct?
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
`... | stats avg(duration) as avg_dur, count as cnt by user | where avg_dur>100 and cnt>5`
Option C is correct because it uses the `stats` command to compute the average duration and count per user in a single pass, then filters with `where` to enforce both conditions: average duration > 100 and event count > 5. This is the standard pattern for per-user aggregation followed by post-aggregation filtering in Splunk.
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.
- ✗
`... | where avg(duration)>100 | stats count by user | where count>5`
Why it's wrong here
The first where tries to use an aggregate function on raw events, which is invalid.
- ✗
`... | top user limit=0 | where avg(duration)>100`
Why it's wrong here
Top counts events per user, does not compute average.
- ✓
`... | stats avg(duration) as avg_dur, count as cnt by user | where avg_dur>100 and cnt>5`
Why this is correct
Correct: stats reduces to one row per user, then where filters.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
`... | eventstats avg(duration) as avg_dur, count as cnt by user | where avg_dur>100 and cnt>5`
Why it's wrong here
eventstats adds fields to each event, does not collapse; the search would return events, not distinct users.
- ✗
`... | stats avg(duration) as avg_dur, count as cnt by user | having avg_dur>100 and cnt>5`
Why it's wrong here
'having' is not a valid Splunk command.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Splunk often tests the difference between `stats` and `eventstats`, where candidates mistakenly choose `eventstats` thinking it filters users, but it actually keeps all events and applies the `where` condition per event, not per user.
Trap categories for this question
Command / output trap
'having' is not a valid Splunk command.
Detailed technical explanation
How to think about this question
The `stats` command in Splunk operates on grouped data, producing one result row per unique value of the `by` field, and aggregate functions like `avg()` and `count()` are computed within each group. Using `eventstats` instead would retain the original events and add aggregate fields, which is useful for per-event comparisons but not for reducing to user-level summaries. In real-world scenarios, this distinction is critical when you need to filter users based on aggregated metrics without altering the event count.
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.
- →
Advanced Searching and Statistics — study guide chapter
Learn the concepts, then practise the questions
- →
Advanced Searching and Statistics 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?
Advanced Searching and Statistics — This question tests Advanced Searching and Statistics — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: `... | stats avg(duration) as avg_dur, count as cnt by user | where avg_dur>100 and cnt>5` — Option C is correct because it uses the `stats` command to compute the average duration and count per user in a single pass, then filters with `where` to enforce both conditions: average duration > 100 and event count > 5. This is the standard pattern for per-user aggregation followed by post-aggregation filtering in Splunk.
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 →
Last reviewed: Jun 30, 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.