Bird
Raised Fist0

Why does Elasticsearch store async search results with an ID instead of returning all results immediately?

hard🧠 Conceptual Q10 of Q15
Elasticsearch - Advanced Patterns
Why does Elasticsearch store async search results with an ID instead of returning all results immediately?
ABecause expensive queries may take a long time, storing results allows clients to retrieve them later without blocking
BBecause Elasticsearch cannot return any results synchronously
CBecause storing results reduces the cluster memory usage drastically
DBecause async search results are always partial and never complete
Step-by-Step Solution
Solution:
  1. Step 1: Understand async search design

    Expensive queries can take long to complete, so returning immediately is not feasible.
  2. Step 2: Purpose of storing results with ID

    Storing results allows clients to fetch them later when ready, avoiding blocking connections.
  3. Final Answer:

    Because expensive queries may take a long time, storing results allows clients to retrieve them later without blocking -> Option A
  4. Quick Check:

    Async search stores results for later retrieval [OK]
Quick Trick: Async search stores results to avoid blocking clients [OK]
Common Mistakes:
MISTAKES
  • Thinking Elasticsearch cannot return synchronous results
  • Assuming storing results reduces memory drastically
  • Believing async search results are always partial

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Elasticsearch Quizzes