Last reviewed
Correct answer: D. Checkpoints are for quick recovery in a session, not permanent history
Explanation
The principle — recovery and history are different requirements, and only one of them survives the week.
Why the key is correct — Anthropic frames checkpoints as designed for quick, session-level recovery, and says that for permanent version history and collaboration you should continue using version control. They are also separate from git, so nothing your teammate does inside a session reaches the repository at all. That is the flaw: a colleague reviewing the branch, a build running in CI, or the same person next month all read git, and none of them can see a checkpoint.
Why the others are wrong — resuming does keep checkpoints reachable, but reachability was never the gap; purpose was. They do not live in git, so there is no duplication to eliminate. And they are not written only at the end of a session — a checkpoint is created at every prompt, which means mid-session coverage is the part that already works.
Remember this — rewind is for the last ten minutes; a commit is for everyone else.
Sources — Anthropic's checkpointing page and How Claude Code works.
Sources
“Checkpoints are designed for quick, session-level recovery.”
“Checkpoints are separate from git and remain available when you resume a conversation.”
Practise 10 questions on this topic
Take Claude Code Basics — Timed Test 2 (10 questions) — scored instantly, explanation for every question, no login.