Q55 of 60 — CCA Practice Exam

Developer Productivity with Claude

A developer on your team is working on a large monorepo with Claude Code. They've structured path-scoped rules in .claude/rules/ with paths: frontmatter to enforce service-specific coding standards. After several hours of editing files across the codebase, the session auto-compacts. The developer then returns to the payments service directory and makes edits — but Claude ignores the payments-specific formatting rules it was following earlier. Examining the setup, you find the rules are loaded only via paths: frontmatter. What is the most likely explanation for this behavior, and what is the correct architectural fix?

A. Auto-compaction summarizes path-scoped rules along with message history; they only reload when Claude next reads a matching file. To guarantee persistence across compaction, move critical rules to project-root CLAUDE.md or remove the paths: frontmatter entirely.

B. Auto-compaction clears all CLAUDE.md files including the project-root one; the correct fix is to increase the session's token budget so compaction is triggered less frequently, preserving the path-scoped rules in context for longer.

C. Path-scoped rules are dropped permanently once compaction runs and cannot reload automatically; the fix is for the developer to manually re-specify the relevant rules in each new prompt to restore them for that session.

D. Auto-compaction retains path-scoped rules in the system prompt but strips their frontmatter metadata; the fix is to migrate the rules into the auto memory file so they are re-injected from disk independently of any path trigger.