CCARF Practice Question

Paper 3 · Question 14

D3 Claude Code Configuration & Workflows · 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. A new teammate's Claude Code sessions ignore the team's coding standards. You discover the standards live in your own ~/.claude/CLAUDE.md. What is the correct fix, and how do you verify it?

• A.Move the standards into the project-level CLAUDE.md (checked into the repository) so every clone receives them, and use the /memory command to verify which memory files a session has loaded
• B.Email the teammate your ~/.claude/CLAUDE.md to copy into their home directory
• C.Have the teammate re-install Claude Code to refresh configuration
• D.Paste the standards at the start of each session until they stick

Show answer & explanations

Correct answer: A

A: User-level configuration applies only to that user — it never travels via version control. Team standards belong at project level, and /memory is the diagnostic that shows exactly which memory files a session loaded.

B: distributes configuration by hand and drifts immediately

C: reinstalls software to fix a file-location problem

D: mistakes a persistent configuration issue for a per-session prompting task — and nothing “sticks” between sessions

Related Claude Code Configuration & Workflows questions

More: Paper 3 · All practice questions