Question 20
An implementation team reports: A consultant builds multiple nested expensive subsearches with no result budget or runtime review. What should the lead consultant do?
Explanation
Correct Answer
The immediate requirement is specific: A consultant builds multiple nested expensive subsearches with no result budget or runtime review. Compare supported lookups, aggregate joins, and bounded subsearches before adopting high-cardinality nested search plans. The supporting mechanism is: Subsearch result expansion and distributed joins can create significant execution and truncation overhead. The consultant should confirm success when performance tests prove complete intended result coverage within configured budget and without silent subsearch truncation.
Incorrect Answers
The alternative applies to “An analyst changes the order of an outer query and bracketed term list and gets unexpected matches”, where bracketed subsearches execute independently and contribute formatted search terms to the outer command. Here, subsearch result expansion and distributed joins can create significant execution and truncation overhead.
The alternative applies to “Job metadata reports a canceled search from quota policy rather than a remote peer crash”, where search execution can be constrained by authorization and scheduler controls independently of SPL correctness. Here, subsearch result expansion and distributed joins can create significant execution and truncation overhead.
It addresses the separate case A consultant performs costly enrichment before testing a simple indexed equality filter. That situation would call for: Push safe selective base constraints before expensive per-event extraction or enrichment steps. The observed problem instead requires a different control because subsearch result expansion and distributed joins can create significant execution and truncation overhead.