CCARF Practice Question

Paper 3 · Question 19

D5 Context Management & Reliability · Paper 3

[Scenario 2: Code Generation with Claude Code] Your team uses Claude Code for code generation, refactoring, debugging, and documentation, integrated into daily development with custom slash commands and CLAUDE.md configuration — and you must judge when plan mode beats direct execution. Mid-way through an extended exploration session, context is filling with verbose discovery output and responses are noticeably degrading, but you are not ready to end the session. Which built-in command helps immediately?

• A./memory, which clears the conversation
• B./fork, which splits the session in half
• C./compact, which reduces context usage by compacting the conversation so the session can continue productively
• D./rules, which reloads the rule files

Show answer & explanations

Correct answer: C

A: shows which memory files are loaded — diagnostic, not cleanup

B: is not the mechanism (forking is for divergent branches, not compression)

C: /compact is the in-session relief valve for exactly this situation: it compacts accumulated context — typically bloated with verbose discovery output — so an extended session can continue without degradation.

D: does not address conversation bloat

Related Context Management & Reliability questions

More: Paper 3 · All practice questions