Practise vocabulary for search autocomplete: suggesters, did-you-mean, fuzzy matching, n-grams, and personalised suggestions.
0 / 10 completed
1 / 10
A ___ in Elasticsearch is a specialised data structure that enables fast prefix-based autocomplete as users type.
The completion suggester uses a finite state transducer (FST) data structure optimised for prefix queries. It returns suggestions sorted by weight (popularity) for the typed prefix, enabling instant autocomplete with < 10ms latency.
2 / 10
'Did You Mean?' functionality corrects user typos by suggesting the ___ term in the index to their misspelled query.
Did-You-Mean uses edit distance (Levenshtein distance) to find indexed terms close to the user's query. Elasticsearch's phrase suggester checks for word-level corrections using the Lucene index, returning the most likely correction.
3 / 10
___ matching allows queries to match documents even when the query term has minor spelling variations — controlled by a maximum edit distance.
Fuzzy matching uses edit distance (insertions, deletions, substitutions, transpositions) to match terms with up to N differences from the query term. Elasticsearch fuzzy queries accept AUTO (auto-detect fuzziness based on term length) or explicit values 0, 1, 2.
4 / 10
N-gram tokenisation splits text into all possible substrings of length N — used to enable ___ matching even in the middle of a word.
N-gram tokenisation (bigram: 'search' → 'se', 'ea', 'ar', 'rc', 'ch') enables matching at any position within a word. This allows users to search 'arch' and find 'search', 'architecture' — essential for autocomplete within words.
5 / 10
___ autocomplete suggestions are ranked based on the specific user's past queries and clicks, not just global popularity.
Personalised autocomplete uses the user's query history, click behaviour, and preferences to rank suggestions. A user who frequently searches for Python resources sees Python-related suggestions ranked higher than a user who searches for Java.
6 / 10
During a code review of a new search feature for our e-commerce platform, Alice comments: 'I'm seeing that the autocomplete suggestions are returning results for 'red shoes' when users type 'red'. This is likely due to fuzzy matching being enabled without proper indexing. What does Alice mean in this context?',
Alice describes fuzzy matching, which allows for approximate matches due to variations in spelling or word order. It's a common issue when using autocomplete without proper configuration – simply having many documents with similar terms doesn't automatically make it a good search result; the algorithm needs to handle those differences. The other options represent incorrect assumptions about how autocomplete typically functions.
7 / 10
You receive a Slack message from Ben: 'The API response for our product search is taking forever! I'm seeing a huge number of suggestions being returned. I think we need to adjust the ngram tokenisation settings.' What is Ben referring to?
Ben is discussing ngram tokenisation, a technique where text is split into smaller units (n-grams) – usually sequences of words. This is fundamental to autocomplete because it allows the system to understand and suggest completions based on these word groupings. The other options represent different aspects of an API response or search ranking.
8 / 10
You're writing a PR description for a change that improves the accuracy of our autocomplete suggestions. You want to explain why you've implemented context-aware ranking. What is the best way to describe it?
Context-aware ranking means that autocomplete suggestions aren't just based on global popularity. Instead, they factor in the individual user's behavior – their past searches and clicks – to provide more personalized and relevant results. This is a crucial element of effective autocomplete systems.
9 / 10
During a standup meeting, Sarah says: 'We're using prefix matching to improve the speed of our search queries'. What does she mean?
prefix matching is an indexing technique where documents are organized so that searches starting with a specific prefix can be quickly identified. This dramatically speeds up search operations because it avoids scanning the entire index for every query. It's a core optimization strategy.
10 / 10
You're reviewing code that implements autocomplete suggestions in our mobile app. The developers have used a system that learns from user behavior to rank the suggestions. What is this approach most closely related to?
This describes personalized ranking. This approach uses machine learning to adapt the autocomplete suggestions to each user's unique behavior and preferences – this is a key differentiator from simple global popularity-based rankings. The other options represent alternative approaches that don't account for individual user data.
What will I learn from the "Autocomplete & Suggestions Vocabulary" exercise?
Practise vocabulary for search autocomplete: suggesters, did-you-mean, fuzzy matching, n-grams, and personalised suggestions.
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.