179 questions
No questions match those filters.
Your RAG system is giving wrong answers in production....
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansThe instinct is to blame the model, but that’s almost always the wrong place to start. Work backward through the pipeline instead: first confirm the right document is actually showing up in the top-k retrieved results — if it isn’t, nothing downstream matters. Then check whether chunking is cutting content in a way that strips necessary context, or padding it with so much surrounding noise that the signal gets diluted. After that, check whether the embedding model was built for general text and is quietly underperforming on domain-specific vocabulary like legal or medical terminology.
Only once retrieval, chunking, and embeddings check out is it worth looking at whether the LLM is ignoring the context it was handed — usually a prompt problem, not a model capability problem. And it’s worth checking the index itself for duplicate or outdated documents that get retrieved alongside the current version and confuse the model about which one to trust.
A support bot that kept quoting a 2023 no-refunds policy after the policy had changed is a textbook case: both the old and new policy documents were sitting in the vector store with no versioning, and the model had no way to know which one was current. Adding a date or version field to the metadata and filtering on it fixed it without touching the model at all.