Design a RAG system that supports both fresh operational data and slower-changing reference docs.

Instruction: Explain how you would combine hot data and cold knowledge in one retrieval experience.

Context: Assesses whether the candidate can design a practical architecture and explain the main tradeoffs. Explain how you would combine hot data and cold knowledge in one retrieval experience.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would use two knowledge paths with a shared answer contract. Operational data is fresh, volatile, and often best accessed through APIs, databases, or near-real-time indexes. Reference docs are slower-changing and fit classic document retrieval well...

Upgrade to view official answer

Related Questions