Pass Anthropic CCA-F Exam in First Attempt Guaranteed!

Grep looks for text matches inside files, whereas the requirement is to list paths that match **/*.spec.ts regardless of their contents. Use Glob to discover the matching test filenames; Grep could miss a matching file that does not contain the searched text.

Whole-file writing is suitable when the entire file is intentionally regenerated. This alternative does not establish how to discover files by path or naming convention in the stated workflow.

Bash can enumerate paths if command execution is authorized, but it grants more capability than the file-pattern discovery task requires. Glob directly matches the requested **/*.spec.ts filenames without running a shell command or risking command side effects.

Glob resolves path patterns and extensions without searching full file contents. That addresses a different part of the system, not the requirement to make a surgical edit to known source text.

Write is suited for creating or replacing a complete file. This is not a substitute for “Use Edit for a targeted replacement after inspecting surrounding context”; that control is necessary in the stated circumstances. Confirm that the expected original value occurs at the intended location and inspect the resulting diff before accepting the change.

Whole-file writing is suitable when the entire file is intentionally regenerated. The scenario instead requires a way to make a surgical edit to known source text.

A targeted replacement cannot edit a file that has not yet been created. Edit expects an existing matched location, so attempting it against a missing README is an invalid operation. Use Write or another explicit creation procedure when the intended file does not yet exist, then verify content.

Grep searches contents efficiently. This capability does not directly create a new file rather than patching nonexistent text. Searching existing source text cannot create the missing README. Read may confirm the target does not exist, but Write is the file-creation operation under the approved path.

Glob resolves path patterns and extensions without searching full file contents. It would leave the stated need to create a new file rather than patching nonexistent text unresolved.

Glob resolves path patterns and extensions without searching full file contents. This alternative does not establish how to execute approved project test commands in the stated workflow.

Write is suited for creating or replacing a complete file. Although useful elsewhere, it is not the direct mechanism to execute approved project test commands.

Read can inspect source code, but it cannot execute npm test or produce the command’s actual exit code. A code review alone cannot establish that unit or integration tests pass. The requested evidence is a real test process result, obtained with an authorized Bash execution and reviewed standard output, standard error and exit status.

Write creates or replaces file contents; using it before inspecting one known module could overwrite code without understanding its dependencies. Read the specific file first, identify the relevant implementation and then choose a bounded edit if a change is justified.

Whole-file replacement increases the risk of deleting concurrent or unrelated material. The proposed option cannot provide the specific “Use Read on the specific module rather than grepping the entire repository” behavior that the case requires. When a specific file path has already been established and authorized, reading that file directly is more precise than running another broad repository search.

Content search reveals references regardless of filenames. That addresses a different part of the system, not the requirement to inspect a known file before editing it.

Glob handles structural filename discovery. The decisive requirement here is to find and inspect code references before refactoring. Glob finds filenames by pattern and may miss imports using other source names. A symbol-level Grep followed by Read is better for locating actual dependency references.

Glob resolves path patterns and extensions without searching full file contents. It would leave the stated need to find and inspect code references before refactoring unresolved.

When the file is already known, direct reading provides the necessary context with less search noise. This alternative does not establish how to find and inspect code references before refactoring in the stated workflow.

Running a focused test is useful after a modification, but it does not choose the safest way to change a single paragraph in an existing large file. Use a targeted Edit after reading the surrounding text; wholesale Write risks replacing unrelated sections.

When the file is already known, direct reading provides the necessary context with less search noise. Although useful elsewhere, it is not the direct mechanism to minimize change scope for a local correction.

Whole-file writing is suitable when the entire file is intentionally regenerated. The proposed option cannot provide the specific “Use a targeted Edit that preserves all unrelated content” behavior that the case requires. Rewriting an entire policy file for one small change risks removing unrelated clauses or annotations.

Glob can list workspace paths without side effects, but the research-only agent is attempting a package-install command through Bash. The primary control is to deny execution permissions for Bash, not to switch to a file-name search tool after the unsafe request.

A correct edit must be verified. This capability does not directly enforce execution permissions on built-in tools. Reading and testing may be allowed in a different coding workflow, but they do not authorize a research-only agent to install packages. Reject Bash where command execution exceeds its role.

A targeted Edit changes text precisely, but it still modifies files and is unrelated to a package install requested through Bash. Research-only capabilities should exclude or deny shell execution at the tool boundary regardless of whether another editing tool seems narrower.

Grep finds symbols inside source text; the engineer needs paths named package.json across nested directories. Glob directly matches that filename pattern. Content search would depend on arbitrary text inside those files and could omit legitimate package manifests.

Write is suited for creating or replacing a complete file. Although useful elsewhere, it is not the direct mechanism to locate files by their basenames.

Exhaustive manual reading wastes context when a filename pattern can locate manifests directly. Reading all repository files creates unnecessary cost and may expose unrelated secrets. Use Glob to discover likely paths and Grep to locate matching content, then Read the few relevant files before proposing a change.

Whole-file writing is suitable when the entire file is intentionally regenerated. Here, after changing a parser, the assistant claims success without examining the file or running tests. Read the changed region and use Bash to run the focused test suite. A correct edit must be verified.

Bash runs shell commands and returns execution output. That addresses a different part of the system, not the requirement to verify source changes with reading and executable tests.

Glob resolves path patterns and extensions without searching full file contents. The scenario instead requires a way to verify source changes with reading and executable tests.

Glob alone maps file locations but does not find the relevant function names and references for selective reading. Combine path filtering with Grep on symbols, then Read only the matched modules instead of loading the whole monorepo into context.

Edit is a precise modification operation, not an exploration strategy. The agent has not yet located the relevant code, so making edits now risks changing the wrong module. First narrow paths with Glob and locate symbols with Grep, then read the necessary context.

Write is appropriate only after the full replacement content is validated and authorized. It does not solve the early discovery problem of reading far too many files. Locate relevant paths and symbols before deciding whether any rewrite is warranted.