Quick Answer
The answer is the `fieldsummary` command. This command is the correct choice because it generates a statistical overview of every field extracted from the events in your search results, displaying the field name, count, distinct count, and the percentage of events containing that field. When you first filter your search to a specific sourcetype using `index=* sourcetype=your_sourcetype`, then pipe the results into `| fieldsummary`, you get a complete, structured list of all fields extracted from that sourcetype, making it the precise tool for this task. On the Splunk Core Certified User SPLK-1002 exam, this question tests your understanding of field discovery commands versus data transformation commands; a common trap is confusing `fieldsummary` with `fields` (which only shows or hides columns) or `stats` (which requires explicit field naming). Remember the memory tip: "Fieldsummary gives you the full field menu" — it serves as a menu of every extracted field available for that sourcetype.
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 see the list of all fields that are extracted from a specific sourcetype. Which command should they use?
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.
| rex field=_raw ...
Why wrong: rex extracts specific fields.
| fields *
Why wrong: Shows all fields in each event, not a distinct list.
| eval fields=...
Why wrong: eval doesn't list fields.
| fieldsummary
fieldsummary provides a summary of fields, including names.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
| fieldsummary
The `fieldsummary` command provides a summary of all fields extracted from the events in the search results, including their count, distinct count, and percentage of events containing each field. When applied to a specific sourcetype, it lists every field that has been extracted from that sourcetype, making it the correct tool for this task.
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.
| rex field=_raw ...
Why it's wrong here
rex extracts specific fields.
| fields *
Why it's wrong here
Shows all fields in each event, not a distinct list.
| eval fields=...
Why it's wrong here
eval doesn't list fields.
| fieldsummary
Why this is correct
fieldsummary provides a summary of fields, including names.
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.
Common exam traps
Splunk often tests the distinction between commands that list fields (`fieldsummary`) versus commands that extract or manipulate fields (`rex`, `eval`, `fields`), leading candidates to confuse the purpose of `fields *` (which removes fields) with listing them.
Trap categories for this question
Command / output trap
Shows all fields in each event, not a distinct list.
Detailed technical explanation
The `fieldsummary` command operates on the search results after all field extractions (automatic, regex, and lookup-based) have been applied, providing a statistical overview of field presence. Under the hood, it iterates over every event in the result set and aggregates metadata about each field's occurrence, which is especially useful for understanding data quality and coverage across different sourcetypes 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: | fieldsummary — The `fieldsummary` command provides a summary of all fields extracted from the events in the search results, including their count, distinct count, and percentage of events containing each field. When applied to a specific sourcetype, it lists every field that has been extracted from that sourcetype, making it the correct tool for this task.
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 →
Same concept, more angles
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A Splunk user wants to see a list of all fields that are extracted from events of sourcetype 'apache_access'. They need to know which fields are available for use in searches and lookups. Which command should they use to discover all fields automatically extracted by Splunk for that sourcetype?
easyWhy A: Option A is correct because the `| fields` command, when used without arguments, lists all fields present in the search results. By searching `sourcetype=apache_access` and piping to `| fields`, Splunk returns a table of all extracted fields (both default and custom) from the events of that sourcetype, allowing the user to see which fields are available for searches and lookups.
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.