Anthropic CCAR-F Practice Exam Questions & Answers

Option B removes the identified startup work while deliberately restoring the one source of project context the reviews require. Anthropic documents that --bare skips automatic discovery of hooks, skills, plugins, MCP servers, auto memory, and CLAUDE.md files. It is specifically intended for CI and scripted execution where fast, reproducible startup behavior is more important than loading every locally configured extension.

Because bare mode also skips the root CLAUDE.md, the pipeline must supply that content explicitly. --append-system-prompt-file ./CLAUDE.md loads the standards while retaining Claude Code's default coding-agent behavior and tool guidance. Option A replaces the default system prompt but does not, by itself, establish the same minimal startup path as --bare; replacement also discards valuable default coding instructions. Option C can work technically but duplicates repository policy inside every pipeline invocation and creates configuration drift. Option D improves prompt-cache reuse by relocating machine-specific prompt sections, but it does not eliminate discovery of hooks, MCP servers, plugins, skills, and nested instructions. Bare mode plus an explicitly appended standards file directly addresses both performance and policy requirements. Claude Code bare-mode documentation

Option C gives the human agent the operational state required to continue without replaying a long conversation. The handoff should include verified identifiers, the duplicate transaction evidence, the diagnosed timeout-and-retry mechanism, the $847 refund requirement, the agent's $500 authorization constraint, completed verification steps, prior actions, and the recommended resolution. Any unresolved uncertainty should be labeled explicitly.

Anthropic's effective context-engineering guidance recommends preserving high-value state in structured notes while removing redundant conversational and tool-call history. Its long-running-agent guidance likewise describes structured handoffs as the mechanism for maintaining continuity across context resets or agent boundaries.

Option A maximizes raw information but forces the human to locate the relevant facts among more than 25 turns, increasing delay and error risk. Option B preserves evidence but omits the authorization constraint, completed verification, and explicit recommended action. Option D is too sparse to support validation or execution. A structured handoff balances fidelity and efficiency: it contains everything needed for the next actor to make the refund decision while excluding greetings, repeated explanations, and irrelevant intermediate tool output.

This change is narrow, localized, and already defined: add one conditional validation check to an existing function in a single file. A separate planning phase would introduce process overhead without resolving meaningful architectural uncertainty. Direct execution allows Claude to read the function, implement the condition, and run the relevant focused tests.

Anthropic explicitly states that plan mode adds overhead and should generally be skipped when the scope is clear and the fix is small. Planning is most valuable when the approach is uncertain, multiple files are affected, or the code is unfamiliar. Anthropic's practical rule is that when the required diff can be described in one sentence, direct implementation is appropriate. (https://code.claude.com/docs/en/best-practices)

Option B allocates unnecessary reasoning effort to straightforward validation logic. Options C and D exaggerate the complexity of a single-function change. Broader impact analysis would be justified only if the requirement altered reservation semantics, time-zone rules, persistence behavior, or public interfaces---none of which is stated.

The implementation should still include verification. Claude should add or update tests for a future date, the current date, and a past date, then run the narrowest relevant test command. Direct execution does not mean unverified execution.

Official references/topics: Direct Execution; Plan-Mode Selection; Small Scoped Changes; Focused Verification.

Option B removes the ambiguity from the tool interface itself. The agent no longer needs to choose between separate functions that represent closely related business operations. Instead, a single compensation tool exposes an explicit action parameter, while the existing order lookup tool can optionally return delivery-tracking information through a clearly defined flag.

Anthropic's tool-design guidance recommends consolidating related operations into fewer, more capable tools when separate functions create unnecessary semantic overlap. Claude selects tools primarily from their names, descriptions, schemas, and the current task. When multiple tools appear capable of satisfying the same request, selection accuracy declines because the agent must infer distinctions that should have been made explicit in the interface design.

Option A adds routing complexity but leaves overlapping financial operations available within the same sub-agent. Option C reduces the number of tools loaded initially, but it does not eliminate the semantic duplication between compensation operations or overlapping lookup functions. Option D may improve behavior through examples, but it compensates for a poorly designed tool surface rather than correcting the root cause.

The consolidated schemas should use enums for supported actions, clearly define when each action applies, and document the returned fields. This creates a smaller and more deterministic agent-computer interface.

Official references/topics: Tool consolidation, semantic tool boundaries, action parameters, MCP tool-selection accuracy.

Option C creates an objective verification loop. The tests encode expected traversal behavior for disconnected graphs, cycle handling, weighted edges, invalid inputs, and performance constraints. Claude can implement the algorithm, execute the suite, inspect concrete failures, and refine the implementation until the measurable conditions pass.

Anthropic emphasizes giving Claude a verification mechanism such as tests, builds, linters, or fixture comparisons. Without an executable pass-or-fail check, Claude can only determine that an implementation appears complete. With tests, it can perform work, evaluate the result, and iterate using evidence rather than subjective judgment. Anthropic also recommends reproducing defects with failing tests before applying corrections. (https://code.claude.com/docs/en/best-practices)

Option A may produce a thoughtful initial design but does not guarantee progressive improvement after implementation. Option B risks inheriting assumptions or deficiencies from a reference that may not match the project's constraints. Option D depends on manual review and converts the developer into the primary verification system.

The test suite should include correctness fixtures, boundary cases, complexity-sensitive workloads, and regression tests added whenever a new failure is discovered. This makes every iteration cumulative: a correction must satisfy the new case without breaking previously validated behavior.

Official references/topics: Executable Verification; Test-Driven Iteration; Feedback Loops; Regression Testing.