CCDV-F Claude Code Practice Question
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?
⚠ Common exam trap
The trap here is assuming that Claude Code's context includes system-wide implications, when its knowledge is typically limited to the project and provided context.
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
✓
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 analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Accept the suggestion but create a backup of the configuration file first.
Why it's wrong here
Creating a backup is prudent, but it does not address the fundamental risk of modifying a shared configuration file. Other processes or projects may depend on the current settings, and a backup does not prevent immediate breakage. The developer should first explore project-local alternatives before resorting to external changes.
- ✗
Use the `/undo` command to revert the suggestion and then manually edit the configuration file.
Why it's wrong here
There is no `/undo` command to revert a suggestion before it is applied; `/undo` reverts applied edits. Manually editing the configuration file still carries the same risks as allowing Claude Code to do it. The core issue is whether to modify an external file at all, not who performs the edit.
- ✗
Allow the modification because Claude Code has context about the system.
Why it's wrong here
Claude Code's context is limited to the project and any files it has been given access to. Modifying a configuration file outside the project directory can affect other projects or system stability. The developer should not assume Claude Code has full system context. It is safer to review and potentially reject the suggestion.
- ✓
Reject the suggestion and ask Claude Code to propose a solution that stays within the project directory.
Why this is correct
Rejecting the suggestion and requesting an alternative that confines changes to the project directory minimizes the risk of unintended side effects. This approach keeps the solution contained and reversible. Claude Code can often find alternative approaches that do not require modifying external files, such as using project-local configuration.
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.