CCDV-F Claude Code Practice Question
A developer repeatedly types the same multi-step instruction to Claude Code: review the current diff, run the unit tests, and summarize any failures. They want to trigger this workflow with a single short command in future sessions. What should they create?
⚠ Common exam trap
The trap here is assuming CLAUDE.md can be invoked like a command, when it only supplies passive context and cannot be triggered on demand as a reusable workflow.
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 stored as a markdown file in the project's `.claude/commands` directory.
Custom slash commands are markdown files placed in `.claude/commands` that become invocable by name. Storing the review-test-summarize instruction in such a file lets the developer trigger the entire workflow with one short command in any session in that project. Memory files provide passive context, shell aliases live outside Claude Code, and no settings shortcut field exists for this purpose.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A custom slash command stored as a markdown file in the project's `.claude/commands` directory.
Why this is correct
Custom slash commands are defined as markdown files under `.claude/commands` and are invoked by typing a short slash command. The file can contain the full multi-step instruction, so the developer triggers the whole workflow with one command. This is the documented way to package repeatable prompts for reuse across sessions in a project.
- ✗
A new entry in CLAUDE.md that lists the three steps.
Why it's wrong here
CLAUDE.md is project memory that provides background context, not a named, invocable action. Adding the steps there would make the guidance always present but would not give the developer a single short command to trigger the workflow on demand. It also risks cluttering memory with procedural instructions that are only sometimes relevant.
- ✗
A `.claude/settings.json` field named `shortcuts` mapping a key to the instruction text.
Why it's wrong here
There is no `shortcuts` field in Claude Code settings for mapping keys to prompt text. Settings control permissions, hooks, and environment variables. Inventing such a field would not work and would not create an invocable workflow. The supported feature for reusable, named prompts is custom slash commands, not a settings-based shortcut map.
- ✗
A shell alias in the developer's `.bashrc` that pipes the instruction into a Claude Code process.
Why it's wrong here
A shell alias is external to Claude Code and does not integrate with its session model, tool permissions, or project context in the intended way. It would be fragile, hard to share with teammates, and not the supported mechanism for reusable prompts. The scenario asks for a single command inside Claude Code's workflow, which native slash commands provide.
About these practice questions
One of 257 original CCDV-F practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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 CCDV-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 CCDV-F exam.