- A
Adding the field required the acceleration summary to be rebuilt, and the new field increased the summary size because it is not constrained.
Adding a field increases the data stored in acceleration summaries.
- B
The data model must be re-accelerated manually after adding a field, and the admin did not do so.
Why wrong: Splunk automatically rebuilds acceleration after a data model change.
- C
The 'department' field has a high number of unique values, and the acceleration summary cannot handle high-cardinality fields efficiently.
Why wrong: While high cardinality can affect performance, the primary issue is summary size.
- D
The new field caused the root event constraint to become more inclusive, adding more events.
Why wrong: Constraints are unchanged; only a field was added.
Quick Answer
The answer is that the performance drop occurs because adding the field forces the acceleration summary to be rebuilt, and the unconstrained 'department' field dramatically increases the summary size. In an accelerated data model, the summary stores pre-computed values for all fields at the root event level. When you add a new field without a constraint—meaning no filter limits which events contribute to it—the summary must now store that field's data for every single event in the acceleration window, bloating the summary and slowing query scans. On the SPLK-1002 exam, this tests your understanding of how data model acceleration works and the impact of unconstrained fields on summary storage. A common trap is assuming any new field will have minimal effect, but the key is whether the field is constrained by a filter. Remember: unconstrained fields are like adding a heavy backpack to every item in a warehouse—everything gets slower. Memory tip: "No constraint, no restraint—summary size unrestrained."
SPLK-1002 Data Models and Best Practices Practice Question
This SPLK-1002 practice question tests your understanding of data models and best practices. 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.
You are an admin for a large healthcare organization that uses Splunk for compliance monitoring. You have a data model named 'Patient_Access' that tracks access to patient records. The data model includes fields like 'employee_id', 'patient_id', 'access_time', and 'action'. The data model is accelerated with a 30-day summary. Recently, a new compliance report requires filtering on a field named 'department', which is not currently part of the data model. You add 'department' as a new field to the root event of the data model. After this change, reports using the data model become slower. The data model's acceleration summary size has significantly increased. What is the most likely reason for the slowdown?
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 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
Adding the field required the acceleration summary to be rebuilt, and the new field increased the summary size because it is not constrained.
When a new field is added to the root event of an accelerated data model, the acceleration summary must be rebuilt to include that field. Because the 'department' field is not constrained (i.e., it is not part of a constraint that limits which events are included), the summary now stores values for this field across all events, significantly increasing the summary size. This larger summary takes more time to scan and process, causing queries to become slower.
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.
- ✓
Adding the field required the acceleration summary to be rebuilt, and the new field increased the summary size because it is not constrained.
Why this is correct
Adding a field increases the data stored in acceleration summaries.
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.
- ✗
The data model must be re-accelerated manually after adding a field, and the admin did not do so.
Why it's wrong here
Splunk automatically rebuilds acceleration after a data model change.
- ✗
The 'department' field has a high number of unique values, and the acceleration summary cannot handle high-cardinality fields efficiently.
Why it's wrong here
While high cardinality can affect performance, the primary issue is summary size.
- ✗
The new field caused the root event constraint to become more inclusive, adding more events.
Why it's wrong here
Constraints are unchanged; only a field was added.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume high cardinality (Option C) is the culprit, but the real issue is the lack of a constraint on the new field, which forces the summary to store data for all events, regardless of cardinality.
Detailed technical explanation
How to think about this question
Acceleration summaries in Splunk are precomputed aggregations stored in the `tsidx` files. When an unconstrained field is added to the root event, the summary must store every unique value of that field for every event in the acceleration time range, which can dramatically inflate the summary size. In contrast, constrained fields (e.g., those used in `where` clauses) limit the events stored, keeping summaries lean. This is why best practice is to add new fields to child datasets or apply constraints to avoid bloating the root summary.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Data Models and Best Practices 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?
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: Adding the field required the acceleration summary to be rebuilt, and the new field increased the summary size because it is not constrained. — When a new field is added to the root event of an accelerated data model, the acceleration summary must be rebuilt to include that field. Because the 'department' field is not constrained (i.e., it is not part of a constraint that limits which events are included), the summary now stores values for this field across all events, significantly increasing the summary size. This larger summary takes more time to scan and process, causing queries to become slower.
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 →
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.