CCAR-F Claude Code Configuration and Workflows Practice Question
A new engineer on a team wants to see every slash command currently available in their Claude Code session, including custom commands the team has added, before starting a large refactor. Which action should they take?
⚠ Common exam trap
The trap here is assuming a shell-level flag or filesystem inspection replaces the in-session discovery command, when Claude Code centralizes command listing behind the `/help` slash command.
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
✓
Type `/help` at the prompt to display the list of available slash commands, including custom ones.
Claude Code exposes slash-command discovery through `/help`, which lists both built-in commands and any custom commands defined for the project or user. Because the engineer needs a complete, current view before starting a refactor, invoking `/help` inside the session is the direct and authoritative way to get that list.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Run `claude --list-commands` from the shell before launching the interactive session.
Why it's wrong here
The Claude Code CLI does not expose a `--list-commands` flag; command discovery happens inside the interactive session rather than through a shell argument. Relying on this would leave the engineer without the list they need, and the flag itself would be rejected as an unknown option by the CLI.
- ✗
Open the `~/.claude/commands` directory and read every Markdown file to reconstruct the command list manually.
Why it's wrong here
Custom commands are indeed stored as Markdown files, but this only reveals user-defined commands and misses all built-in slash commands. Manually reconstructing the list is error-prone and slow, and it does not reflect commands contributed by the project or any other source, so it is not a reliable discovery method.
- ✓
Type `/help` at the prompt to display the list of available slash commands, including custom ones.
Why this is correct
The `/help` slash command in Claude Code prints the built-in commands along with any custom commands the project or user has defined. It is the standard way to discover what is available in the current session, making it the right first step before a large refactor where the engineer wants to know which shortcuts exist.
- ✗
Press `Ctrl+R` to open the command history and infer the available commands from prior sessions.
Why it's wrong here
`Ctrl+R` performs reverse history search over previously entered prompts, not a catalog of available slash commands. It only shows what was typed before, which may be incomplete or stale, and it cannot reveal commands the engineer has never used, so it fails as a discovery mechanism.
About these practice questions
Courseiva writes every CCAR-F question from scratch — 271 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.