CCARF Practice Question

Paper 1 · Question 59

D2 Tool Design & MCP Integration · Paper 1

An engineering team needs to update all references to a renamed API endpoint across their 500,000-line codebase. They know the old endpoint name (POST /api/v1/users/create) but not which files reference it. After locating the files, they need to replace the old endpoint with the new one (POST /api/v2/users). What is the correct tool sequence?

• A.Use Glob for '**/*.md' to find all documentation files, then Read each one to check for the old endpoint, then use Edit to update matches.
• B.Use Read on the API router file to find all endpoint definitions, then manually trace each reference.
• C.Grep for '/api/v1/users/create' to find every file with the old endpoint, then use Edit to replace it in each match.
• D.Use Bash with sed to perform a global find-and-replace across all files in a single command.

Show answer & explanations

Correct answer: C

A: Glob finds files by path pattern, but the endpoint reference could appear in any file type, not just Markdown. Reading every documentation file to search for the string wastes context tokens on irrelevant files.

B: This approach only finds where the endpoint is defined, not where it is referenced. It also requires knowing which file contains the router definition, and manual tracing is unreliable across a large codebase.

C: Grep searches file contents across the entire codebase, locating all references regardless of file type or location. Edit then makes targeted replacements in each matched file. This is the minimal, precise approach.

D: A global sed command bypasses the built-in tools designed for this task and risks unintended modifications without the ability to review each change. Edit provides targeted modifications with unique text matching for safety.

Related Tool Design & MCP Integration questions

More: Paper 1 · All practice questions