Skip to content

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

  1. Connection and authority map

    Can a reviewer trace each connection and identify which service authenticates the caller, decrypts the request and decides access?

  2. Parser and platform review

    Have you named the parser's credentials and resource limits, then separated the platform evidence you observed from the properties it cannot establish?

  3. Incident and credential plan

    Does each hypothesis name evidence that could distinguish it? Does the credential rehearsal cover existing sessions, queued work and recovery checks?

  4. Prioritized service memo

    Can another engineer take the first correction, find its owner and run both an allowed case and a denied case?

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?

Use a fictional document service that adds an external OCR provider. Revise your data-flow map, permitted recipients and credential plan. Identify one new assumption, the evidence needed to check it, and the finding that would keep the feature switched off.

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. Explain the mechanism and its limits when the service assumptions change.

NEXT COURSE

Secure an LLM feature →

Apply those boundaries to retrieved documents, generated replies and tool effects.

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.