Quick Answer
The answer is that the calculated field is missing a REPORT clause in props.conf, which is the most likely reason it is not appearing in search results. Calculated fields in Splunk are not automatically applied by simply defining an extraction expression; they require explicit configuration in props.conf with a REPORT stanza to tell Splunk when and how to run the extraction during indexing or search time. Without this, the field definition exists but is never executed, so the domain extraction from the email address never populates. On the SPLK-1002 exam, this tests your understanding of the relationship between field extractions and configuration files—a common trap is assuming that a valid rex expression alone makes a field available. Remember the memory tip: “No REPORT, no result”—if you don’t link the extraction in props.conf, the calculated field stays invisible to your searches.
This SPLK-1002 practice question tests your understanding of using fields and lookups. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 creates a calculated field that extracts the domain from email addresses using the expression `| rex field=email "(?P<domain>@\w+\.\w+)"`. However, the calculated field does not appear in search results. What is the most likely reason?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Calculated fields must be enabled in props.conf with REPORT clauses.
Requires proper configuration.
Calculated fields are only applied at search time, not index time.
Why wrong: They are applied at search time, but still need definition.
The field extraction is incorrect.
Why wrong: Extraction seems valid.
Calculated fields must be used with the `eval` command.
Why wrong: eval is separate.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Calculated fields must be enabled in props.conf with REPORT clauses.
Option A is correct because calculated fields in Splunk require explicit configuration in props.conf using a REPORT clause to define the extraction. Without this configuration, the calculated field is not available for use in searches, even if the extraction expression is valid. The user's calculated field definition is missing the necessary props.conf setup, so it never gets applied.
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.
Calculated fields must be enabled in props.conf with REPORT clauses.
Why this is correct
Requires proper configuration.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Calculated fields are only applied at search time, not index time.
Why it's wrong here
They are applied at search time, but still need definition.
The field extraction is incorrect.
Why it's wrong here
Extraction seems valid.
Calculated fields must be used with the `eval` command.
Why it's wrong here
eval is separate.
Common exam traps
The trap here is that candidates assume a valid regex in a calculated field definition is sufficient for it to appear in results, overlooking the mandatory props.conf configuration step that Splunk requires for persistent field extractions.
Detailed technical explanation
Calculated fields in Splunk are defined in props.conf under a specific sourcetype or host stanza using the `EXTRACT-<class>` or `REPORT-<class>` syntax, which references a transforms.conf stanza that contains the extraction regex. The field extraction is applied at search time by the search head, but only if the props.conf configuration is present and the sourcetype matches. A common real-world scenario is when a user defines a calculated field in the UI but forgets to deploy the corresponding props.conf changes to all search peers, causing the field to be missing in distributed searches.
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: Calculated fields must be enabled in props.conf with REPORT clauses. — Option A is correct because calculated fields in Splunk require explicit configuration in props.conf using a REPORT clause to define the extraction. Without this configuration, the calculated field is not available for use in searches, even if the extraction expression is valid. The user's calculated field definition is missing the necessary props.conf setup, so it never gets applied.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 user notices that a calculated field defined in props.conf is not appearing in search results. Which of the following is the most likely cause?
easyWhy B: Calculated fields in Splunk are evaluated at search time based on existing extracted source fields. If the source fields referenced in the calculation are not extracted (e.g., due to missing or incorrect field extraction configurations), the calculated field will not appear in search results. Option B correctly identifies this dependency.
Last reviewed: Jun 24, 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.