Quick Answer
The correct answer is that version comparison will not be numeric, giving incorrect results because the `where` clause performs lexicographic (string) comparison on the `version` field. When Splunk evaluates strings like '2.0' and '10.0' character by character, '2' is greater than '1', so '2.0' is considered larger than '10.0'—a classic failure of string vs numeric version comparison. On the SPLK-1002 exam, this question tests your understanding of data types in lookups and how Splunk’s comparison operators behave; the common trap is assuming that fields containing numbers are automatically treated as numeric. To avoid this, always check field types in the lookup file or use `tonumber(version)` in your search to force numeric comparison. Memory tip: think of string comparison as alphabetizing—'10' comes before '2' because '1' < '2', but numerically it’s the opposite.
This SPLK-1002 practice question tests your understanding of using fields and lookups. 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.
Refer to the exhibit. | inputlookup app_versions.csv | where version > "2.0" | table app version
Refer to the exhibit. The lookup file app_versions.csv contains fields 'app' and 'version'. The version values are strings like '1.5', '2.0', '2.1'. What is the issue with this search?
Refer to the exhibit. | inputlookup app_versions.csv | where version > "2.0" | table app version
Version comparison will not be numeric, giving incorrect results
String comparison fails for version numbers.
where cannot be used with string comparisons
Why wrong: where works with strings.
inputlookup is not a valid command
Why wrong: inputlookup is valid.
table should be replaced with fields
Why wrong: table is fine.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Version comparison will not be numeric, giving incorrect results
The issue is that the `where` clause performs lexicographic (string) comparison on the `version` field because the values in the lookup file are stored as strings (e.g., '1.5', '2.0', '2.1'). Since string comparison evaluates character by character, a version like '2.0' would be considered greater than '10.0' because '2' > '1' as a character, leading to incorrect filtering results. To compare versions numerically, you must convert the field to a numeric type using functions like `tonumber()` or parse the version string into comparable components.
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.
Version comparison will not be numeric, giving incorrect results
Why this is correct
String comparison fails for version numbers.
Related concept
Read the scenario before looking for a memorised answer.
where cannot be used with string comparisons
Why it's wrong here
where works with strings.
inputlookup is not a valid command
Why it's wrong here
inputlookup is valid.
table should be replaced with fields
Why it's wrong here
table is fine.
Common exam traps
Splunk often tests the misconception that `where` can automatically handle numeric comparisons for fields that look like numbers but are stored as strings, leading candidates to overlook the need for explicit type conversion.
Detailed technical explanation
Under the hood, Splunk's `where` command uses the same comparison operators as the search language, which default to string comparison for string fields. For version strings like '1.5', '2.0', '2.1', lexicographic ordering does not align with semantic versioning; for example, '9.9' would be considered greater than '10.0' because '9' > '1'. A robust solution involves splitting the version into major and minor parts using `eval` and `split()`, then comparing numeric values, or using `tonumber()` on the entire string if the format is consistently numeric (e.g., '1.5' becomes 1.5 as a float). In real-world scenarios, this issue commonly arises when comparing software versions, IP addresses, or any dotted-decimal strings where numeric ordering is expected.
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-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
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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise SPLK-1002 questions linked to Splunk Basics and Interface Navigation.
Practise SPLK-1002 questions linked to Basic Searching and Transforming Commands.
Practise SPLK-1002 questions linked to Using Fields and Lookups.
Practise SPLK-1002 questions linked to Creating Reports, Dashboards and Visualizations.
Practise SPLK-1002 questions linked to Data Models and Best Practices.
Practise SPLK-1002 questions linked to SPLK-1002 fundamentals.
Practise SPLK-1002 questions linked to SPLK-1002 scenario.
Practise SPLK-1002 questions linked to SPLK-1002 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Using Fields and Lookups — This question tests Using Fields and Lookups — Read the scenario before looking for a memorised answer..
The correct answer is: Version comparison will not be numeric, giving incorrect results — The issue is that the `where` clause performs lexicographic (string) comparison on the `version` field because the values in the lookup file are stored as strings (e.g., '1.5', '2.0', '2.1'). Since string comparison evaluates character by character, a version like '2.0' would be considered greater than '10.0' because '2' > '1' as a character, leading to incorrect filtering results. To compare versions numerically, you must convert the field to a numeric type using functions like `tonumber()` or parse the version string into comparable components.
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 →
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.