Practise vocabulary for search indexing: inverted indexes, mappings, shards, replicas, and index lifecycle operations.
0 / 10 completed
1 / 10
An ___ index is the core data structure of a search engine — it maps each unique term to the list of documents containing that term.
An inverted index maps terms to document IDs (like a book index maps topics to page numbers). This enables fast full-text search: given a query term, find all documents instantly without scanning every document.
2 / 10
In Elasticsearch/OpenSearch, a ___ defines the data types and analysis rules for each field in an index.
A mapping defines how each field is indexed: text (full-text analysed), keyword (exact match), integer, date, geo_point, etc. Mappings affect query behaviour — a text field uses the analyser; a keyword field does exact matching.
3 / 10
A ___ is a horizontal partition of an Elasticsearch index — distributing data across nodes for parallelism and capacity.
Shards divide an index's data across nodes. More shards = more parallelism (faster indexing and querying) but more overhead. An index with 5 shards distributes documents across 5 shards, each on potentially different nodes.
4 / 10
A ___ is a copy of a shard on a different node, providing fault tolerance and increased read throughput.
Replicas are copies of primary shards on different nodes. If a primary fails, a replica promotes to primary (fault tolerance). Replicas also serve read requests, increasing query throughput.
5 / 10
An ___ in Elasticsearch converts text to lowercase, removes stop words, and applies stemming before indexing.
An analyser processes text through: character filters, tokeniser (split into tokens), and token filters (lowercase, stop words, stemming). The same analyser is applied at index time and query time to ensure consistent matching.
6 / 10
John from the Search Team sent a Slack message: 'Hey team, we're seeing slow query times on the user search index. I suspect it's related to the new `product_category` field being indexed without stemming. Can someone investigate?' What does stemming refer to in this context?
Stemming is a crucial process in indexing that transforms words to their root form – like 'running' becoming 'run'. This significantly reduces the number of distinct terms in the index, improving search performance and minimizing storage requirements. The misconception here is often confusing stemming with spell checking or duplicate copies; it's about algorithmic reduction.
7 / 10
You're reviewing a pull request for a new e-commerce search feature. The PR description reads: 'We've implemented inverted indexes to optimize query speed and added a `keyword_analyzer` mapping to the product_name field. What is a keyword_analyzer primarily used for?',
An keyword_analyzer is a specific type of analysis mapping defined within an Elasticsearch index. It dictates how text data is processed during indexing – in this case, tokenizing and potentially stemming. The core purpose is to transform raw text into searchable terms, aligning with the needs of the search query. It's distinct from ranking or filtering; those are separate functionalities.
8 / 10
During a standup meeting, Sarah explains that her team is using Elasticsearch for their customer support search index. She states, 'We're employing sharding to handle the volume of queries.' What does sharding achieve?
Sharding is a fundamental Elasticsearch concept that distributes an index across multiple nodes. This parallel processing dramatically improves query speed and overall system capacity, especially when dealing with large datasets. It's not about encryption or deletion; those are separate operations, though sharding *indirectly* contributes to security by reducing the load on any single node.
9 / 10
You're debugging a slow search query. The Elasticsearch monitoring dashboard shows high CPU usage on one of your nodes. You discover that the node is heavily involved in replicating a shard. What does replication primarily serve to do?
Replication is a core resilience mechanism in Elasticsearch. It creates multiple copies of each shard on different nodes. This redundancy protects against data loss if one node fails and significantly increases read performance by allowing queries to be served from any replica, not just the primary.
10 / 10
You're designing a new search index for a social media platform. You need to ensure that searches are case-insensitive and performant. Which Elasticsearch setting would be most appropriate to configure?
The analysis.analyzer setting within Elasticsearch controls the pre-processing of text fields before indexing. Specifically, configuring it with a lowercase analyzer ensures that all text is converted to lowercase during indexing, resulting in case-insensitive search results. Other options relate to different aspects of index management but don't directly address case sensitivity.
What will I learn from the "Search Index Vocabulary" exercise?
Practise vocabulary for search indexing: inverted indexes, mappings, shards, replicas, and index lifecycle operations.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Search Engineering Language exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss search engineering language topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Search Engineering Language exercises?
See the full Search Engineering Language exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.