Question 790
The deployment acceptance review finds: A scheduled report combines a broad outer search with a slow subsearch that repeats identical expensive work each run. Which response is best supported?
Explanation
Correct Answer
The immediate requirement is specific: A scheduled report combines a broad outer search with a slow subsearch that repeats identical expensive work each run. Consider materialized lookups or maintained summaries when a costly repeated subsearch computes relatively static reference data. The supporting mechanism is: Repeated subsearch execution can consume unnecessary resources when reusable data changes on a slower schedule. The consultant should confirm success when the replacement preserves match semantics and reduces repeated runtime under the expected reporting cadence.
Incorrect Answers
It addresses the separate case Job inspector exposes a remote peer delay that does not appear in the local CPU chart. That situation would call for: Correlate search job peer warnings with the specific slow or unresponsive indexer and its resource telemetry. The observed problem instead requires a different control because repeated subsearch execution can consume unnecessary resources when reusable data changes on a slower schedule.
This is a reasonable action for a different condition, such as: A developer uses join on an unbounded index dataset and blames Splunk for lost rows. There, join invokes constrained subsearch behavior and can be less suitable than aggregations, lookups, or carefully bounded alternatives. The present incident instead depends on repeated subsearch execution can consume unnecessary resources when reusable data changes on a slower schedule.
This is a reasonable action for a different condition, such as: A user uses a broad wildcard index pattern despite knowing the exact data source and time range. There, narrow indexed predicates reduce unnecessary scanned data and improve distributed retrieval efficiency. The present incident instead depends on repeated subsearch execution can consume unnecessary resources when reusable data changes on a slower schedule.