SproutStackSproutStack home
Section checkpoint

Head-to-head comparisons

10 questions drawn from the 10 chapters in this section. If most land on the first try, you are ready for the next section. If not, the explanation after each answer says which idea to revisit.

Checkpoint

10 questions · first-try answers earn the most XP

1. What is the honest limitation the chapter names about FireDucks specifically?
2. You need to prove a concept to a stakeholder this week with no budget. Which constraint matters most?
3. Why does the chapter say a RAG system with top-K=4 rarely needs the largest available context window?
4. What does the chapter mean by abstractions hiding prompts, retries, and costs?
5. You need tenant isolation so one customer's search can never return another's chunks. What does pgvector give you here?
6. You need a model that writes a customer reply, explains a stack trace, or drafts code. Which one fits?
7. Orders for each customer must be processed in order, but one SQS FIFO queue without batching is too slow. What keeps per-customer order and raises throughput?
8. Your team wants answers that follow a strict legal format and use up-to-date contracts. What's the sensible combination?
9. You are opening an API to outside partners who use many different languages and tools. Which choice is usually the safest default?
10. A teammate says llama.cpp only works on NVIDIA GPUs and cannot serve an API. Which correction is accurate?

What this checkpoint covers