Elasticsearch easy
What is the primary benefit of splitting an Elasticsearch index into multiple 'Primary Shards'?
- A It encrypts the data to prevent unauthorized access by other nodes.
- B It enables Horizontal Scaling by allowing the index's total data and search load to be distributed across multiple physical servers (Nodes).
- C It forces the data to be stored on SSDs instead of HDDs.
- D It automatically compresses the data using the Zlib algorithm.
Answer: B. It enables Horizontal Scaling by allowing the index's total data and search load to be distributed across multiple physical servers (Nodes).
Shards are the fundamental unit of scale. A single node has CPU and RAM limits; by sharding, a 10TB index can be spread across 50 nodes, each handling a proportional slice of the data and queries.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- What are the two primary reasons for configuring one or more 'Replica Shards' for an index?
- When a String field is mapped as `text`, what process is performed to enable full-text search capability?
- Every document stored in an Elasticsearch index is uniquely tracked by which mandatory metadata field?
- Elasticsearch search results include a metadata field called `_score`. What does this value primarily indicate?
- What is the primary architectural purpose of Elasticsearch in a modern software stack?
- In the standard Elastic Stack architecture, what is the primary function of **Kibana**?