Check yourself

Each question is tagged with the concept it tests. An outline answer follows each one. For a scored check, take the quiz below. It mixes the questions from this chapter's pages and asks 10 at a time. Zia Tutor AI holds a larger bank for practice.

1. 21.1 Name the four rungs, and what each takes over. Your loop (nothing) and a tool runner (the loop). Then an agent SDK (the loop, the tools, the conversation, in your process), and a hosted runtime (all three, on the provider's servers).
2. 21.2 What three kinds of answer go in an SDK column of the mapping table? It does it (with the option), it does it differently (with the difference), or still yours.
3. 21.3 Name the four things to collect about every run. What the run was given, each model reply, each tool call and result, and how it ended and what it cost. Check which ones your SDK reports, and write the rest yourself.
4. 21.4 Why turn off every built-in tool for an AP worker? It needs none of them, and each is a way for an injected instruction to reach the computer.
5. 21.4 Who runs a tool call when your process connects to the server, and when a hosted tool is used? Your process, and the provider's service, out of your sight.
6. 21.5 Name the layers a tool call passes, in order. Code around every call, fixed rules, the general setting, the allow list, then your rule.
7. 21.5 How does an approval differ from a permission callback? A callback is asked, answers, and the run carries on at once. With an approval the run pauses and hands the call back to your code. Your code can decide now or later and then resume the run from its saved state.
8. 21.5 A hook throws an error. Does the tool still run? On the first SDK, by default yes. A hook that must block must be set to block on failure.
9. 21.6 Can a guardrail check that a citation is the right line? No. It checks the shape of the answer, not its truth.
10. 21.6 Which limit does neither SDK keep for you? The time limit.
11. 21.7 Name the places a conversation can live, from yours to theirs. In your program, a file or store on your side, a conversation on the provider's side, a chain of replies on the provider's side, or nowhere after the run.
12. 21.7 Your program restarts. With session files off, what is left of the conversation, and with the history kept in your program? With session files off, nothing. With the history in your program, only what your code saved.
13. 21.8 You point an SDK at a model on your own computer, with its tracing on by default. Where can the traces go? Still to the provider. The SDK's default trace address does not change when the model's does. Turn tracing off, or send traces through a processor you choose.
14. 21.9 Name four things an SDK in your own process still leaves to you. Any four of: the process and, for some, a disk, the sandbox, what it inherits, credentials, where transcripts and traces live, cost and time, upgrades, what counts as done.
15. 21.9 Name the five verbs of harness engineering, and one place you used each in this chapter. Constrain (the tool list, your rule, the limits), inform (instructions and tool descriptions), verify (the answer check), correct (the denial message), escalate (the approval that hands the call back).
16. 21.10 State the invariant in one sentence. An SDK may supply defaults for tools, limits, state and what counts as done, but the owner still chooses, checks and enforces the rules the business needs.