Bird
Raised Fist0

Why is it recommended to use filters instead of queries in saved searches when filtering data in Elasticsearch?

hard🧠 Conceptual Q10 of Q15
Elasticsearch - Kibana and Visualization
Why is it recommended to use filters instead of queries in saved searches when filtering data in Elasticsearch?
AFilters are cached and faster for repeated use, queries calculate relevance scores
BQueries are deprecated and no longer supported
CFilters return documents in random order, queries return sorted results
DQueries cannot be saved, only filters can
Step-by-Step Solution
Solution:

  1. Step 1: Understand difference between filters and queries

    Filters do not calculate relevance scores and are cached for speed.

  2. Step 2: Compare performance and usage

    Queries calculate scores and are slower; filters improve performance in saved searches.

  3. Final Answer:

    Filters are cached and faster for repeated use, queries calculate relevance scores -> Option A

  4. Quick Check:

    Filters cache and speed > queries scoring [OK]
Quick Trick: Filters cache results, queries compute scores; filters faster [OK]
Common Mistakes:
MISTAKES
  • Thinking queries are deprecated
  • Confusing order of results with filter/query difference
  • Believing queries cannot be saved

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Elasticsearch Quizzes
Advanced Patterns - Search after for efficient pagination - Quiz 12easy Advanced Patterns - Async search for expensive queries - Quiz 4medium Cluster Management - Rolling upgrades - Quiz 9hard Kibana and Visualization - Dashboard creation - Quiz 10hard Kibana and Visualization - Dashboard creation - Quiz 7medium Performance and Scaling - Shard sizing strategy - Quiz 4medium Performance and Scaling - Hot-warm-cold architecture - Quiz 10hard Performance and Scaling - Why performance tuning handles growth - Quiz 11easy Security - Authentication basics - Quiz 9hard Security - API key management - Quiz 3easy