The answer is that the field name in the WHERE clause must be enclosed in single quotes because it contains parentheses. This is correct because Splunk’s search processing language (SPL) interprets unquoted field names with special characters like parentheses as function calls rather than literal field references, causing a syntax error when you try to filter on `perc95(response_time)`. On the Splunk SPLK-1003 exam, this tests your understanding of how the `where` command handles field names generated by statistical functions like `perc95`, a common trap where candidates forget that the resulting field retains the exact syntax of the calculation. A reliable memory tip is to think of the field name as a single, quoted token: if it has parentheses, wrap it in single quotes to tell Splunk “this is a field, not a function.”
SPLK-1003 Advanced Searching and Statistics Practice Question
This SPLK-1003 practice question tests your understanding of advanced searching and statistics. 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 search is used to calculate the 95th percentile of response times for each application, and then to find applications where the 95th percentile exceeds 5000 ms. The current search is:
`index=perf sourcetype=app_response | stats perc95(response_time) by app | where perc95(response_time) > 5000`
This search fails with an error. What is the most likely reason?
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.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The field name in the where clause must match exactly, including parentheses. Use `where 'perc95(response_time)' > 5000`
Option C is correct because the `where` clause in SPL treats field names containing special characters (like parentheses) as literal strings. Without quoting, `perc95(response_time)` is parsed as a function call rather than a field name, causing a syntax error. Wrapping the field name in single quotes (`'perc95(response_time)'`) tells Splunk to treat it as a literal field reference.
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 stats command cannot use perc95 with a by clause.
Why it's wrong here
It can, but the field name includes the function.
✗
The stats command requires a rename of the output field.
Why it's wrong here
Not required, though recommended.
✓
The field name in the where clause must match exactly, including parentheses. Use `where 'perc95(response_time)' > 5000`
Why this is correct
In Splunk, the resulting field is named with the function and parentheses, so it must be quoted or escaped.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The perc95 function is not a valid stats function.
Why it's wrong here
perc95 is valid.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Splunk often tests the nuance that field names generated by `stats` with functions like `perc95()` must be quoted in subsequent commands like `where` or `eval` to avoid being misinterpreted as function calls.
Detailed technical explanation
How to think about this question
When Splunk evaluates `where perc95(response_time) > 5000`, it interprets `perc95(response_time)` as a function call expecting an argument, not as a field name. The `stats` command automatically names the output field using the exact expression, including parentheses, so the correct reference is `'perc95(response_time)'`. This quoting behavior is essential when field names contain spaces, hyphens, or special characters like parentheses, and is a common source of errors in SPL.
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 — 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: The field name in the where clause must match exactly, including parentheses. Use `where 'perc95(response_time)' > 5000` — Option C is correct because the `where` clause in SPL treats field names containing special characters (like parentheses) as literal strings. Without quoting, `perc95(response_time)` is parsed as a function call rather than a field name, causing a syntax error. Wrapping the field name in single quotes (`'perc95(response_time)'`) tells Splunk to treat it as a literal field reference.
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". 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.