Anthropic CCAR-F - Claude Certified Architect – Foundations

Option A corrects the missing tool contract that permits Claude to guess a required parameter. The process_refund description should state its prerequisite explicitly: invoke lookup_order, use only the exact order_id returned by that successful call, and ask for additional identifying information when lookup cannot resolve an order. An input example can demonstrate the correct two-tool sequence.

Anthropic’s tool-definition guidance identifies detailed descriptions as the most important factor in tool performance. Descriptions should explain when a tool should and should not be used, what every parameter means, and all important limitations. The tool-use overview confirms that Claude selects and populates tools based on the request and their descriptions.

Option B forces some tool call but does not tell Claude which tool must run first or where the identifier originates. Option C is an essential defence-in-depth control, but it detects the fabricated value after Claude has already made the incorrect decision. Option D works only when the customer supplies an identifier and does not cover “recent purchase.” Explicit prerequisite and provenance instructions directly prevent the model from inventing the required argument.

Option A uses the limited review capacity as a risk-ranking mechanism rather than spending it uniformly. JSON Schema validation can prove that an output has the expected types and structure, but it cannot detect a semantically misplaced value such as a duration stored as an ingredient quantity. Field-level confidence can identify the exact parts of a record that warrant inspection, provided those scores are calibrated against labeled examples rather than trusted at face value. The labeled validation set must mirror the production distribution and include edge cases; Anthropic’s evaluation guidance explicitly recommends task-specific evaluations, representative distributions, measurable criteria, and automated grading where possible. Calibration then converts raw confidence into an empirically tested estimate of error risk, allowing reviewers to inspect the lowest-confidence records or fields first. Option C, random sampling, is useful for unbiased quality measurement and discovering new failure modes, but it does not maximize error detection within a fixed 20 percent review budget. Options B and D target narrow proxies—layout anomalies and missing required values—while the observed errors pass structural validation and may occur in ordinary-looking documents. The operational design should combine calibrated risk-based review with a smaller random audit sample to detect drift and overconfidence.

================

Option A uses the dedicated control surface for managed Claude Code Review. Anthropic’s Code Review documentation states that a root-level REVIEW.md is injected into every review agent as the highest-priority instruction block. It can define skip paths, suppress categories already enforced by CI, recalibrate severity, cap nit volume, and require source evidence before reporting particular findings. The documentation explicitly identifies generated code, linting, and verification requirements as appropriate uses.

Option B configures a self-hosted GitHub Actions workflow, but the scenario concerns the separate managed Code Review service running on Anthropic’s infrastructure. Instructions in that workflow do not control the managed reviewer. Option C provides useful general project context, but CLAUDE.md has lower review-specific authority: managed Code Review treats violations of it primarily as nit-level findings. REVIEW.md is the stronger and more precise mechanism for changing what the managed service reports. The file should skip src/gen/**, suppress style issues already enforced by CI, and require concrete behavioral evidence for rendering-helper warnings while continuing to report verified correctness and security defects.

================

The --system-prompt flag replaces Claude Code’s complete default system prompt. Although this does not technically remove the available tools, it discards the default coding-agent guidance that tells Claude how to gather repository context, navigate code, use tools, and verify findings. The replacement prompt says only to analyze the supplied diff, so the observed diff-only behaviour is consistent with the configured instructions.

Option B preserves the standard Claude Code identity and tool guidance while adding the custom review criteria. The Claude Code CLI reference states that --append-system-prompt appends instructions to the default prompt, whereas --system-prompt replaces it. Anthropic specifically recommends appending when Claude should remain a coding assistant that follows additional per-invocation rules.

Option A is incorrect because print mode does not inherently disable Read, Glob, or Grep; --allowedTools restricts or pre-authorizes tools but does not restore overwritten behavioural guidance. Option C is incorrect because replacement system prompts remain compatible with tools, although the replacement must supply suitable tool instructions. Option D changes where the diff appears but does not restore Claude Code’s default code-navigation behaviour. Appending the review instructions directly addresses the configuration error.

================

Option A establishes the caching architecture before consuming thousands of implementation lines. The base class or protocol reveals the supported operations, lifecycle, cache-key rules, and invalidation contract. Imports, subclasses, registrations, and call sites can then direct the agent toward only those concrete implementations relevant to the proposed trigger. Anthropic’s effective context-engineering guidance explains that context is finite and that recall degrades as irrelevant tokens accumulate. It identifies Glob and Grep as mechanisms for retrieving code just in time rather than loading an entire repository upfront. Option B assumes file size or naming determines architectural importance; a small interface may define the system while a large service file contains incidental caching calls. Option C loads approximately 8,000 lines before establishing which portions matter. Option D is overly lexical and can miss invalidation implemented through event publication, key-version changes, inherited methods, or generically named hooks. Dependency-guided exploration provides a compact conceptual model first and expands the investigation only when concrete relationships show that additional files are relevant.

================