CCAR-F Claude Code Configuration and Workflows Practice Question
A developer wants a single Claude Code slash command available only to their own user account on a shared Linux workstation, not to other engineers who log into the same machine. Where should the command's Markdown file be stored?
⚠ Common exam trap
The trap here is assuming that any file placed under a .claude directory behaves the same, when user-level and project-level command directories deliberately differ in visibility and version control.
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
✓
In ~/.claude/commands in the developer's home directory
Slash commands are Markdown files discovered from command directories, and scope follows location: files under the user's home .claude/commands are personal, while files under the project's .claude/commands are shared through the repository. To keep a command visible only to one developer on a multi-user workstation, it must be stored in that developer's home directory command folder rather than in any project-level location.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
In the project's .claude/commands directory at the repository root
Why it's wrong here
Placing the command in .claude/commands inside the repository makes it project-scoped, so it is version-controlled and becomes available to every collaborator who clones or pulls the repo. That directly violates the requirement to keep the command private to one user account on the shared workstation, since teammates working in the same project would also see and be able to run it.
- ✗
In a CLAUDE.md file committed at the repository root
Why it's wrong here
CLAUDE.md holds project memory and instructions that Claude Code loads as context; it is not a command-registration mechanism. Even though a committed CLAUDE.md is shared with the team, it cannot define an invocable slash command, so it neither creates the command nor restricts it to a single user account on the shared host.
- ✗
In the settings.json file under the project's .claude directory
Why it's wrong here
Settings files control configuration such as permissions, environment variables, and hooks; they do not register slash commands. Writing command content into a project settings.json would not produce an invocable command, and because the file is project-scoped and typically committed, it also fails the requirement of limiting the command to one user's account.
- ✓
In ~/.claude/commands in the developer's home directory
Why this is correct
Personal slash commands live under the user-level ~/.claude/commands folder, so they load for that OS account only and are never committed to the repository. On a shared workstation, other engineers logging in under their own accounts use their own home directories, so they cannot see or invoke this command, which satisfies the isolation requirement.
About these practice questions
This CCAR-F question is part of Courseiva's 271-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.