179 questions
No questions match those filters.
Retrieved knowledge can be injected into a model as tex...
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 plansThese are three different points on the same trade-off between flexibility, cost, and auditability.
Text injection — standard RAG, placing retrieved passages directly in the prompt — is the most flexible: trivially updatable (change the datastore, not the model), easy to cite and audit (the source text is right there), but it costs real context-window tokens per request and is hard-bounded by how much fits in the context window at once.
Embedding-level injection — incorporating retrieved information as vector representations fused into the model’s hidden states rather than as literal tokens — is more compact and can incorporate more information per unit of compute, but is much less interpretable: you can no longer point to the exact source text that produced a given output, which is a serious problem for any application needing citations or auditability.
Parameter-level injection — fine-tuning the model on the knowledge so it’s baked into the weights — is the most compute-efficient at inference time (no retrieval step, no extra context tokens at all), but it’s the slowest and most expensive to update (a training run per change) and the hardest to audit, since there’s no way to point to “where” a fact lives in a weight matrix. Which one is right depends entirely on how often the knowledge changes and how much you need to prove where an answer came from.