- A
Replace the real-time search with a base search that runs every 10 minutes
Why wrong: A base search would still scan all data every 10 minutes, which is heavy.
- B
Implement a summary index that aggregates events per second by sourcetype every minute, and have the dashboard search the summary index
Summary indexing pre-computes aggregated data, drastically reducing search volume.
- C
Change the real-time window to a 10-minute historical search and enable report acceleration
Why wrong: Report acceleration can speed up repeating historical searches, but it still needs to scan the raw data for the first acceleration.
- D
Create a data model for all sourcetypes and use acceleration on the data model
Why wrong: Data model acceleration works over time, but the initial acceleration for 2 TB/day is resource-intensive and not suited for real-time.
Quick Answer
The answer is to implement a summary index that aggregates events per second by sourcetype every minute, and have the dashboard search that summary index. This is correct because a summary index pre-aggregates data at a regular interval, such as every minute, which drastically reduces the volume of data the dashboard must scan; instead of processing 2 TB of raw logs in real time, the dashboard queries a small, precomputed table, eliminating the performance bottleneck caused by the heavy forwarder’s high ingestion rate. On the SPLK-1002 exam, this tests your understanding of summary index optimization for real-time dashboards, a key strategy when dealing with large-scale data and broad searches like `index=* | stats count by sourcetype`. A common trap is to assume adding more hardware or using a faster search command will fix the issue, but the core problem is the raw data volume, not the search syntax. Remember the memory tip: “Summarize first, search later” — summary indexes turn a firehose of data into a sip, making real-time dashboards fast and reliable.
SPLK-1002 Practice Question: Creating Reports, Dashboards and Visualizations
This SPLK-1002 practice question tests your understanding of creating reports, dashboards and visualizations. 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 large enterprise Splunk environment has a heavy forwarder sending 2 TB of log data per day. An operator builds a dashboard that displays a real-time chart of events per second across all data sources, using the search 'index=* | stats count by sourcetype' with a real-time window of last 10 minutes. The dashboard is extremely slow, often timing out. The operator suspects the search is too broad. Which optimization strategy should be implemented first?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"first"Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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
Implement a summary index that aggregates events per second by sourcetype every minute, and have the dashboard search the summary index
Option B is correct because a summary index pre-aggregates the events-per-second data by sourcetype at a regular interval (e.g., every minute), drastically reducing the data volume the dashboard must scan. Instead of processing 2 TB of raw logs in real time, the dashboard queries a small, precomputed table, eliminating the performance bottleneck caused by the heavy forwarder's high ingestion rate.
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.
- ✗
Replace the real-time search with a base search that runs every 10 minutes
Why it's wrong here
A base search would still scan all data every 10 minutes, which is heavy.
- ✓
Implement a summary index that aggregates events per second by sourcetype every minute, and have the dashboard search the summary index
Why this is correct
Summary indexing pre-computes aggregated data, drastically reducing search volume.
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Change the real-time window to a 10-minute historical search and enable report acceleration
Why it's wrong here
Report acceleration can speed up repeating historical searches, but it still needs to scan the raw data for the first acceleration.
- ✗
Create a data model for all sourcetypes and use acceleration on the data model
Why it's wrong here
Data model acceleration works over time, but the initial acceleration for 2 TB/day is resource-intensive and not suited for real-time.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Splunk often tests the misconception that report acceleration or data model acceleration can solve real-time performance issues, but these features are designed for historical searches and pivot-based reporting, not for reducing the raw data volume in near-real-time dashboards.
Detailed technical explanation
How to think about this question
Summary indexes work by running a scheduled search (e.g., every minute) that aggregates data (e.g., count by sourcetype) and writes the results into a separate, small index. The dashboard then queries this summary index, which contains only the aggregated rows (e.g., 1 row per sourcetype per minute) instead of millions of raw events. In a heavy forwarder environment sending 2 TB/day, this reduces the searchable data from billions of events to a few thousand summary rows, making real-time dashboards feasible without overwhelming the search head.
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.
- →
Creating Reports, Dashboards and Visualizations — study guide chapter
Learn the concepts, then practise the questions
- →
Creating Reports, Dashboards and Visualizations 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?
Creating Reports, Dashboards and Visualizations — This question tests Creating Reports, Dashboards and Visualizations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement a summary index that aggregates events per second by sourcetype every minute, and have the dashboard search the summary index — Option B is correct because a summary index pre-aggregates the events-per-second data by sourcetype at a regular interval (e.g., every minute), drastically reducing the data volume the dashboard must scan. Instead of processing 2 TB of raw logs in real time, the dashboard queries a small, precomputed table, eliminating the performance bottleneck caused by the heavy forwarder's high ingestion rate.
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: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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 →
Same concept, more angles
1 more ways this is tested on SPLK-1002
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 report is scheduled to run every hour but sometimes returns incomplete data because the search is too slow and times out. Which action should be taken to improve reliability without losing data?
hard- ✓ A.Use a summary index to pre-aggregate data
- B.Add the 'lazy' command to defer computation
- C.Reduce the time range to the last 30 minutes
- D.Increase the search auto-finalization time
Why A: A summary index pre-aggregates data at search time, storing the results in a separate index. When the report runs, it queries the summary index instead of the raw data, which is much faster and avoids timeouts. This ensures all data is captured because the summary is built incrementally from the full data set, not by sampling or truncating.
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.