- A
Add `| stats sum(amount) by _time, trans_type` before timechart.
Why wrong: Timechart already groups by time; this would cause double grouping.
- B
Use `| eval trans_type=split(trans_type, ",") | mvexpand trans_type | timechart sum(amount) by trans_type`.
Handles multivalue fields.
- C
Use `| chart sum(amount) by trans_type` instead of timechart.
Why wrong: Loses daily breakdown.
- D
Use `| makemv trans_type | timechart sum(amount) by trans_type`.
Why wrong: Makemv may not split correctly if delimiter is not space.
Quick Answer
The correct answer is to use `| eval trans_type=split(trans_type, ",") | mvexpand trans_type | timechart sum(amount) by trans_type`. This is necessary because the `trans_type` field contains multiple values stored as a single string, such as 'credit,debit,transfer', and the `timechart` command cannot separate these into distinct series without first expanding them. The `split()` function breaks the comma-separated string into a multivalue field, and `mvexpand` creates a separate event for each value, allowing `timechart` to correctly aggregate and display each transaction type as its own series. On the Splunk SPLK-1002 exam, this scenario tests your understanding of handling multivalue fields in timechart, a common trap where candidates forget to expand multivalue data before using statistical commands. A helpful memory tip is "split then expand, or your chart will be bland"—always remember to break apart and expand multivalue fields before any aggregation command like `timechart` or `stats`.
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.
You are a Splunk analyst for a financial services firm. You need to create a weekly report for management showing the total transaction value and number of transactions per day, broken down by transaction type (credit, debit, transfer). The data is in index=transactions with fields: trans_date, trans_type, amount. The report should be sent via email every Monday morning at 8 AM. You have created a report with the search: `index=transactions | timechart sum(amount) by trans_type`. However, the timechart shows only one series because the trans_type field has multiple values. You need to fix the search so that it correctly separates by trans_type. Additionally, you need to schedule the report. What should you do?
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
Use `| eval trans_type=split(trans_type, ",") | mvexpand trans_type | timechart sum(amount) by trans_type`.
Option B is correct because the trans_type field contains multiple values in a single field (e.g., 'credit,debit,transfer'), so you must first split the values using `split()` and then expand them with `mvexpand` before using `timechart` to correctly separate the series. This ensures each transaction type is treated as an individual event for the aggregation.
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.
- ✗
Add `| stats sum(amount) by _time, trans_type` before timechart.
Why it's wrong here
Timechart already groups by time; this would cause double grouping.
- ✓
Use `| eval trans_type=split(trans_type, ",") | mvexpand trans_type | timechart sum(amount) by trans_type`.
Why this is correct
Handles multivalue fields.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use `| chart sum(amount) by trans_type` instead of timechart.
Why it's wrong here
Loses daily breakdown.
- ✗
Use `| makemv trans_type | timechart sum(amount) by trans_type`.
Why it's wrong here
Makemv may not split correctly if delimiter is not space.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Splunk often tests the distinction between `makemv` (which works on space-delimited or newline-delimited multivalue fields) and `split`/`mvexpand` (which handles custom delimiters like commas), leading candidates to incorrectly choose `makemv` for comma-separated data.
Detailed technical explanation
How to think about this question
The `split()` function creates a multivalue field from a string using a delimiter, and `mvexpand` expands each multivalue element into a separate event, allowing `timechart` to aggregate by each individual trans_type. Without this expansion, `timechart` treats the multivalue field as a single value, resulting in only one series. This technique is essential when fields contain comma-separated lists, such as tags or categories, that need to be analyzed independently.
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.
- →
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: Use `| eval trans_type=split(trans_type, ",") | mvexpand trans_type | timechart sum(amount) by trans_type`. — Option B is correct because the trans_type field contains multiple values in a single field (e.g., 'credit,debit,transfer'), so you must first split the values using `split()` and then expand them with `mvexpand` before using `timechart` to correctly separate the series. This ensures each transaction type is treated as an individual event for the aggregation.
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.
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 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.