Q34 of 60 — CCA Practice Exam

Code Generation with Claude Code

Your team is using Claude Code to automate a large-scale test remediation effort: fixing 200 failing tests across a legacy codebase in a multi-session workflow. After three sessions, developers report that Claude is losing track of which tests it already fixed, occasionally re-investigating tests it resolved in a prior session and leaving genuinely new failures unaddressed. Logs show that between sessions, Claude has access only to a single progress.txt file containing a freeform narrative summary of work done. What change to the state management approach would most directly fix this problem?

A. Add more detail to the freeform progress.txt narrative, including the names of every test fixed, so Claude can scan the file to determine what has been resolved across sessions.

B. Introduce a structured JSON file (e.g., tests.json) tracking each test's id, name, and status alongside the existing freeform notes, applying each format to what it does best.

C. Instruct Claude at the start of each session to re-run the full test suite and derive current status from scratch, discarding prior session notes entirely to avoid stale information.

D. Switch to a single longer session so Claude never loses context between handoffs, removing the need for any cross-session state tracking mechanism in the workflow.