Module 05 Knowledge Check
5 questions. Pass mark 4 out of 5. Answer every question before checking the answer key below, then retry after reading the feedback.
1. A guardrail is most valuable when it…
- A. Rewrites output silently
- B. Blocks or escalates before a consequential action or external output
- C. Logs the run
- D. Formats text
2. Validating a task's output against its expected format lets you…
- A. Skip review
- B. Catch a failed step before it contaminates downstream tasks
- C. Reduce cost
- D. Improve tone
3. Human review should be placed…
- A. After publication
- B. Before anything is sent, published, or actioned externally
- C. At the start
- D. Only on errors
4. Asking a human to approve every intermediate step usually…
- A. Improves quality
- B. Causes approval fatigue, so approvals become reflexive and the control stops working
- C. Reduces cost
- D. Speeds delivery
5. Callbacks are primarily for…
- A. Changing agent behaviour
- B. Observing execution - what each agent produced, which tools ran, and where time went
- C. Storing memory
- D. Routing
---
Answer Key and Explanations
Check these only after attempting every question.
1. B - Blocks or escalates before a consequential action or external output
The control must sit where it can still prevent the outcome.
2. B - Catch a failed step before it contaminates downstream tasks
Early validation stops error propagation through the chain.
3. B - Before anything is sent, published, or actioned externally
Review after the fact is an audit, not a control.
4. B - Causes approval fatigue, so approvals become reflexive and the control stops working
Gate the consequential steps; let the rest run.
5. B - Observing execution - what each agent produced, which tools ran, and where time went
They are the instrumentation that makes a multi-agent run explainable.
Practical Check
Apply this module to your own work: complete the module activity for *Guardrails, Callbacks, and Human Review*, then write one sentence naming what your result shows and one naming what it does not.
Strong Answer Pattern
A strong answer names the task, the evidence used, the check performed, and the remaining limitation. It avoids "proved", "guaranteed", or "always" unless the evidence genuinely supports it.