CCDV-F Claude Code Practice Question

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 changes and manually delete the artifacts later.

  Why it's wrong here

  Accepting incorrect changes is poor practice. Modifying build artifacts can lead to inconsistent build states and potentially corrupt the project's output. It is better to address the issue immediately by reverting the changes and ensuring the agent is properly restricted to avoid future occurrences.

• ✓

  Add the build artifact paths to .claudeignore and revert changes.

  Why this is correct

  Updating the .claudeignore file is the standard configuration fix for this issue. It prevents the agent from seeing or touching these files in future tasks. Reverting the changes via Git ensures the repository returns to a clean state, correcting the mistake effectively and efficiently.

• ✗

  Tell the agent to be more careful next time.

  Why it's wrong here

  Simply telling the agent to 'be more careful' is insufficient because it doesn't solve the underlying path-awareness issue. The agent needs explicit boundaries, such as those provided by .claudeignore, to ensure it doesn't repeat the mistake, as natural language feedback alone is not a persistent configuration.

• ✗

  Rebuild the project to overwrite the agent's changes.

  Why it's wrong here

  Rebuilding does not fix the underlying issue of the agent modifying files it shouldn't. It may just mask the problem temporarily. The correct approach is to prevent the modification from happening in the first place through proper file scoping and repository management.