Free Anthropic CCAR-F Practice Exam with Questions & Answers

Option B demonstrates the decision boundary Claude must learn. Carefully selected examples can show structurally similar code producing different outcomes based on project context—for example, an approved authentication wrapper versus an unsafe direct call, or a deliberate performance trade-off versus an accidental quadratic operation. These contrasts help Claude apply the underlying judgment to new code rather than merely memorizing prohibited phrases.

Anthropic identifies relevant, diverse, and clearly structured examples as one of the most reliable methods for improving output accuracy and consistency. It recommends several examples that mirror the real use case and cover important edge conditions. Option A risks creating an oversized negative catalogue that consumes context, becomes difficult to maintain, and cannot anticipate every future variation. Option C filters text after generation and may suppress genuine findings that happen to use the selected keywords. Option D is dangerously vague: telling a reviewer to be conservative can suppress real but uncertain defects and reduce recall. The prompt should provide paired acceptable/problematic examples, explain why each classification differs, and require concrete code evidence for every reported finding. Anthropic prompting best practices

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

The key difference is reviewer independence. In the original session, Claude retains the reasoning, assumptions, implementation decisions, and intermediate conclusions that led to the refactor. That context can anchor the subsequent review toward defending or confirming the chosen approach instead of evaluating the resulting code independently. The separate CI review begins with fresh context and can assess the implementation solely against the code and review criteria.

Anthropic’s Claude Code best-practices documentation explicitly states that fresh context improves code review because Claude is not biased toward code it has just written. It recommends a writer/reviewer pattern using separate sessions or a review subagent with an isolated context.

Option B is possible in an uncontrolled comparison, but the scenario’s defining distinction is that one review occurs in the implementation session and the other is independent. Option C is false because local Claude Code can read and search the repository when permissions and tools permit it; it is not inherently restricted to the current file. Option D would require evidence of context saturation, such as degraded instruction following or an almost-full context window. No such evidence is supplied. Prior-reasoning bias most directly explains the observed discrepancy.

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

Option B eliminates an unnecessary agent boundary. The coordinator already possesses the accumulated findings and can answer a straightforward follow-up without serializing more than 80,000 tokens into a fresh subagent context, waiting for another model execution, and receiving the result back. Anthropic’s multi-agent research engineering guidance emphasizes scaling effort to task complexity: simple fact-finding or lightweight processing should use substantially fewer agents and tool calls than complex research. It also reports that multi-agent systems consume far more tokens than ordinary interactions, making avoidable delegation expensive and slow. Option A adds an interactive retrieval protocol between agents and additional round trips. Option C spends compute proactively on summaries that users may never request and creates cache-invalidation problems whenever findings change. Option D could reduce repeated input cost where caching is applicable, but the subagent still receives and processes an unnecessarily large context and still incurs spawning latency. Delegation is valuable when an isolated context or specialized capability materially improves the result. For a direct summary already supported by the coordinator’s active context, local handling is the faster and simpler architecture.

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

Option D directly addresses cache entries expiring before later batch requests are processed. Anthropic’s batch-processing documentation specifically notes that Message Batches can take longer than five minutes and recommends the one-hour prompt-cache duration for batches containing shared context. The prompt-caching documentation confirms that the default TTL is five minutes and that " ttl " : " 1h " creates an extended entry.

Option A may improve cache locality, but it introduces the sequential-processing latency explicitly prohibited by the requirement. Option B seeds the cache initially, but the prewarmed entry still expires after five minutes unless the TTL is extended; it therefore does not solve misses among requests scheduled later. Option C places the breakpoint on request-specific content, defeating reuse of the stable 8,000-token prefix and attempting to cache scripts that are not byte-for-byte identical.

The system should retain the breakpoint at the end of the shared system content and apply the one-hour TTL there. Cache-usage fields should then be monitored to confirm that cache_read_input_tokens rises and later batch requests reuse the intended prefix.

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

The evaluation results demonstrate prompt interference: improving attention to business-logic examples reduces performance on API design. Option C isolates the competing objectives so each model call can apply focused terminology, examples, evidence requirements, and evaluation criteria. The resulting structured findings can then be merged, deduplicated, and ranked before being posted.

Anthropic’s Building Effective AI Agents describes parallelization through sectioning, where independent aspects of a task are handled by separate model calls and subsequently aggregated. This pattern is appropriate when one prompt must evaluate several distinct considerations and a single call does not handle all of them reliably.

Option A increases context volume without resolving competition between the review objectives; irrelevant repository content may further dilute attention. Option B may improve known quiz-scoring cases but can overfit the reviewer to an incomplete checklist and does not restore API-design recall. Option D assumes that additional model capability will eliminate prompt interference without supporting evaluation evidence. Separate specialized review passes directly address the measured failure. Each pass should be evaluated independently, followed by an end-to-end evaluation confirming that consolidation preserves recall and does not introduce duplicated findings.

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

Option A describes the principal reason an independent review context is valuable. The implementing session contains the assumptions, interpretations, and reasoning that produced the refactor. When asked to review its own work, Claude may continue operating within those same assumptions and therefore overlook defects caused by them. A fresh reviewer evaluates the resulting diff and stated requirements independently, without inheriting the implementation narrative.

Anthropic’s Claude Code best-practices guidance explicitly recommends an adversarial review step using a fresh subagent or separate context. It explains that the reviewer should see the diff and review criteria rather than the reasoning that produced the change. Option B is possible in an unusually long session, but the scenario provides no evidence that the context window was exhausted. Option C could influence review quality, but no prompt difference is established. Option D is factually incorrect: a local Claude Code session can inspect the checked-out repository through its filesystem tools. The reliable workflow is therefore a writer/reviewer separation in which implementation occurs in one context and correctness review occurs in a fresh context with explicit evidence and reporting criteria. Claude Code best practices

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

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.

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

Option D identifies the dominant capacity problem. Anthropic states that everything sent in a request counts toward the context window : the system prompt, messages, documents, tool results, tool definitions, and the output Claude generates. A 175,000–190,000-token document is therefore not the complete input. Adding a 2,500-token tool schema, system instructions, wrappers, and the reserved output budget can push a nominally sub-200,000-token document close to or beyond the effective limit. Anthropic also warns that more context is not automatically better and that accuracy and recall can degrade as token count grows, a behavior described as context rot. That combination explains why short documents remain accurate while long documents lose information. Option A predicts a problem independent of document length, contradicting the measurements. Option B is an unsupported generalization and does not account for tool-definition overhead. Option C recognizes long-context degradation but ignores the concrete evidence that hidden prompt components consume the same window. The correct response is to count tokens for the complete request before submission, reserve output capacity, and chunk or retrieve relevant sections when the total approaches the model’s supported window.

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

The task is open-ended because neither the critical modules nor the required testing sequence is known in advance. The agent should first use lightweight discovery tools to map the repository, locate existing tests, identify central modules, and determine which components have high fan-in, business significance, complex branching, or extensive external dependencies. It can then produce an initial risk-based testing plan and refine it as new dependency information appears.

Anthropic distinguishes predefined workflows from agents that dynamically control their processes and tool usage. Agents are appropriate when the required steps cannot be reliably hardcoded and must adapt to environmental evidence. During execution, they should obtain ground truth through tool results and use that feedback to determine subsequent actions. ( https://www.anthropic.com/research/building-effective-agents ) Anthropic also identifies orchestrator-worker designs as suitable for complex coding and search tasks where the necessary subtasks depend on what the investigation reveals. ( https://www.anthropic.com/research/building-effective-agents )

Option A assigns effort using directory boundaries rather than risk. Option C exhausts context before delivering value. Option D uses alphabetical order, which has no relationship to impact or coverage priority.

Option B establishes an evidence-driven decomposition: discover, prioritize, test high-impact paths, measure results, and revise the plan as dependencies and uncovered risks emerge.

Official references/topics: Dynamic Task Decomposition; Adaptive Agent Loops; Orchestrator-Workers; Risk-Based Test Planning.

Option A gives the report generator the finished narrative context plus the evidence required to verify and cite its claims. The 3,000-token synthesis draft supplies organization and conclusions, while the source index preserves URLs, supporting excerpts, and claim-to-source mappings without transferring 120,000 tokens of raw search material. Anthropic’s effective context-engineering guidance recommends curating the smallest high-signal context and having subagents return condensed, distilled results rather than flooding later stages with their complete working history. Anthropic’s citation guidance likewise depends on retaining specific supporting passages and source locations. Option B is complete but inefficient and introduces context pollution that can reduce attention to relevant evidence. Option C separates citation insertion from the reasoning that produced the claims, making incorrect or unsupported matches more likely. Option D retains source names but discards the passages needed to demonstrate that each source actually supports the associated claim. The structured index should use stable source IDs and include only the excerpts necessary for the report’s factual claims, with validation that every cited claim maps to at least one evidence entry.

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