SPLK-3003 · Question #61
When utilizing a subsearch within a Splunk SPL search query, which of the following statements is accurate?
The correct answer is C. Subsearches have a default result output limit of 10000. Splunk subsearches have a default result output limit of 10,000 results, along with a default time limit of 60 seconds - these constraints exist to protect search head performance when nested searches run inside brackets (e.g., index=main [search index=logs | return 5 user])…
Question
When utilizing a subsearch within a Splunk SPL search query, which of the following statements is accurate?
Options
- ASubsearches have to be initiated with the | subsearch command.
- BSubsearches can only be utilized with | inputlookup command.
- CSubsearches have a default result output limit of 10000.
- DThere are no specific limitations when using subsearches.
How the community answered
(30 responses)- A3% (1)
- B3% (1)
- C93% (28)
Explanation
Splunk subsearches have a default result output limit of 10,000 results, along with a default time limit of 60 seconds - these constraints exist to protect search head performance when nested searches run inside brackets (e.g., index=main [search index=logs | return 5 user]). Option A is wrong because subsearches are defined with square brackets [ ], not a | subsearch command - no such command exists. Option B is incorrect because subsearches work with many commands (like | search, | join, | append), not exclusively with | inputlookup. Option D is false precisely because Splunk does impose limits - the 10,000-result cap and 60-second timeout are well-defined defaults that can be adjusted in limits.conf.
Memory tip: Think "10K cap in brackets" - the square brackets that wrap a subsearch are your visual cue that results are boxed in at 10,000.
Topics
Community Discussion
No community discussion yet for this question.