CCDV-F Claude Code Practice Test 3 — 15 Questions

Question 1

Refer to the exhibit. How does Claude Code handle this interruption, and what is the expected outcome?

Accepted Answer

The agent updates the plan and skips the 'test' directory.. Claude Code is built to handle mid-task updates to instructions. When the user provides a constraint update (like excluding a folder), the agent halts its planned execution to incorporate this new requirement into its plan. This allows for safe, interactive corrections to mass-refactoring tasks, ensuring that the developer remains in control and preventing accidental modifications to sensitive or critical parts of the codebase during large-scale operations.

Answer

The agent proceeds with the original plan to ensure consistency.

Answer

The agent crashes and requires a session restart.

Answer

The agent asks the user to manually perform the file changes.

Question 2

What role do 'project-aware' features play in Claude Code during a development session?

Accepted Answer

They enable the agent to understand existing project conventions.. Project-awareness allows Claude Code to understand the structure, language conventions, and dependency relationships within the codebase. This context is crucial for generating code that is idiomatic and structurally sound. Instead of treating files as isolated units, the agent can reason about how changes in one file impact another, leading to more accurate refactoring and fewer integration issues across the entire project repository.

Answer

They allow the agent to automatically commit changes to Git.

Answer

They force the agent to only use the most popular libraries.

Answer

They prevent the agent from accessing external online resources.

Question 3

Why is it important to use the Claude Code CLI within an initialized Git repository?

Accepted Answer

It provides a safety net for reverting changes.. Git integration is fundamental to using Claude Code effectively. It allows the agent to track changes, easily undo mistakes, and see the 'diff' of what it has modified. This safety net encourages experimentation and allows the developer to revert changes easily if the agent's output is not what they intended, creating a professional development workflow that minimizes risk during automated code modifications.

Answer

It is required for the agent to connect to the internet.

Answer

It automatically deploys the code to GitHub.

Answer

The agent refuses to work without a remote origin defined.

Question 4

Refer to the exhibit. What is the most effective way to address the agent's modification of build artifacts?

Accepted Answer

Add the build artifact paths to .claudeignore and revert changes.. The correct approach is to stop the agent, exclude the build artifacts via .claudeignore, and revert the changes to those specific files using Git. This protects the integrity of the build process and ensures the agent stays focused on source code. By teaching the agent to respect these boundaries, you optimize future task performance and prevent similar errors in subsequent automated refactoring steps.

Answer

Accept the changes and manually delete the artifacts later.

Answer

Tell the agent to be more careful next time.

Answer

Rebuild the project to overwrite the agent's changes.

Question 5

You are working in a monorepo where the repository root contains a CLAUDE.md with shared coding standards, and the packages/api directory has its own CLAUDE.md with API-specific conventions. During a session started from the repository root, Claude Code begins editing files under packages/api. Which CLAUDE.md content is applied to those edits, and how should you expect the two files to interact?

Accepted Answer

Both files contribute: the root CLAUDE.md supplies repo-wide standards while the packages/api CLAUDE.md adds directory-specific conventions that take precedence for those files.. Claude Code treats CLAUDE.md as layered project memory rather than a single global file. A repository-root CLAUDE.md carries standards that apply across the codebase, and a nested CLAUDE.md inside a package refines those rules for that subtree. For edits under packages/api, the nested conventions govern while the root standards still apply where they are not contradicted, which is why monorepos can share common guidance and still specialize per package.

Answer

Neither file is applied automatically; you must paste the relevant conventions into the prompt each time you want them honored.

Answer

Only the repository root CLAUDE.md is loaded, because Claude Code reads a single memory file at the project root and ignores nested ones.

Answer

The nested packages/api CLAUDE.md completely replaces the root CLAUDE.md for the whole session once any file in that directory is touched.

Question 6

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?

Accepted Answer

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

Manually paste the entire directory tree into the first prompt.

Answer

Run `claude --verbose` to enable detailed logging of all file accesses.

Answer

Execute `claude --reset` to clear previous session memory and start fresh.

Question 7

A developer is using Claude Code to refactor a function across multiple files. After a few edits, Claude Code proposes a change that would alter the behavior of a critical utility function used elsewhere. The developer wants to ensure the change is safe before applying it. What is the most appropriate action?

Accepted Answer

Reject the change and ask Claude Code to propose an alternative that preserves the existing behavior.. Rejecting the proposed change and asking for an alternative that preserves existing behavior is the safest approach when a critical utility function is involved. It keeps the developer in control and avoids unintended side effects. Other options either apply the risky change, discard too much work, or bypass the review process entirely.

Answer

Use the `/undo` command to revert all previous edits and start the refactor from scratch.

Answer

Accept the change and run the full test suite afterward to catch any regressions.

Answer

Manually edit the utility function to match the proposed change and then continue.

Question 8

A developer wants Claude Code to remember a project-specific convention: all new database migration files must be placed in the `db/migrations` directory and named with a `YYYYMMDDHHMMSS_` prefix. The developer wants this rule applied automatically in every future Claude Code session for this repository, without having to repeat the instruction each time. What is the most appropriate way to achieve this?

Accepted Answer

Add the convention to a CLAUDE.md file at the repository root.. Persistent, repository-scoped instructions belong in CLAUDE.md, which Claude Code reads automatically at session start. That file can be committed so every developer and every future session inherits the naming and placement rule without manual repetition. Ad-hoc pasting or non-existent config keys do not satisfy the requirement of automatic, durable application across sessions.

Answer

Run `claude config set migration.dir db/migrations` before each session.

Answer

Create a `.claudeignore` file listing `db/migrations` to protect the directory.

Answer

Paste the convention into the first message of every new session.

Question 9

A developer is working on a large refactoring task with Claude Code. They want to ensure the agent has sufficient context about the project's architecture and coding standards. Which TWO of the following are recommended ways to provide this context? (Choose two.)

Accepted Answer

During the session, explicitly reference key files like `src/core/engine.ts` and ask Claude to read them for context.. The recommended ways to provide project context are using a `CLAUDE.md` file at the root and explicitly referencing key files during the session. `CLAUDE.md` offers persistent, project-wide guidance, while on-demand file references allow the agent to focus on specific areas. Other options like `/context` command, `--add-context` flag, or relying solely on comments are not supported or effective.

Answer

Run `claude --add-context architecture.md` to load the architecture document into the session.

Answer

Include detailed comments in each source file describing the overall system design.

Answer

Use the `/context` command to manually upload a PDF of the architecture diagram.

Question 10

A developer is onboarding to an unfamiliar Python service and wants to use Claude Code to build an accurate mental model of how requests flow through the codebase before making changes. Which TWO actions best leverage Claude Code for this exploration task? (Choose two.)

Accepted Answer

Ask Claude Code to trace the request path from the HTTP route definitions through the service layer and summarize each hop.. Effective exploration with Claude Code means asking for synthesized understanding of relationships: tracing a request from route to service and describing how middleware, routing, and dependency injection connect. Those tasks exploit the agent's ability to read across files and explain architecture. Inventory-style listings, test counts, and reformatting do not reveal how requests flow and therefore fail to build the mental model.

Answer

Ask Claude Code to reformat all source files with the project's linter settings.

Answer

Ask Claude Code to list every file in the repository sorted by line count.

Answer

Ask Claude Code to run the full test suite and report only the total pass and fail counts.

Question 11

A developer wants Claude Code to add input validation to a specific function in `src/api/users.py`. Which instruction is most likely to produce a correct, targeted change?

Accepted Answer

In `src/api/users.py`, add validation to the `create_user` function that rejects requests where `email` is missing or lacks an `@` character, and return a 400 with a clear message.. Targeted instructions that specify file, function, validation rules, and expected error behavior produce minimal, verifiable edits. Claude Code performs best when the scope and acceptance criteria are explicit, because it can act confidently without guessing. Vague, unbounded, or purely documentary prompts either miss the goal or create unnecessary churn across the repository.

Answer

Check all the inputs everywhere and fix anything that looks wrong.

Answer

Make the code better.

Answer

Add a TODO comment in the users module about validation.

Question 12

A developer is working in a large monorepo and wants Claude Code to automatically run `npm run lint` and `npm run test` after every file edit it makes, without needing to ask each time. Which Claude Code feature should the developer configure to achieve this?

Accepted Answer

Configure a PostToolUse hook in `.claude/settings.json` that matches the Edit and Write tools and runs the lint and test commands.. Hooks are the deterministic automation mechanism in Claude Code. A PostToolUse hook bound to the Edit and Write tools executes a configured shell command every time those tools complete, which guarantees `npm run lint` and `npm run test` run after each change without any prompt. Documentation files, slash commands, and permission flags influence behavior or require manual action but cannot enforce automatic post-edit execution.

Answer

Add a CLAUDE.md file at the repository root that documents the lint and test commands.

Answer

Enable the `--auto-approve` flag in the project's `.claude/settings.json` so Claude Code can decide when to run the commands.

Answer

Create a custom slash command named `/lint-test` in `.claude/commands` that runs both commands.

Question 13

A developer is using Claude Code to debug a complex issue. After several exchanges, Claude Code suggests a solution that involves modifying a configuration file outside the project directory. The developer is concerned about unintended side effects. What is the most appropriate way to handle this?

Accepted Answer

Reject the suggestion and ask Claude Code to propose a solution that stays within the project directory.. Rejecting the suggestion and asking for a solution confined to the project directory is the safest approach. It avoids potential side effects on other projects or the system. Claude Code can often provide alternatives that use project-local configuration, which are easier to manage and revert.

Answer

Accept the suggestion but create a backup of the configuration file first.

Answer

Use the `/undo` command to revert the suggestion and then manually edit the configuration file.

Answer

Allow the modification because Claude Code has context about the system.

Question 14

A team wants Claude Code to run a custom script that inspects the repository for license headers before any commit. The script must run automatically each time Claude Code is about to create a commit, and the team wants the same hook to apply to every developer without manual setup. Which mechanism should they use?

Accepted Answer

Define a hook in the project's Claude Code settings that triggers on the commit event and runs the script.. Hooks defined in project-level Claude Code settings run deterministically on lifecycle events such as pre-commit and are shared through the repository, so every developer gets identical behavior automatically. Advisory notes in CLAUDE.md and per-machine aliases or cron jobs are either non-enforcing or require individual setup, and none reliably fires at the exact moment Claude Code is about to commit.

Answer

Ask each developer to add the script to their personal shell profile as an alias.

Answer

Configure a cron job on each developer machine to run the script every five minutes.

Answer

Add a note in CLAUDE.md instructing Claude Code to run the script before committing.

Question 15

A developer wants Claude Code to understand the team's API conventions, directory layout, and preferred testing framework for a specific service, and wants that guidance loaded automatically at the start of every session in that repository without typing it. What is the most appropriate way to accomplish this?

Accepted Answer

Place a CLAUDE.md file in the repository root containing the conventions, layout notes, and testing framework guidance.. CLAUDE.md is the designated project memory file. Claude Code automatically reads it at the start of a session in the repository, so conventions, layout notes, and testing framework preferences placed there are available without manual effort. Manual pasting, unsupported settings fields, and scattered code comments cannot deliver the same consistent, automatic, repository-wide context loading that the developer needs.

Answer

Add the conventions as comments in a source file that Claude Code is likely to read during the session.

Answer

Create a `.claude/settings.json` entry with a `systemPrompt` field containing the conventions.

Answer

Paste the conventions into the first message of each session before asking for changes.