- A
rex field=_raw 's/ERROR/Error/g'
Why wrong: rex extracts fields; it does not modify existing fields in place.
- B
eval severity=replace(severity, "ERROR", "Error")
eval with replace function modifies the field value.
- C
lookup severity_lookup severity OUTPUT new_severity
Why wrong: lookup adds fields from a lookup table, does not replace in place.
- D
convert ctime(_time)
Why wrong: convert changes time formats, not string values.
Quick Answer
The correct command is eval severity=replace(severity, "ERROR", "Error"). This works because the eval command’s replace function performs a case-sensitive, exact string substitution on the specified field, allowing you to replace field value using eval without needing regular expressions. On the Splunk SPLK-1002 exam, this question tests your understanding of the eval command’s string manipulation functions versus the rex command, which is often a trap for those who default to regex for simple replacements. A common mistake is choosing rex because it can also modify fields, but replace is the direct, simpler tool for case-sensitive text swaps like changing 'ERROR' to 'Error' in the severity field. To remember this, think of eval replace as a find-and-replace tool in a word processor—it swaps exact text without pattern matching. For the exam, keep in mind that replace is case-sensitive by default, so 'ERROR' and 'Error' are treated as distinct strings.
SPLK-1002 Using Fields and Lookups Practice Question
This SPLK-1002 practice question tests your understanding of using fields and lookups. 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 user wants to replace a field value 'ERROR' with 'Error' in search results. Which command should be used within a search to achieve this transformation?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"which command"Why it matters: Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
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
eval severity=replace(severity, "ERROR", "Error")
Option B is correct because the `replace` function in the `eval` command performs a case-sensitive string replacement on a specific field. In this case, it replaces the exact string 'ERROR' with 'Error' in the `severity` field, which is the precise transformation requested. Unlike `rex`, `replace` does not require regex syntax and directly modifies the field value without affecting other parts of the event.
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.
- ✗
rex field=_raw 's/ERROR/Error/g'
Why it's wrong here
rex extracts fields; it does not modify existing fields in place.
- ✓
eval severity=replace(severity, "ERROR", "Error")
Why this is correct
eval with replace function modifies the field value.
Clue confirmation
The clue word "which command" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
lookup severity_lookup severity OUTPUT new_severity
Why it's wrong here
lookup adds fields from a lookup table, does not replace in place.
- ✗
convert ctime(_time)
Why it's wrong here
convert changes time formats, not string values.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Splunk often tests the distinction between `rex` (which modifies raw text or a field using regex) and `eval` with `replace` (which performs a simple string replacement on a specific field), leading candidates to choose `rex` when a field-level substitution is needed.
Detailed technical explanation
How to think about this question
The `replace` function in Splunk's `eval` command is a non-regex string replacement, making it ideal for simple substitutions without the overhead of regex compilation. Under the hood, `eval` creates a new field or modifies an existing one in the search pipeline, and the `replace` function performs a literal character-by-character match. In real-world scenarios, this is commonly used to normalize log levels (e.g., 'ERROR', 'error', 'Error') to a consistent case for aggregation or alerting, avoiding the complexity of regex patterns.
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-1002 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.
- →
Using Fields and Lookups — study guide chapter
Learn the concepts, then practise the questions
- →
Using Fields and Lookups practice questions
Targeted practice on this topic area only
- →
All SPLK-1002 questions
510 questions across all exam domains
- →
Splunk Core Certified User SPLK-1002 study guide
Full concept coverage aligned to exam objectives
- →
SPLK-1002 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SPLK-1002 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Splunk Basics and Interface Navigation practice questions
Practise SPLK-1002 questions linked to Splunk Basics and Interface Navigation.
Basic Searching and Transforming Commands practice questions
Practise SPLK-1002 questions linked to Basic Searching and Transforming Commands.
Using Fields and Lookups practice questions
Practise SPLK-1002 questions linked to Using Fields and Lookups.
Creating Reports, Dashboards and Visualizations practice questions
Practise SPLK-1002 questions linked to Creating Reports, Dashboards and Visualizations.
Data Models and Best Practices practice questions
Practise SPLK-1002 questions linked to Data Models and Best Practices.
SPLK-1002 fundamentals practice questions
Practise SPLK-1002 questions linked to SPLK-1002 fundamentals.
SPLK-1002 scenario practice questions
Practise SPLK-1002 questions linked to SPLK-1002 scenario.
SPLK-1002 troubleshooting practice questions
Practise SPLK-1002 questions linked to SPLK-1002 troubleshooting.
Practice this exam
Start a free SPLK-1002 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-1002 question test?
Using Fields and Lookups — This question tests Using Fields and Lookups — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: eval severity=replace(severity, "ERROR", "Error") — Option B is correct because the `replace` function in the `eval` command performs a case-sensitive string replacement on a specific field. In this case, it replaces the exact string 'ERROR' with 'Error' in the `severity` field, which is the precise transformation requested. Unlike `rex`, `replace` does not require regex syntax and directly modifies the field value without affecting other parts of the event.
What should I do if I get this SPLK-1002 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: "which command". Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
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-1002 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-1002 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.