Q45 of 60 — CCA Practice Exam

Code Generation with Claude Code

Your team has standardized on Claude Code for a large API project, and you've written a root CLAUDE.md with rules like "always use async/await for I/O operations" and "prefer descriptive variable names." Three weeks in, developers report that Claude follows the async/await rule inconsistently — roughly 30% of generated functions still use callback patterns. Running /memory confirms the CLAUDE.md is loaded every session. What is the most likely root cause and the most effective fix?

A. CLAUDE.md is delivered as a user message, not the system prompt, so vague instructions are followed probabilistically. Rewrite the rule to be concrete and specific: "all functions performing file, network, or database I/O must use async/await — callbacks and .then() chains are forbidden."

B. The root CLAUDE.md is not the right location for code style rules; move the async/await rule into an auto memory entry so Claude treats it as a learned preference rather than an instruction, which gives it stronger enforcement weight in every session.

C. Increase the token budget for each session so Claude has more processing capacity to read and internalize the CLAUDE.md instructions before generating code, reducing the chance that style rules are skipped under context pressure.

D. Add a system prompt instruction at the start of each conversation reminding Claude to re-read the CLAUDE.md file before generating any functions, so the async/await rule is refreshed in Claude's attention window prior to each code generation task.