RAG Frameworks — LangChain & LlamaIndex — Practice quiz
Untimed. Answers are graded when you submit, with explanations and spaced-repetition scheduling.
- Question 1easy
Fundamentally, what does a RAG framework like LangChain or LlamaIndex provide over a hand-rolled pipeline?
- Question 2easy
LlamaIndex is best characterized as:
- Question 3easy
In LangChain's LCEL, what does the `|` operator mean in `retriever | prompt | llm`?
- Question 4medium
What is LangChain's primary strength relative to LlamaIndex?
- Question 5medium
In the abstraction mapping, your hand-rolled `recursive_split` corresponds to which framework concept?
- Question 6medium
When is hand-rolling a RAG pipeline a reasonable choice? (Select all that apply)
Select all that apply.
- Question 7medium
What does LlamaIndex's `VectorStoreIndex.from_documents(docs)` do in one call?
- Question 8hard
Why wrap a framework behind your own thin `retrieve()`/`answer()` interface?
- Question 9hard
You migrate a working pipeline to a framework. What makes that swap SAFE?
- Question 10medium
Can LangChain and LlamaIndex be used together?
- Question 11medium
An ingestion-heavy app must pull from Notion, Slack, Google Drive, and SQL into one index. Which factor most favors adopting LlamaIndex?
- Question 12hard
Which caution is MOST specific to using these frameworks?
- Question 13medium
What is the name (acronym) of LangChain's expression language that composes components with the `|` operator?
- Question 14hard
Complete the rule of thumb: start hand-rolled for learning and simple cases; adopt a framework when the glue code you're writing is exactly what the framework already ____.