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. Streaming intermediate progress matters because…
- A. It is faster
- B. Users abandon workflows that appear frozen, and progress makes state visible
- C. It reduces cost
- D. It improves accuracy
2. Streaming partial model output to users during a consequential step risks…
- A. Nothing
- B. Users treating an unreviewed draft as the final, approved result
- C. Higher latency
- D. Broken state
3. For a workflow that may run for minutes, the right pattern is…
- A. Block the request
- B. Run asynchronously with a durable run id the user can return to
- C. Retry silently
- D. Shorten the work
4. Showing which node is executing helps mainly by…
- A. Looking technical
- B. Making stalls and loops visible to both users and operators
- C. Reducing tokens
- D. Improving accuracy
5. When a long run fails midway, the best user experience is…
- A. A generic error
- B. Saying what completed, what did not, and whether anything was actually actioned
- C. Silent retry
- D. Restarting automatically
---
Answer Key and Explanations
Check these only after attempting every question.
1. B - Users abandon workflows that appear frozen, and progress makes state visible
Perceived responsiveness is a real reliability property for multi-step workflows.
2. B - Users treating an unreviewed draft as the final, approved result
Show progress, but make clear what is provisional and what has been approved.
3. B - Run asynchronously with a durable run id the user can return to
Long work should survive a closed browser tab; that requires persistence, not a held connection.
4. B - Making stalls and loops visible to both users and operators
A visible step name turns 'it's stuck' into 'it's stuck at the retrieval node'.
5. B - Saying what completed, what did not, and whether anything was actually actioned
After a partial failure the user's first question is whether a real-world action already happened.
Practical Check
Apply this module to your own work: complete the module activity for *Streaming and Long-Running Workflow UX*, 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.