The answer is that the DEST_KEY is set to _meta, which does not make the field available for data models. When you use DEST_KEY _meta in field extraction, the extracted value is written into the internal metadata of the event rather than into the event’s indexed key-value store. Data models require fields to be part of the event’s indexed structure to be accessible for preview and reporting, so a field stored in _meta remains invisible to the data model. On the Splunk SPLK-1002 exam, this tests your understanding of how DEST_KEY destinations affect field availability, and it’s a common trap where candidates assume any extracted field will appear in the data model. Remember that _meta is for internal routing, not for indexed fields. A simple memory tip: “_meta is metadata, not data—if you want your field in the model, keep it out of _meta.”
SPLK-1002 Data Models and Best Practices Practice Question
This SPLK-1002 practice question tests your understanding of data models and best practices. 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.
Exhibit
Refer to the exhibit.
# props.conf
[apache_error]
TRANSFORMS-set = set_error_type
# transforms.conf
[set_error_type]
REGEX = \[(error|warn|info)\]
FORMAT = error_type::$1
DEST_KEY = _meta
Refer to the exhibit. A Splunk user is building a data model for Apache error logs. The configuration above extracts an error_type field. However, when previewing data in the data model, the error_type field is not available. What is the most likely cause?
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.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The DEST_KEY is set to _meta, which does not make the field available for data models.
Option D is correct because when DEST_KEY is set to _meta, the extracted field is stored in the internal metadata of the event rather than in the event's indexed fields. Data models rely on indexed fields that are part of the event's key-value structure, so fields stored in _meta are not accessible for data model field extraction or preview.
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.
✗
The regular expression in transforms.conf is incorrectly formatted.
Why it's wrong here
The regex correctly captures error, warn, or info.
✗
The transforms.conf is in the wrong app context.
Why it's wrong here
App context would not prevent the field from being available if configured correctly.
✗
The transform name in props.conf does not match the transform name in transforms.conf.
Why it's wrong here
The names match: 'set_error_type'.
✓
The DEST_KEY is set to _meta, which does not make the field available for data models.
Why this is correct
_meta stores the value in internal metadata, not as an indexed or search-time field.
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.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume any extracted field is automatically available to data models, but Splunk requires fields to be indexed or written to the event's key-value store, not hidden in metadata like _meta.
Detailed technical explanation
How to think about this question
The _meta key is a special internal field in Splunk that stores metadata about the event, such as source, sourcetype, and host. Fields written to _meta via DEST_KEY are not indexed as searchable key-value pairs and are not included in the field dictionary used by data models. To make extracted fields available to data models, DEST_KEY should be set to _raw (to modify the raw event) or the default behavior (writing to indexed fields) should be used.
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.
Data Models and Best Practices — This question tests Data Models and Best Practices — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The DEST_KEY is set to _meta, which does not make the field available for data models. — Option D is correct because when DEST_KEY is set to _meta, the extracted field is stored in the internal metadata of the event rather than in the event's indexed fields. Data models rely on indexed fields that are part of the event's key-value structure, so fields stored in _meta are not accessible for data model field extraction or preview.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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.
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.