Practise vocabulary for the query understanding pipeline: tokenisation, spell correction, synonym expansion, and intent classification.
0 / 10 completed
1 / 10
Splitting the raw query string into individual terms is ___.
Tokenisation breaks the query into tokens (words/subwords) that downstream stages can process.
2 / 10
Reducing 'running' and 'ran' to a common root is ___.
Stemming or lemmatisation normalises word forms so a search for one form matches documents using another.
3 / 10
Automatically fixing 'iphnoe' to 'iphone' is ___ correction.
Spell correction (typo tolerance) maps misspelled queries to likely intended terms so users still get results.
4 / 10
Treating 'laptop' and 'notebook' as equivalent uses ___ expansion.
Synonym expansion broadens a query to include equivalent terms, improving recall for varied phrasing.
5 / 10
Deciding whether a query is navigational, informational, or transactional is ___ classification.
Intent classification routes the query appropriately (e.g. show a product page vs articles), tailoring the experience to what the user wants.
6 / 10
During a code review of a query builder component, Alice comments: 'This regex is overly complex; we should use a more targeted approach to avoid unnecessary processing. Specifically, breaking down the search term into individual components would improve performance.' What does Alice mean in this context?
Alice refers to 'splitting' the query string – this is a common optimization technique. By breaking down a complex search term into smaller parts, you can dramatically reduce the scope and complexity of the regular expression needed. This avoids unnecessary matching and improves performance, especially when dealing with large datasets or complex patterns. The other options represent less efficient approaches.
7 / 10
In a Slack channel discussing query optimization, Ben writes: 'I'm using fuzzy matching to handle typos and variations in user search queries. We're normalizing the input by applying a common root for terms like 'running' and 'ran'.' What technique is Ben describing?
Ben is using lemmatization, a more sophisticated technique than stemming. Lemmatization aims to find the root form of a word ('lemma') based on its context, unlike stemming which simply chops off suffixes regardless of meaning. This ensures that 'running' and 'ran' are treated as equivalent for matching purposes – a key benefit of fuzzy search implementations. Stemming is a simpler, less accurate approach.
8 / 10
Sarah is reviewing the documentation for an API that handles search queries and notices the following: 'The system automatically corrects common misspellings like 'iphnoe' to 'iphone'.' What type of correction does this represent?
This is an example of fuzzy string matching. The API isn't simply correcting a single typo; it's using algorithms to find strings that *resemble* 'iphnoe', even if they contain minor errors. This allows for more robust search functionality when users make typos or use slightly different phrasing. Typographical error correction is too narrow, and regular expression substitution doesn't typically handle this level of similarity.
9 / 10
During a standup meeting, David explains: 'We're using query expansion to broaden our search results. We treat 'laptop' and 'notebook' as equivalent terms—effectively expanding the query with related concepts.' What technique is David describing?
David is employing query expansion, a technique designed to improve the breadth of a search. By treating 'laptop' and 'notebook' as equivalent, he's effectively adding related terms to the original query. This helps capture more relevant results that might not have been found using just the initial term, significantly increasing recall – the ability to find *all* relevant documents. Keyword filtering is a pre-processing step, while ranking algorithms determine order.
10 / 10
You're writing a PR description for a change that improves query understanding. You want to accurately describe the system's behavior. Which statement best summarizes the core function of this process?
Query classification is fundamental to effective query understanding. Determining whether a query is navigational (e.g., 'find Amazon'), informational (e.g., 'what is the weather?'), or transactional (e.g., 'buy headphones') dictates how the system should interpret and process it. This allows for targeted search strategies, leading to more relevant results. The other options represent different but distinct aspects of query processing.
What will I learn from the "Query Understanding Pipeline Vocabulary" exercise?
Practise vocabulary for the query understanding pipeline: tokenisation, spell correction, synonym expansion, and intent classification.
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.