Keep related records consistent
Follow issues, comments, and owned edits across persistence boundaries. Preserve identity, authorship, and parent relationships after both successful and failed requests.
What you will practice
- Distinguish an entity’s author from its parent’s author.
- Keep identity sequences and saved relationships correct after failures.
- Verify updates through a later read instead of the write response alone.
Continue the guided path with Pro
Get this lesson, its focused drills and review guidance, plus explanations, replay, and unlimited native grading. AI usage has a separate allowance.
Sources and scope
Sources establish reported task overlap, not each module’s exact API, starter, tests, or extensions. Those are independently authored nrml practice. Linked report dates appear in the source labels; reviewed dates refer to the recorded source review. Historical reports and secondary summaries are identified explicitly. Completion records practice and review, not hiring readiness.
- Amazon Jira-like comment-repair report · July 21, 2026Reviewed 2026-10-14