Q18 of 60 — CCA Practice Exam

Developer Productivity with Claude

Your team uses the Claude Code SDK to run long-running developer sessions that span dozens of tool calls — reading files, running tests, and iterating on a complex refactor. Developers report that after automatic compaction triggers mid-session, Claude loses track of the acceptance criteria defined at the start of the session and begins re-introducing patterns it was explicitly told to avoid. Logs confirm the compact_boundary system message is emitting correctly, and the compaction itself is working as intended. What is the most effective fix?

A. Add a PreCompact hook that archives the full transcript before compaction occurs, then injects the archived transcript back into the next session's initial prompt.

B. Add a section to the project's CLAUDE.md specifying that the compactor should always preserve the current task objective, acceptance criteria, and any architectural decisions made during the session.

C. Move the acceptance criteria and refactoring constraints into the initial prompt of each session, making them the most prominent context for Claude at the start of each conversation.

D. Trigger manual compaction via /compact before the context window fills, so that developers can time compaction to occur at a natural break point rather than mid-refactor.