Claude Certified Architect – Foundations Practice Question 32: SDK Session Resume Fork
Claude Certified Architect, Foundations · Test 4 · question 2 of 10
An engineering assistant built on the Claude Agent SDK analyzed a large repository in one session and proposed a refactor. The user now wants to try a radically different approach (for example, a different database library) while keeping the original conversation and its conclusions intact so they can return to it later. What should the application do?
Show answer and explanation
Answer:
Forking creates a new session ID that begins with a copy of the original session's history. The original session stays unchanged, so the user can explore the alternative and still return to the first line of work.
B is wrong because resuming continues the same session: the new turns are appended to it, so the alternative exploration would mix into the original history. C works but loses the full tool results and reasoning the agent already built up, and it is more work and less faithful than forking. D is not a supported workflow; deleting the stored session loses the history you wanted to preserve.
Reference: Work with sessions - Agent SDK