Practice query understanding vocabulary: query parsing, expansion, spell correction, intent classification, and query normalization in search engineering.
0 / 10 completed
1 / 10
'Query _____ (synonyms, stemming)' adds related terms to improve search recall.
Query expansion adds synonyms, related terms, and stemmed variants to the user's query to retrieve more relevant results the user might not have found with exact keyword matching.
2 / 10
'The user typed java script — normalize to javascript.' What query processing step is this?
Query normalization standardizes query tokens (merging 'java script' to 'javascript', lowercasing, removing special characters) to improve matching against the index.
The three main query intent classes are: navigational (find a specific site), informational (learn about a topic), and transactional (complete an action like buying). Each warrants different ranking strategies.
4 / 10
'Spell correction' in search is important because:
Spell correction (e.g., 'serach' → 'search') is critical for search precision — typos are common and without correction they result in zero results for valid user intents.
5 / 10
What is 'query parsing' in search?
Query parsing interprets the raw query string — tokenizing it, identifying field-specific terms (title:foo), boolean operators (AND/OR/NOT), and phrase queries ('exact phrase') — before search execution.
6 / 10
Liam from the backend team commented on a code review: 'This query is returning too many results. We need to refine it.' Which of the following best describes what Liam is suggesting?
Liam is referring to optimizing the SQL query itself. While index tuning and schema normalization can *indirectly* impact performance, the core issue he identifies is with the logic of the query. Query optimization focuses on rewriting or modifying the SQL to reduce the number of rows returned.
7 / 10
Sarah sent a Slack message: 'I'm seeing a lot of users submitting queries like 'find all users with name start with A'. The search engine is struggling to understand this natural language.' What does Sarah's message primarily highlight?
Sarah's message focuses on the challenge of translating a user's natural language query ('find all users with name start with A') into a format that the search engine can understand. Query reformulation is the process of transforming such queries into structured queries, often involving stemming and normalization.
8 / 10
The API response from a search service for the query 'customer support' is:
{"query_intent": "help", "keywords": ["customer", "support"], "relevance_score": 0.95}
What does the `query_intent` field in this JSON indicate?
The `query_intent` field classifies the *purpose* of the user's search. In this case, a relevance score of 0.95 combined with keywords like 'customer' and 'support' strongly suggests that the user is seeking help or troubleshooting related to customer support services.
9 / 10
Mark wrote a PR description for a change to the search algorithm: 'We've implemented stemming and lowercasing to improve query matching.' What is the primary purpose of these techniques?
Stemming and lowercasing are normalization techniques used to handle variations in how users might type their queries. Stemming reduces words to their root form (e.g., 'running' becomes 'run'), while lowercasing converts all text to lowercase. This allows the search engine to match queries even if they don't exactly match the indexed terms, increasing recall.
10 / 10
During a standup meeting, David says: 'We need to improve our query latency. Some users are waiting over 5 seconds for results.' What is David primarily raising concerns about?
David is directly addressing query latency – the time it takes to execute a query. High latency (over 5 seconds) indicates a problem with the system's ability to handle queries efficiently, likely due to issues like concurrent requests or inefficient processing.
What will I learn from the "Query Understanding Vocabulary" exercise?
Practice query understanding vocabulary: query parsing, expansion, spell correction, intent classification, and query normalization in search engineering.
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.