Elasticsearch easy
What are the two primary reasons for configuring one or more 'Replica Shards' for an index?
- A Data obfuscation and offline archiving.
- B High Availability (recovery from node failure) and increased Read Throughput (handling more search queries).
- C Automatic data compression and deduplication.
- D Reducing the total disk storage required for the cluster.
Answer: B. High Availability (recovery from node failure) and increased Read Throughput (handling more search queries).
Replicas provide redundancy. If a node containing a Primary Shard crashes, a Replica on another node is promoted to Primary. Additionally, search queries can be distributed across all copies (Primary and Replicas), multiplying the cluster's ability to handle concurrent searches.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- When a String field is mapped as `text`, what process is performed to enable full-text search capability?
- What is the primary benefit of splitting an Elasticsearch index into multiple 'Primary Shards'?
- 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**?