Module 15 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. The capstone should begin with…
- A. the directory structure
- B. the contract, including errors and guarantees
- C. the model choice
- D. the deployment target
2. The import rules should be…
- A. implied by the structure
- B. written down alongside it
- C. enforced by convention
- D. left to review
3. In a well-structured service, the number of tests needing a network is…
- A. most of them
- B. a small minority
- C. all of them
- D. zero
4. Every bound - input size, budget, timeout, rate limit - should be…
- A. documented
- B. enforced in code
- C. checked in review
- D. configured in the gateway only
5. The most useful entry in a handover's untested list is…
- A. something unrelated to the design
- B. the consequence of a limit you already listed
- C. a future feature
- D. a performance target
---
Answer Key and Explanations
Check these only after attempting every question.
1. B - the contract, including errors and guarantees
Each guarantee becomes a test and constrains what you may build later.
2. B - written down alongside it
The structure is obvious; the constraints are what preserve it.
3. B - a small minority
Only the live model call is genuinely an integration test.
4. B - enforced in code
A documented intention is not a control.
5. B - the consequence of a limit you already listed
It tells the next person exactly where to look first.
Practical Check
Apply this module to your own work: complete the module activity for *Capstone: Tested, AI-Ready FastAPI Backend*, 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.