Put your review packet to the test
Close the worked answers and examine what you produced. A useful review lets another engineer follow your decision, challenge an assumption and test the proposed control. Use the prompts below to find the part that still needs work.
Sign in to save your reading progress. You can use these review prompts without an account. Lesson access follows the course syllabus.
Check the artifacts
Event contract
Do known fixtures preserve actor, target, action, outcome and time through normalization and rule execution?
Investigation and intelligence
Can each relationship be traced to evidence, with intelligence revision, expiry, withdrawal and sharing restrictions preserved?
Historical-search assessment
Does the conclusion retain the rule, corpus, job and handling limits?
Response and recovery
Can the workflow reconcile unknown remote effects and verify the authority state before recovery?
For each prompt, point to a decision in your own work. If you can only repeat the lesson's wording, revisit its exercise and explain what would change your answer.
TRY A CHANGED REQUIREMENT
Can the reasoning travel?
A fictional incident includes a delayed cloud event and a reused endpoint address after containment. Revise the correlation and response record without merging unrelated identities or inventing a new action.
Write the revision before checking the course examples. Name the changed boundary, a justified decision, a remaining uncertainty and a test that could disprove your conclusion. Use fictional data or work you are authorized to review.
Choose your next step
If the decision still feels uncertain, return to the project and compare your revised memo with its worked feedback. Connect public mechanisms to local controls, evidence and recovery decisions.
Share the course syllabus and its free lessons with a colleague if they are working through similar questions. Keep private review material out of anything you share.