The answer is to modify the macro definition by enclosing the `$sourcetype$` argument in quotation marks: `sourcetype="$sourcetype$"`. This is correct because when Splunk processes a macro argument containing hyphens, such as `cisco-asa`, the unquoted value is misinterpreted as a subtraction operator or a search syntax modifier, causing the search to fail silently for those specific sourcetypes. Quoting the argument forces Splunk to treat the entire hyphenated string as a literal value rather than parsing it as part of the search command. On the SPLK-1003 exam, this tests your understanding of how macro argument quoting interacts with special characters in field values—a common trap where candidates assume errors will appear in the Job Inspector, but Splunk simply skips the malformed search. A reliable memory tip: when a macro argument contains hyphens, always wrap it in double quotes to prevent the hyphen from being interpreted as a minus sign.
SPLK-1003 Macros, Saved Searches and CIM Practice Question
This SPLK-1003 practice question tests your understanding of macros, saved searches and cim. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 organization uses Splunk to monitor its network infrastructure. They have a single saved search that runs every hour to create a summary index for each of the 50 network device sourcetypes. The saved search uses a macro named `build_network_summary` that accepts two arguments: `sourcetype` and `time_range`. The macro definition is:
The saved search iterates over the 50 sourcetypes using a separate lookup or list. Recently, the security team noticed that the network_summary index is missing data for certain sourcetypes, specifically those with hyphens in their names (e.g., `cisco-asa`, `juniper-srx`). For other sourcetypes, the summary is complete. The saved search runs without errors in Splunk's job inspector. Which course of action should the administrator take to resolve the issue?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Modify the macro definition to enclose the `$sourcetype$` argument in quotation marks: `sourcetype="$sourcetype$"`
Option A is correct: the hyphens in sourcetype names are being interpreted as subtraction operators or search syntax modifiers because the macro argument is not quoted. Option B would increase load but not fix the parsing. Option C addresses time range, not sourcetype. Option D is unrelated.
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.
✗
Increase the summary index range to cover all sourcetypes in one pass rather than iterating.
Why it's wrong here
This does not address the parsing issue with hyphens.
✓
Modify the macro definition to enclose the `$sourcetype$` argument in quotation marks: `sourcetype="$sourcetype$"`
Why this is correct
Quoting prevents hyphens from being interpreted as search operators.
Related concept
Read the scenario before looking for a memorised answer.
✗
Change the macro's time_range argument to use a static time range to avoid relative time issues.
Why it's wrong here
Time range is not the cause; the problem is specific to sourcetypes with hyphens.
✗
Enable acceleration on the network_summary index to improve data completeness.
Why it's wrong here
Acceleration does not affect the data insertion process.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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-1003 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 SPLK-1003 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Macros, Saved Searches and CIM — This question tests Macros, Saved Searches and CIM — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Modify the macro definition to enclose the `$sourcetype$` argument in quotation marks: `sourcetype="$sourcetype$"` — Option A is correct: the hyphens in sourcetype names are being interpreted as subtraction operators or search syntax modifiers because the macro argument is not quoted. Option B would increase load but not fix the parsing. Option C addresses time range, not sourcetype. Option D is unrelated.
What should I do if I get this SPLK-1003 question wrong?
Identify which SPLK-1003 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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-1003 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-1003 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.