179 questions
No questions match those filters.
What's the actual difference between a query router and...
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 plansA descriptive controller maps a query to a label describing a property of it — needs external knowledge, time-sensitive, multi-hop — a boolean or small enum. A prescriptive router maps a query directly to an action the pipeline will actually execute: answer directly, retrieve as issued, rewrite then retrieve, decompose then retrieve, or run chain-of-thought with no retrieval. They look interchangeable and aren’t.
Bolting a hand-written policy on top of descriptive labels means enumerating every combination of label bits, and the deeper problem is that the correct action for a given combination depends on properties — hop count, ambiguity, whether the query is self-contained — that the descriptive classifier never measured. With no basis for choosing, the hand-written policy typically collapses every “needs retrieval” query into one default action, reproducing the original static pipeline minus whatever the classifier managed to skip entirely. The fix is to supervise the action directly rather than a description of the query: run every candidate action, score which one produced a correct answer at the lowest cost, and use that as a silver label — this manufactured supervision is what makes systems like Adaptive-RAG trainable without anyone hand-annotating “this query needs three hops.” The asymmetry only runs one direction: a prescriptive router’s “answer directly” or “chain-of-thought” choices subsume a when-to-retrieve decision, but a when-to-retrieve classifier says nothing about which retrieval strategy to use once it says yes.