- A
Add a stats count by error_code
Why wrong: stats does not inherently support drilldown.
- B
Replace top with fields to keep only error_code
Why wrong: fields does not produce a table for drilldown.
- C
Replace top with table error_code, count
table creates a table that can be used for drilldown.
- D
Add an eval command to create a clickable link
Why wrong: Clickable links are not needed for drilldown.
Quick Answer
The answer is to replace `top` with `table error_code, count`. This is correct because the `table` command produces a clean, tabular output that retains the raw field values needed for dashboard drilldown functionality, allowing the selected `error_code` to be passed as a token to another search. In contrast, the `top` command generates an aggregated statistical summary that strips away the underlying event structure, breaking the standard drilldown behavior in Splunk dashboards. On the Splunk Core Certified User SPLK-1002 exam, this question tests your understanding of how different transforming commands affect drilldown capabilities—a common trap is assuming `top` works for drilldown since it also shows counts, but only `table` preserves the clickable field values. Remember: for a dashboard drilldown table vs top, think “table retains, top aggregates.” A handy memory tip is “Table is clickable, top is static.”
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 Splunk admin is tasked with creating a dashboard that shows the top 10 error codes from application logs. The logs contain a field 'error_code' which is extracted automatically. The admin writes the search: index=app sourcetype=app_log | top limit=10 error_code. The dashboard shows the correct data, but the admin wants to add a drilldown that passes the selected error code to another search. The admin considers using the 'fields' command to keep only error_code, the 'table' command to display the data, the 'eval' command to create a new field, or the 'stats' command to count. Which change should the admin make to the search to enable the drilldown functionality?
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
Replace top with table error_code, count
Option C is correct because the `table` command produces a tabular output that inherently supports drilldown in Splunk dashboards by preserving the raw event data and field values. When you use `table error_code, count`, the dashboard can pass the selected `error_code` value to another search via a token. The original `top` command aggregates data into a statistical summary that does not retain the raw event structure required for standard drilldown behavior.
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.
- ✗
Add a stats count by error_code
Why it's wrong here
stats does not inherently support drilldown.
- ✗
Replace top with fields to keep only error_code
Why it's wrong here
fields does not produce a table for drilldown.
- ✓
Replace top with table error_code, count
Why this is correct
table creates a table that can be used for drilldown.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Add an eval command to create a clickable link
Why it's wrong here
Clickable links are not needed for drilldown.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume `top` already displays a table and thus supports drilldown, but they miss that `top` produces a statistical summary that does not retain the raw event context required for standard token-based drilldown in Splunk dashboards.
Detailed technical explanation
How to think about this question
Under the hood, Splunk dashboard drilldown works by setting tokens from the clicked row's field values. The `table` command outputs results in a structured, row-based format that the Simple XML framework can parse for token assignment. In contrast, `top` and `stats` return statistical tables that are not directly linked to raw events, so the dashboard cannot automatically extract the `error_code` value from a click without custom JavaScript or a post-process search. A real-world scenario is building a dashboard that lets operators click an error code to open a detailed incident investigation view.
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: Replace top with table error_code, count — Option C is correct because the `table` command produces a tabular output that inherently supports drilldown in Splunk dashboards by preserving the raw event data and field values. When you use `table error_code, count`, the dashboard can pass the selected `error_code` value to another search via a token. The original `top` command aggregates data into a statistical summary that does not retain the raw event structure required for standard drilldown behavior.
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.
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 11, 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.