- A
Use 'convert num(bytes)' before stats.
Why wrong: The convert command is deprecated and may not work as expected in all versions; also, it modifies the field in place which could cause issues.
- B
Use 'eval bytes_numeric = tonumber(bytes)' then 'stats sum(bytes_numeric) as total_bytes by user'.
This explicitly converts the string to numeric, ensuring correct summation.
- C
Use 'where isnum(bytes)' to filter out non-numeric values before stats.
Why wrong: This may remove events where bytes is numeric but stored as string, but it does not convert; sum would still treat as string.
- D
Use 'eval bytes = string(bytes)' before stats.
Why wrong: This would keep bytes as string, not numeric, and sum would not work correctly.
Question 372 of 500
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 Splunk administrator runs the following search to identify the top 5 users by total bytes transferred:
index=proxy sourcetype=webproxy | stats sum(bytes) as total_bytes by user | sort - total_bytes | head 5
The search returns results, but the numbers seem inflated. On closer inspection, the 'bytes' field is a string type. What must be done to correct the search?
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
✓
Use 'eval bytes_numeric = tonumber(bytes)' then 'stats sum(bytes_numeric) as total_bytes by user'.
Option B is correct because `bytes` is stored as a string. `stats sum()` may not correctly sum string values if they contain non-numeric characters. Using `eval tonumber()` creates a numeric field and safely converts non-numeric values to null (ignored by sum), ensuring accurate totals. While `convert num(bytes)` (Option A) is a valid command, `eval tonumber()` is the preferred method for explicit conversion before statistical aggregations.
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.
- ✗
Use 'convert num(bytes)' before stats.
Why it's wrong here
The convert command is deprecated and may not work as expected in all versions; also, it modifies the field in place which could cause issues.
- ✓
Use 'eval bytes_numeric = tonumber(bytes)' then 'stats sum(bytes_numeric) as total_bytes by user'.
Why this is correct
This explicitly converts the string to numeric, ensuring correct summation.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use 'where isnum(bytes)' to filter out non-numeric values before stats.
Why it's wrong here
This may remove events where bytes is numeric but stored as string, but it does not convert; sum would still treat as string.
- ✗
Use 'eval bytes = string(bytes)' before stats.
Why it's wrong here
This would keep bytes as string, not numeric, and sum would not work correctly.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Candidates may assume that `stats sum()` automatically converts strings and works correctly, or they may choose `convert` thinking it is the only option. However, `eval tonumber()` provides more control and is the recommended approach for this scenario.
Trap categories for this question
Command / output trap
The convert command is deprecated and may not work as expected in all versions; also, it modifies the field in place which could cause issues.
Detailed technical explanation
How to think about this question
Under the hood, Splunk's `stats sum()` expects numeric field values; if the field is a string, Splunk may coerce it to zero or treat it as a concatenation operation, depending on context. The `tonumber()` function handles edge cases like leading/trailing whitespace, commas, or non-numeric characters by returning NULL for invalid inputs, which `stats` then ignores — this prevents silent data corruption. In real-world proxy logs, the `bytes` field often contains commas or units (e.g., '1,024'), so `tonumber()` with a `eval` expression like `replace(bytes, ",", "")` may be needed for robust conversion.
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.
- →
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: Use 'eval bytes_numeric = tonumber(bytes)' then 'stats sum(bytes_numeric) as total_bytes by user'. — Option B is correct because `bytes` is stored as a string. `stats sum()` may not correctly sum string values if they contain non-numeric characters. Using `eval tonumber()` creates a numeric field and safely converts non-numeric values to null (ignored by sum), ensuring accurate totals. While `convert num(bytes)` (Option A) is a valid command, `eval tonumber()` is the preferred method for explicit conversion before statistical aggregations.
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 →
Keep practising
More SPLK-1003 practice questions
- A telecom company monitors call detail records (CDR). Each call has a unique call_id, and events are generated at each n…
- Which TWO statements correctly describe the behavior of the transaction command in Splunk?
- Which TWO of the following are valid reasons to use the Common Information Model (CIM) in a Splunk environment?
- Arrange the steps to create a new index in Splunk in the correct order.
- A Splunk admin wants to track the number of unique users who accessed a system each hour over the past 24 hours. Which s…
- A search returns many events, and the analyst wants to see a summary table of the top 5 values of the field `src_ip` alo…
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.