Rag And Retrieval medium
For failing queries, your evaluation shows the gold chunk is present in the top-5 context 92% of the time. The answers still ignore it or hedge. The team proposes migrating to a different vector database. Where should effort go?
- A Swap to a different vector database, since a better ANN index will raise recall at 5 above its current level.
- B Increase top-k from 5 to 25 so the generator sees more supporting evidence for each failing question.
- C Add a cross-encoder reranker, because the gold chunk is likely ranked too low within the top-5 window.
- D Treat it as a generation problem and iterate on the prompt, context formatting, and grounding instructions.
Answer: D. Treat it as a generation problem and iterate on the prompt, context formatting, and grounding instructions.
**Evaluate retrieval and generation separately.** When the gold chunk is already in context and the answer is still wrong, the failure is in prompting or grounding, not in search. Changing the vector store or k leaves the actual cause untouched, and a larger k adds noise. Retrieval changes are the right lever when recall at k itself is low.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- You must index 100M chunks using a 3,072-dimension embedding in fp32, served from RAM via HNSW. The raw vectors alone take about 1.2 TB before graph overhead. You need to cut memory several-fold while losing at most a point or two of recall@10. Which approach fits?
- A multi-tenant SaaS app stores all tenants in one vector index with a tenant_id field. Queries fetch the top 20 chunks by similarity and then drop chunks from other tenants. Small tenants often get 0-2 results. Why does this happen, and what is the fix?
- Runbooks are split into fixed 300-token chunks with no overlap. When a procedure step starts near the end of one chunk and finishes in the next, answers come back incomplete. What is the lowest-cost fix?
- Your offline eval shows recall@5 of 92% on a labeled set, so the gold passage is in the context for nearly every question. Yet human graders mark 35% of answers wrong, and the wrong answers often ignore or contradict the gold passage. Where should the team invest next?
- Your product requires every RAG answer to include clickable source citations that users can verify. How should those citations be produced?
- A runbook RAG system uses fixed 500-token chunks with no overlap. Users who ask for a multi-step recovery procedure get answers that stop at step 4 of 9, and retrieval logs show the top hit ends mid-procedure. What is the most targeted fix?