CCAR-F Claude Code Configuration and Workflows Practice Question
A developer frequently runs the same multi-step task in Claude Code: lint the changed files, run the unit tests, and then draft a commit message. They want to invoke this entire sequence with a single reusable command rather than retyping the instructions each time. Which Claude Code feature should they configure?
⚠ Common exam trap
The trap here is treating any reusable automation (Git alias, shell script) as equivalent to a Claude Code slash command, when only the latter feeds instructions to the model.
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
✓
A custom slash command defined as a Markdown file in .claude/commands/
Custom slash commands are the documented Claude Code mechanism for packaging a reusable prompt as a Markdown file under .claude/commands/. Invoking the command sends the file's contents as the prompt, so a single command can drive linting, testing, and commit message drafting. Git aliases, shell scripts, and permission entries operate outside the model and cannot orchestrate that workflow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
An entry in the permissions.allow array of settings.json
Why it's wrong here
The permissions allowlist only pre-approves tool invocations to reduce prompts; it does not define or trigger a sequence of instructions. Adding commands here would not create a reusable workflow command, so it fails to address the developer's need.
- ✓
A custom slash command defined as a Markdown file in .claude/commands/
Why this is correct
Custom slash commands are Markdown files stored in .claude/commands/ (project) or ~/.claude/commands/ (personal) whose body becomes the prompt sent to Claude. Naming the file, for example lint-test-commit.md, creates a /lint-test-commit command, giving the developer a single reusable invocation for the whole workflow.
- ✗
A Git alias in .git/config
Why it's wrong here
Git aliases only map Git subcommands to other Git invocations; they run inside Git and never reach Claude Code. They cannot instruct Claude to lint files, run tests, and draft a commit message, so this feature does not satisfy the requirement.
- ✗
A shell script added to the PATH
Why it's wrong here
A shell script on the PATH is executed by the operating system, not by Claude Code, and it has no access to the model's reasoning about changed files. It also would not draft a commit message using Claude, so it does not deliver the intended combined workflow.
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.