How would you answer an interview scenario involving RAG freshness and re-indexing?

For an interview scenario involving RAG freshness and re-indexing, I would first clarify the business goal, scale, constraints, and the failure or quality attribute the interviewer wants to explore. Freshness is the ability of a RAG system to reflect document additions, updates, removals, and access changes promptly. In this scenario, for frequently changing policies, explain how you would design ingestion and re-indexing so outdated policy text stops appearing in answers quickly. I would then explain the main alternatives and tradeoffs, identify likely failure modes, and describe how I would validate the solution through testing, observability, security controls, and recovery or rollback planning.