CCDV-F Claude Code Practice Question
A developer is working in a large repository and wants Claude Code to understand the project structure and available tools before making changes. They run `claude` in the project root. Which action best ensures Claude Code has the necessary context for the session?
⚠ Common exam trap
The trap here is assuming that any command-line flag or manual input can substitute for the persistent, structured context that `/init` provides.
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
✓
Run `/init` to generate a CLAUDE.md file that documents the project structure and common commands.
Using `/init` generates a CLAUDE.md file that persists across sessions and captures essential project details like build commands and architecture. This is the intended mechanism for providing durable context in a new codebase. Other options either do not exist, provide only temporary input, or do not enhance Claude Code's understanding of the project.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manually paste the entire directory tree into the first prompt.
Why it's wrong here
Pasting a directory tree is a one-time input that does not persist across sessions and may exceed context limits in a large repository. It also lacks details about build commands, test runners, or coding conventions. While it provides some structure, it is inefficient and does not create a reusable knowledge base for Claude Code.
- ✗
Run `claude --verbose` to enable detailed logging of all file accesses.
Why it's wrong here
The `--verbose` flag increases logging output but does not give Claude Code any additional understanding of the project. It only affects the verbosity of the tool's own diagnostics. It does not create or load a project context file, so Claude Code would still lack the necessary information about the repository's structure and commands.
- ✗
Execute `claude --reset` to clear previous session memory and start fresh.
Why it's wrong here
The `--reset` flag is not a valid Claude Code option. Even if it existed, clearing memory would remove any existing context rather than build it. The developer needs to add project-specific information, not discard it. This approach would leave Claude Code without the structural understanding required to work effectively in the large repository.
- ✓
Run `/init` to generate a CLAUDE.md file that documents the project structure and common commands.
Why this is correct
The `/init` command analyzes the repository and creates a CLAUDE.md file that captures key project details such as build commands, test procedures, and architectural notes. This file is automatically read by Claude Code in subsequent sessions, providing persistent context. It is the recommended first step when starting work in a new or unfamiliar codebase.
About these practice questions
This CCDV-F question is part of Courseiva's 257-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 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.