Quick Answer
The answer is `source=firewall | lookup priority_lookup source OUTPUT priority`, because the conditional lookup filter before command pattern ensures the lookup runs only on events already narrowed by a search-time filter. This approach leverages Splunk’s pipeline processing: by placing `source=firewall` first, you reduce the dataset before the `lookup` command executes, which minimizes resource consumption and avoids unnecessary lookups on irrelevant events. On the SPLK-1002 exam, this tests your understanding of command ordering and efficiency—a common trap is applying the lookup first and then filtering, which wastes processing power on all events. Remember that in Splunk, the pipe is a sequential filter: what comes before the pipe limits what the next command sees. For a memory tip, think “filter first, lookup last”—like checking your ID before entering a restricted room, not after.
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 search uses a lookup that returns a field 'priority'. The admin wants to use the lookup only for events where the 'source' is 'firewall'. Which command should be used?
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.
source=firewall | lookup priority_lookup source OUTPUT priority
Filters first, then lookup only on those events.
| lookup priority_lookup source OUTPUT priority
Why wrong: Runs on all events.
| lookup priority_lookup source OUTPUT priority | where source="firewall"
Why wrong: Lookup still runs on all events.
| lookup priority_lookup source OUTPUT priority WHERE source="firewall"
Why wrong: Invalid syntax.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
source=firewall | lookup priority_lookup source OUTPUT priority
Option A is correct because it first filters events with `source=firewall` using a search-time field filter, then applies the `lookup` command only to those events. This ensures the lookup is performed exclusively on firewall events, minimizing resource usage and avoiding unnecessary lookups on other sources.
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.
source=firewall | lookup priority_lookup source OUTPUT priority
Why this is correct
Filters first, then lookup only on those events.
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 priority_lookup source OUTPUT priority
Why it's wrong here
Runs on all events.
| lookup priority_lookup source OUTPUT priority | where source="firewall"
Why it's wrong here
Lookup still runs on all events.
| lookup priority_lookup source OUTPUT priority WHERE source="firewall"
Why it's wrong here
Invalid syntax.
Common exam traps
Splunk often tests the order of operations in the Splunk search pipeline, where candidates mistakenly think a `WHERE` clause inside the lookup command or a post-lookup filter achieves the same result as pre-filtering with a leading search term.
Detailed technical explanation
The `lookup` command in Splunk performs a field-based lookup against a CSV file or KV store, and it is most efficient when applied to a reduced dataset. By using a leading filter like `source=firewall`, the search pipeline processes only matching events before the lookup, which reduces I/O and improves performance. In contrast, post-lookup filtering with `where` still incurs the cost of the lookup on all events, which can be significant in large datasets.
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: source=firewall | lookup priority_lookup source OUTPUT priority — Option A is correct because it first filters events with `source=firewall` using a search-time field filter, then applies the `lookup` command only to those events. This ensures the lookup is performed exclusively on firewall events, minimizing resource usage and avoiding unnecessary lookups on other sources.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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.
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.