Quick Answer
The answer is the `eval` command with the `if()` function, specifically `| eval status=if(value>100,"critical","normal")`. This is correct because `eval` is the only SPL command that allows conditional field creation through expression evaluation, and the `if()` function provides the necessary conditional logic to test a numeric threshold and assign a new field value based on the result. On the Splunk Core Certified Power User SPLK-1003 exam, this tests your understanding of computed fields and conditional logic, often appearing in scenario-based questions where you must dynamically label events. A common trap is confusing `eval` with `rex` or `where`—remember that `rex` extracts existing data, while `where` filters events, not creates fields. For a quick memory tip: think of `eval` as your "if-then-else" calculator for fields, where the syntax always follows `field=if(condition, true_value, false_value)`.
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.
Which SPL command can be used to create a new field based on a conditional evaluation, such as setting a status field to 'critical' if a numeric threshold is exceeded?
| makemv
Why wrong: Makemv creates multi-value fields from delimited strings
| rex field=_raw
Why wrong: Rex extracts fields using regex, not conditional
| eval status=if(value>100,"critical","normal")
Eval with if performs conditional assignment
| convert status=if(value>100,"critical","normal")
Why wrong: Convert is for data type conversion, not conditional assignment
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
| eval status=if(value>100,"critical","normal")
The `eval` command in SPL is used to create new fields or modify existing ones by evaluating expressions. The `if()` function within `eval` allows conditional logic, making `| eval status=if(value>100,"critical","normal")` the correct syntax to create a new field 'status' that is set to 'critical' when the numeric field 'value' exceeds 100, and 'normal' otherwise.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
| makemv
Why it's wrong here
Makemv creates multi-value fields from delimited strings
| rex field=_raw
Why it's wrong here
Rex extracts fields using regex, not conditional
| eval status=if(value>100,"critical","normal")
Why this is correct
Eval with if performs conditional assignment
Related concept
Read the scenario before looking for a memorised answer.
| convert status=if(value>100,"critical","normal")
Why it's wrong here
Convert is for data type conversion, not conditional assignment
Common exam traps
Splunk often tests the distinction between `eval` (for field creation and computation) and `convert` (for data type conversion), leading candidates to mistakenly choose `convert` for conditional logic due to its similar syntax.
Detailed technical explanation
The `eval` command processes each event individually, evaluating the expression and adding the result as a new field or overwriting an existing one. The `if()` function in `eval` is a ternary conditional that takes three arguments: a boolean expression, a true value, and a false value. This is commonly used in real-world scenarios like alerting thresholds, where a field like 'severity' is dynamically set based on metrics such as CPU usage or response time, enabling efficient filtering and dashboarding.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SPLK-1003 questions linked to Advanced Searching and Statistics.
Practise SPLK-1003 questions linked to Macros, Saved Searches and CIM.
Practise SPLK-1003 questions linked to Advanced Visualization and Lookups.
Practise SPLK-1003 questions linked to Transactions and Event Correlation.
Practise SPLK-1003 questions linked to SPLK-1003 fundamentals.
Practise SPLK-1003 questions linked to SPLK-1003 scenario.
Practise SPLK-1003 questions linked to SPLK-1003 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Advanced Searching and Statistics — This question tests Advanced Searching and Statistics — Read the scenario before looking for a memorised answer..
The correct answer is: | eval status=if(value>100,"critical","normal") — The `eval` command in SPL is used to create new fields or modify existing ones by evaluating expressions. The `if()` function within `eval` allows conditional logic, making `| eval status=if(value>100,"critical","normal")` the correct syntax to create a new field 'status' that is set to 'critical' when the numeric field 'value' exceeds 100, and 'normal' otherwise.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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
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.