ELK Stack Interview FAQs: Quick-Answer Cheat Sheet (2027)
Quick-answer ELK Stack interview cheat sheet: 32 short Q&As on Logstash pipelines, shards, data views, ILM, cluster health and troubleshooting.
The ELK Stack is Elasticsearch for storing and searching data, Logstash for collecting and transforming it, and Kibana for exploring and visualising it. In DevOps interviews you are expected to explain how logs flow through these parts, how indices and shards behave, and how to keep a logging cluster healthy and affordable.
This page is a cheat sheet: short, direct answers you can revise the night before an interview. It is deliberately brief. For the full question bank go to our 80+ ELK Stack interview questions, for senior-level depth use the advanced ELK questions, and for monitoring-focused rounds see ELK for DevOps monitoring. If you need the background first, read the role of ELK in centralized logging.
Key takeaways
- Logstash processes events in three stages: inputs, filters and outputs. Codecs handle encoding and decoding inside inputs and outputs.
- Kibana now calls index patterns "data views". Using the current name in an interview shows you have worked with a recent version.
- Index lifecycle management (ILM) moves indices through hot, warm, cold, frozen and delete phases, and rollover creates a new write index at a size, document count or age threshold.
- Most production ELK problems come down to shard sizing, mapping choices, and retention, so prepare stories about those.
- Give the direct answer first, then one practical detail. That is what interviewers mean by a crisp answer.
The stack in one table
| Component | Job | What interviewers probe |
|---|---|---|
| Elasticsearch | Distributed search and analytics engine that stores documents in indices | Shards, replicas, mappings, cluster health, query types |
| Logstash | Pipeline that ingests, parses and routes events | Pipeline stages, grok, codecs, performance, failure handling |
| Kibana | UI for search, dashboards and stack management | Data views, Discover, Lens, dashboards, alerting |
| Beats and Elastic Agent | Lightweight shippers that collect logs and metrics at the source | When to ship direct to Elasticsearch versus through Logstash, Fleet management |
Beginner FAQs
- What does ELK stand for?
Elasticsearch, Logstash and Kibana. With Beats added, Elastic calls the set the Elastic Stack. - What is an index in Elasticsearch?
A logical collection of documents with a shared mapping. Physically it is split into shards spread across nodes. - What is a shard, and what is a replica?
A primary shard holds part of an index's data. A replica is a copy of a primary on a different node. Replicas give redundancy and extra read capacity. - What is a mapping?
The schema for an index: which fields exist and their types, such as keyword, text, date or long. A wrong mapping is hard to change later and usually means reindexing. - Text versus keyword?
Text fields are analysed (split into terms) for full-text search. Keyword fields are stored as exact values, which suits filtering, sorting and aggregations. - What are the three stages of a Logstash pipeline?
Inputs create events from a source, filters transform them, and outputs send them to destinations. - What is a codec in Logstash?
A stream filter that runs inside an input or output to decode or encode data, for examplejson, ormultilinefor joining stack trace lines into one event. - What is grok?
A Logstash filter that parses unstructured text into fields using named patterns. It is the usual way to turn a raw access log line into structured data. - What is a data view in Kibana?
The configuration that tells Kibana which indices, data streams or aliases to query. It was formerly called an index pattern. - What do the cluster health colours mean?
Green means all primary and replica shards are allocated. Yellow means all primaries are allocated but some replicas are not. Red means at least one primary shard is unallocated, so some data cannot be searched.
Intermediate FAQs
- Write a minimal Logstash pipeline that reads from Beats and writes to Elasticsearch.
Theinput { beats { port => 5044 } } filter { grok { match => { "message" => "%{COMBINEDAPACHELOG}" } } date { match => [ "timestamp", "dd/MMM/yyyy:HH:mm:ss Z" ] } } output { elasticsearch { hosts => ["https://es01:9200"] } }datefilter sets the event timestamp from the log line instead of ingest time, which keeps timelines accurate. - When should logs skip Logstash and go straight to Elasticsearch?
When the parsing needed is light and an ingest pipeline in Elasticsearch can handle it. Keep Logstash for heavy transformation, enrichment, or routing to several destinations. - What is an ingest pipeline?
A series of processors that Elasticsearch runs on documents before indexing them, such as grok, rename, or set. It moves simple parsing work off Logstash. - What is ILM?
Index lifecycle management. A policy moves indices through hot, warm, cold, frozen and delete phases based on age or size, and can roll over, shrink, or delete them. - What does rollover do?
It creates a new write index when the current one reaches a set size, document count or age. Writes go to the new index while older ones move through the lifecycle. - What is a data stream?
An append-only abstraction for time series data such as logs. Writes go through one name while Elasticsearch manages the backing indices underneath, which pairs naturally with ILM. - How do you avoid mapping explosions?
Limit dynamic mapping, define explicit mappings for known fields, and avoid using user-controlled values as field names. Every new field adds to cluster state. - Query versus filter context?
Query context scores how well documents match. Filter context only answers yes or no, skips scoring, and can be cached, so use it for exact conditions like status or time range. - How do you secure an ELK deployment?
Enable TLS between nodes and clients, turn on authentication, use role-based access so teams see only their indices, and keep Kibana behind authentication rather than exposing it openly. - Logstash is falling behind. Where do you look?
Check pipeline worker and batch settings, slow filters (grok patterns are a common culprit), and back pressure from Elasticsearch. The Logstash monitoring APIs show per-plugin event timings.
Experienced FAQs
- How do you size shards for log data?
Aim for shards that are neither tiny nor huge, and use rollover by size so each shard lands in a sensible range. Too many small shards waste heap and slow the cluster. Check Elastic's current sizing guidance for exact targets. - How do you plan hot, warm and cold tiers?
Put recent, frequently queried data on fast storage (hot), move older data to cheaper nodes (warm, cold), and use frozen or deletion for data you keep only for compliance. ILM policies automate the moves. - A cluster turns red after a node fails. What are your steps?
Find unassigned shards withGET _cluster/allocation/explain, bring the node back or restore its disks, and check whether replicas existed. If a primary is lost with no replica, restore from snapshot. - How do you back up Elasticsearch?
Use snapshots to a registered repository, such as shared storage or an object store, and schedule them with snapshot lifecycle management. Test restores, not just backups. - How would you stop one noisy service from overwhelming logging?
Rate-limit or sample at the shipper, drop debug logs at the edge, give the service its own index or data stream with shorter retention, and alert on ingest volume per source. - How do you handle events that fail parsing?
Tag them (grok adds_grokparsefailureby default) and route them to a separate index, or use Logstash's dead letter queue for events Elasticsearch rejects, then review and fix patterns. - How do you reduce storage cost without losing needed data?
Shorten retention per data type, drop unused fields, use correct mappings (keyword only where needed), and move older data to cheaper tiers or snapshots. - How does ELK compare with Prometheus and Grafana?
ELK is built around logs and full-text search. Prometheus is built for numeric time series metrics and alerting. Many teams run both, with Grafana or Kibana as the front end.
Scenario quick answers
- Dashboards show no data for the last hour.
Check the shipper is running, Logstash or the ingest pipeline is not rejecting events, the data view's time field is right, and the cluster has disk space (Elasticsearch blocks writes past its disk watermarks). - Search is slow on a large time range.
Narrow the time range, filter on keyword fields, avoid leading wildcards, check shard count per query, and look at the slow log to find the expensive queries. - Timestamps are off by hours.
The log's timezone was not parsed. Set the timezone in thedatefilter or processor so events store correct UTC time. - Disk is filling faster than planned.
Check for a new noisy source, confirm ILM is attached to the index template, and verify delete phases are actually running.
How to answer ELK questions well
Interviewers hear many memorised definitions. What stands out is a short answer plus something you did: the retention policy you set, the grok pattern you fixed, the shard count you reduced. If you have not run ELK in production, build a small lab. Ship Nginx logs with a Beat, parse them in Logstash, set an ILM policy, and build one Kibana dashboard. That one project gives you material for most of the questions above.
Learn the vocabulary of the current release, too. Saying "data view" rather than "index pattern" and knowing that data streams exist tells the panel your knowledge is recent. If you want guided practice, the ELK Stack course runs as a classroom batch in Kharadi, Pune and as live online classes.
Commands worth knowing by heart
Panels often ask how you would check something rather than what it is. These read-only API calls cover most first-look questions:
GET _cluster/health
GET _cat/nodes?v
GET _cat/indices?v&s=store.size:desc
GET _cat/shards?v
GET _cluster/allocation/explain
GET _ilm/status
Cluster health gives the colour and the count of unassigned shards. The _cat APIs give a quick table of nodes, indices and shards, and sorting indices by size shows where disk is going. Allocation explain tells you why a shard is not assigned, which is the starting point for most red or yellow clusters. Knowing these by name, and what you would look for in each, is often enough to turn a vague answer into a convincing one.
Frequently asked questions
What are the three stages of a Logstash pipeline?
Inputs, filters and outputs. Inputs create events, filters transform them, and outputs send them on.
What is the new name for Kibana index patterns?
Data views. Elastic's documentation describes a data view as formerly a Kibana index pattern.
What are the ILM phases?
Hot, warm, cold, frozen and delete.
What does a yellow cluster status mean?
All primary shards are allocated but at least one replica is not, so data is searchable but redundancy is reduced.
When do you need Logstash if Beats can send to Elasticsearch?
When you need heavy parsing, enrichment, buffering or routing to several outputs. Light parsing can run in an Elasticsearch ingest pipeline.
What is the difference between text and keyword fields?
Text is analysed for full-text search. Keyword stores exact values for filters, sorting and aggregations.
How should I prepare for an ELK interview without production experience?
Build a small lab that ships, parses, stores and visualises real logs with a retention policy, and be ready to explain each choice.
Official references
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0