Module 08 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 workflow is a good automation candidate when…
- A. It is interesting
- B. It is repetitive, has a checkable output, and tolerates review before action
- C. It is complex
- D. It is rare
2. A poor first automation candidate is one where…
- A. Volume is high
- B. A wrong output causes immediate irreversible harm with no review point
- C. The output is text
- D. Tools are needed
3. For a customer-facing draft, the safest design is…
- A. Send automatically
- B. Draft, then require human approval before sending
- C. Send and correct later
- D. Skip drafting
4. Measuring automation success should include…
- A. Runs completed
- B. How often the output was accepted without correction
- C. Tokens used
- D. Agents involved
5. Automating a broken manual process usually…
- A. Fixes it
- B. Produces broken results faster and at larger scale
- C. Reduces cost
- D. Improves quality
---
Answer Key and Explanations
Check these only after attempting every question.
1. B - It is repetitive, has a checkable output, and tolerates review before action
Repetition justifies the build; checkability makes it safe; review makes it deployable.
2. B - A wrong output causes immediate irreversible harm with no review point
Start where errors are recoverable; earn the right to higher-stakes automation.
3. B - Draft, then require human approval before sending
Outbound communication is irreversible and reputationally consequential.
4. B - How often the output was accepted without correction
Completion is not value. Acceptance rate is the honest measure.
5. B - Produces broken results faster and at larger scale
Clarify the process first; automation amplifies whatever it is given.
Practical Check
Apply this module to your own work: complete the module activity for *Business Workflow Examples*, 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.