Claude Certified Architect – Foundations Practice Question 5: Settings Shared vs Local
Claude Certified Architect, Foundations · Test 1 · question 5 of 10
A team wants every developer on a repository to share the same Claude Code permission rules and hooks, while allowing each developer to add personal overrides, such as an extra allowed command, without affecting teammates or showing up in git. Which setup meets this?
Show answer and explanation
Answer:
A is correct. Project settings in .claude/settings.json are meant to be committed so teammates share permissions, hooks, and plugins. .claude/settings.local.json holds personal, per-project overrides; Claude Code keeps it out of git when it creates the file (if you create it by hand, add it to .gitignore).
B is wrong because user-level settings live outside the repository and cannot be distributed through version control. C is wrong because settings.local.json is the personal, uncommitted file, so committing it defeats its purpose and leaks one developer's overrides to everyone. D is wrong because CLAUDE.md is instruction context for the model, not an enforced permission mechanism; permissions and hooks belong in settings files.
Reference: Claude Code settings