Build fluency in the vocabulary of storing and retrieving embeddings by semantic similarity.
0 / 5 completed
1 / 5
At standup, a dev mentions storing document embeddings so that a query can retrieve the most semantically similar entries rather than ones matching exact keywords. What kind of database supports this?
A vector database stores high-dimensional embeddings and retrieves entries by semantic similarity rather than exact keyword matching, letting a query surface conceptually related results even when the wording differs. This underlies most modern semantic search and retrieval-augmented generation systems. A traditional relational database indexed on exact keys isn't built for this kind of similarity comparison.
2 / 5
During a design review, the team wants to reduce search latency by grouping nearby vectors so a query only compares against a relevant subset instead of every stored vector. Which capability supports this?
Approximate nearest neighbor indexing organizes vectors into a structure, like a graph or set of clusters, so a query only needs to compare against a relevant subset rather than every vector in the store. This trades a small amount of accuracy for a large gain in search speed at scale. A full linear scan stays exact but becomes impractically slow as the number of stored vectors grows.
3 / 5
In a code review, a dev notices a search query is configured to also filter results by a metadata field, like a document's category, in addition to vector similarity. What does this represent?
Metadata filtering combined with vector search narrows results to only those matching a specific attribute, like category or date, while still ranking by semantic similarity within that filtered subset. This lets a query be both semantically relevant and constrained to a meaningful scope. Relying on vector similarity alone can surface results that are conceptually close but practically irrelevant, like the wrong category or an outdated document.
4 / 5
An incident report shows a vector database's index went stale after the underlying documents were updated, so queries kept returning outdated embeddings. What practice would prevent this?
Re-embedding and re-indexing an updated document as part of the same update pipeline keeps the vector store's search results consistent with the document's current content. Assuming the index automatically stays current skips a real step, since the embedding was computed once and won't update itself. This synchronization step matters most for a system where source documents change frequently.
5 / 5
During a PR review, a teammate asks why the team uses a vector database instead of relying on traditional keyword search for this retrieval feature. What is the reasoning?
Keyword search matches literal terms, so it misses a relevant result phrased differently even if the underlying meaning is the same. A vector database compares semantic meaning through embeddings, surfacing conceptually related results regardless of exact wording. The tradeoff is the added complexity of generating, storing, and keeping embeddings up to date compared to a simpler keyword index.
What does the "Vector Database Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to vector database vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.