Elasticsearch easy
What is the primary architectural role of **Logstash** within the Elastic Stack?
- A It acts as a server-side processing pipeline that ingests data from various sources, transforms it, and ships it to Elasticsearch.
- B It is a frontend dashboarding tool for executive reporting.
- C It provides a load-balanced endpoint for search queries from the application.
- D It is the primary persistent storage layer for the cluster's system logs.
Answer: A. It acts as a server-side processing pipeline that ingests data from various sources, transforms it, and ships it to Elasticsearch.
Logstash allows for complex data 'munging'. You can take a messy CSV file, parse standard fields, enrich them (e.g., adding GeoIP data to an IP address), and then output the clean document to Elasticsearch for indexing.
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?
- 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?