ElasticSearch ElasticSearch Core Concepts & Architecture 3

Question 1

What is the role of 'coordinating nodes' in Elasticsearch?

Accepted Answer

They route requests, reduce results, and distribute tasks across the cluster

Answer

They store primary shards only

Answer

They hold only replica shards

Answer

They manage cluster settings exclusively

Question 2

What is a 'hot-warm architecture' in Elasticsearch?

Accepted Answer

A tiered storage approach where hot nodes handle new data and warm nodes hold older data

Answer

A failover strategy using two identical clusters

Answer

A deployment model with active-active replication

Answer

A method for real-time data streaming

Question 3

What is the Elasticsearch 'refresh interval'?

Accepted Answer

The interval at which new writes are made available for search

Answer

How often replica shards sync with primary shards

Answer

The frequency of cluster state updates

Answer

How often snapshots are taken

Question 4

What does the 'translog' in Elasticsearch do?

Accepted Answer

Provides durability by recording operations before they are flushed to Lucene

Answer

Logs all HTTP requests to the cluster

Answer

Tracks changes to mappings over time

Answer

Records node join/leave events in the cluster

Question 5

What is the purpose of 'index aliases' in Elasticsearch?

Accepted Answer

To provide a stable name that can point to one or more indices, enabling zero-downtime reindexing

Answer

To create backup copies of indices

Answer

To rename fields within a mapping

Answer

To group indices by data type

Question 6

What is 'segment merging' in Elasticsearch?

Accepted Answer

The background process of merging smaller Lucene segments into larger ones to optimize storage and search performance

Answer

Combining multiple shards into one

Answer

Replicating data between nodes

Answer

Migrating an index from one cluster to another