CCAR-F Claude Code Configuration and Workflows Practice Question
An engineering team wants to customize Claude Code behavior across their enterprise repository by enforcing specific project-level guidelines and system prompts. Where should the lead architect place these configuration directives so that Claude Code automatically detects and applies them upon initialization in the workspace root?
⚠ Common exam trap
Many test-takers mistakenly believe that custom enterprise settings must be injected via external API configuration payloads rather than repository files.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Inside a CLAUDE.md file located directly in the repository root directory
Placing configuration guidelines in the CLAUDE.md file within the workspace root allows Claude Code to automatically load custom project instructions, codebase conventions, and behavioral constraints during startup. This mechanism ensures consistent AI assistance tailored precisely to the specific engineering practices and architectural patterns utilized across the development team's codebase.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Inside a .claude/config.json file in the user home directory
Why it's wrong here
Home directory configuration files manage global user preferences and API credentials rather than specific project-level codebase instructions, architectural conventions, and workspace guidelines that need to be shared collaboratively among multiple developers working within the repository.
- ✗
Within the package.json file under a dedicated claudeConfig key
Why it's wrong here
Claude Code reads CLAUDE.md files for project instructions and system prompts, not package.json keys; npm ignores unknown fields, so nothing is auto-detected at initialisation. A claudeConfig key would suit npm script or dependency metadata, where package.json legitimately governs Node tooling rather than agent behaviour.
- ✓
Inside a CLAUDE.md file located directly in the repository root directory
Why this is correct
CLAUDE.md in the repository root is automatically read and injected as project context when Claude Code initialises in that workspace, so guidelines and system prompts apply without manual invocation. This satisfies the requirement for automatic detection at the workspace root.
- ✗
As environment variables defined inside a local .env file
Why it's wrong here
Environment variables in a .env file supply runtime values such as API keys or model selection, but cannot carry structured system prompts and guidelines that Claude Code parses from CLAUDE.md at initialisation. A .env file is the right choice for secrets and per-machine settings, not repository-wide behavioural directives.
About these practice questions
Courseiva writes every CCAR-F question from scratch — 271 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Anthropic exam blueprint
This CCAR-F practice question is part of Courseiva's free Anthropic certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCAR-F exam.