CCAR-P sample question: where to configure Claude Code for a team
An original sample question by CERTain·exam, based only on Anthropic's public documentation. CERTain·exam is not affiliated with Anthropic.
Domain 7 · Developer Productivity & Operational Enablement (7% of CCAR-P in the exam guide effective until December 6, 2026; 8% from December 7, 2026). Objective covered: "Configure Claude tools and environments for teams (e.g., Claude Code)."
This is a matching item with four requirements and five locations.
The question
Norvik Software is rolling Claude Code out to 70 developers.
For each requirement, select where the platform team should configure it. Each location may be used once, more than once, or not at all.
Requirements:
- The security team requires that Claude never read credential files in any repository on any company laptop, and that no developer can switch this off.
- Everyone working in the billing repository should be able to run its test command without approval prompts, and a formatting hook should run after every edit.
- One developer wants to try a different default model in the billing repository for a week without changing anything for colleagues.
- Claude keeps putting new database migrations in the wrong folder of the billing repository; the team wants it to know the folder layout and naming convention in every session.
Locations:
- Managed settings deployed by the organization
- Shared project settings committed to the repository
- Project-local settings kept out of version control
- User settings in the developer's home directory
- The project's CLAUDE.md committed to the repository
Show the answer and explanation
Answer
| Requirement | Location |
|---|---|
| 1. Never read credential files, no opt-out | Managed settings deployed by the organization |
| 2. Team test command and formatting hook in one repository | Shared project settings committed to the repository |
| 3. One developer tries another model in one repository | Project-local settings kept out of version control |
| 4. Folder layout and naming convention in every session | The project's CLAUDE.md committed to the repository |
User settings are not used.
How to read this question
- Situation. One organization with 70 developers. Three of the four requirements concern one repository (billing).
- What is asked. For each requirement, two things decide the place: who it must apply to (everyone, one repository's team, one person) and whether it must be enforced or only known.
- Requirement by requirement.
- 1 → Managed settings. The rule must hold in every repository, and no developer can override it. Managed settings sit above all other levels, so an allow rule or a ! exception from another source cannot carve out a deny rule. A project file would cover only one repository, and anyone who commits to it could change it. CLAUDE.md is context, not enforcement.
- 2 → Shared project settings. Team permission rules and hooks for one repository belong in the committed project file, which every clone receives.
- 3 → Project-local settings. This is a personal override for one repository that stays out of commits. User settings would change the model in every project on the machine.
- 4 → Project CLAUDE.md. This is knowledge Claude cannot infer from the code (layout, naming), needed in every session and shared through version control. A permission rule or hook could block a wrong path, but it would not teach the convention.
- Rule to remember. Ask two questions: who must this apply to, and must it be enforced? Enforced for everyone: managed settings. Enforced for one repository's team: shared project settings. Just for me, here: local settings. Knowledge, not enforcement: CLAUDE.md.
Sources (Claude Code Docs, quotes checked Oct 23, 2026; page checked Oct 27, 2026)
- Settings:
- Scope table: Managed "Everyone your organization deploys it to"; Shared project "Everyone working in the folder that contains it. In a git repository, commit it so teammates get it"; Project local "You, in this one project only."; User "You, in every project on this machine".
- "Nothing in your own settings files or --settings overrides a managed key".
- "Commit .claude/settings.json so everyone who clones the repository gets the same permissions, hooks, and plugins."
- "To change a setting for yourself in one project without changing it for your teammates, save it in .claude/settings.local.json inside the project."
- Permissions:
- "Permission rules are enforced by Claude Code, not by the model. Instructions in your prompt or CLAUDE.md shape what Claude tries to do, but they don't change what Claude Code allows."
- "An allow rule can't carve an exception out of a deny rule."
- "A Read(!.env) in project settings or in --disallowedTools doesn't cancel a Read(./.env) deny from managed settings or any other settings file."
- How Claude remembers your project (memory):
- Project instructions: "Team-shared instructions for the project Project architecture, coding standards, common workflows Team members via source control".
- "Claude treats them as context, not enforced configuration. To block an action regardless of what Claude decides, use a PreToolUse hook instead."
- Best practices:
- "CLAUDE.md is a special file that Claude reads at the start of every conversation. Include Bash commands, code style, and workflow rules. This gives Claude persistent context it can't infer from code alone."
More practice
Questions
Where does this question come from?
It's an original sample question that CERTain·exam wrote based only on the public Claude Code documentation and the public exam guide.
What does CCAR-P Domain 7 cover?
According to the exam guide effective until December 6, 2026, Developer Productivity & Operational Enablement (7%) covers configuring Claude tools and environments for teams (for example Claude Code), improving developer workflows with AI-assisted tooling, and supporting debugging and operational issue resolution. From December 7, 2026, the domain weighs 8%, and its objectives are rewritten. See what changes on December 7, 2026.
First, sign in with your email.