Free Practice Questions for Anthropic CCAR-F Exam

Option B correctly separates asynchronous bulk work from latency-sensitive operational work. Anthropic describes the Message Batches API as a cost-effective asynchronous service for high-volume requests that do not require immediate responses. Batch requests are processed independently, normally finish within an hour, may remain pending for up to 24 hours, and are billed at 50 percent of standard API prices. Those characteristics fit standard monthly reports because they are archived after processing and have no immediate business deadline. Urgent exception reports, however, must trigger an alert within 30 minutes. The batch service cannot guarantee that deadline, even if many batches finish quickly; a workload should not use typical completion time as a service-level guarantee. Routing exceptions through the synchronous Messages API provides the real-time response path needed for alerting, while the shared JSON schema keeps downstream records consistent across both routes. Option A knowingly permits delayed alerts. Option C introduces an hourly submission delay before processing even begins. Option D meets latency requirements but wastes the batch discount on non-urgent reports. A routing layer based on document priority therefore satisfies both the cost objective and the business deadline without changing the extraction contract.

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

Option B introduces an evaluator-and-refinement loop at the correct orchestration layer. The coordinator already owns the research plan and delegation decisions, so it should inspect the synthesis result against the required questions, identify coverage gaps, and issue focused follow-up assignments. Anthropic’s description of its multi-agent research system follows this pattern: the lead agent synthesizes returned findings, determines whether additional research is required, and creates new subagents or refines its strategy before producing the final result. Increasing the initial query breadth, option A, may generate additional irrelevant material and cannot guarantee that unforeseen gaps will be covered. Option C merely documents the incompleteness instead of correcting it. Option D weakens role separation by giving the synthesis agent search capabilities, increasing tool complexity and bypassing the coordinator’s centralized tracking. Targeted re-delegation preserves specialized responsibilities and creates an observable sequence of research, evaluation, refinement, and resynthesis. The coordinator should also maintain explicit coverage criteria and limit the number of refinement rounds so the system improves completeness without entering an uncontrolled research loop.

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

Formatting is deterministic and should be enforced by deterministic tooling rather than stronger natural-language instructions. A PostToolUse hook executes after a successful tool operation. Matching Edit|Write restricts the hook to file modifications, allowing the edited file path to be passed directly to Prettier.

Anthropic provides this exact pattern in its official hooks guidance: configure a PostToolUse event with an Edit|Write matcher and run Prettier against the modified file. This ensures formatting occurs automatically after every relevant edit instead of depending on Claude remembering to execute a formatter. ( https://code.claude.com/docs/en/hooks-guide )

Option A still relies on instruction-following and unnecessarily loads procedural material. Option B asks another probabilistic model evaluation to determine whether formatting is correct, even though Prettier can enforce the result directly. A Stop hook also runs later than necessary. Option C improves contextual relevance but does not guarantee compliance; path-scoped rules remain instructions rather than enforcement controls.

The hook should be stored in project settings so the workflow is shared by the team. The formatter’s exit status should also be monitored so configuration or syntax failures are visible instead of silently ignored.

Official references/topics: Claude Code Hooks; PostToolUse; Edit|Write Matchers; Deterministic Formatting Enforcement.

The failure is caused by missing evidence, not insufficient reasoning over the supplied evidence. A static prompt containing only changed files cannot reliably identify callers, configuration dependencies, generated interfaces, or indirect relationships located elsewhere in the repository. Asking Claude to reason more deeply cannot recover code that it was never given.

Option A converts the review into a bounded agentic loop. Claude can search for symbol references, read relevant callers, inspect type definitions, and follow newly discovered dependencies before validating a potential defect. Anthropic describes the Claude Code agentic loop as gathering context, taking action, verifying results, and repeating based on tool feedback. A turn limit preserves predictable cost and execution time.

Option C improves coverage but imposes an arbitrary two-hop boundary and depends on the accuracy of a precomputed graph, which may omit dynamic imports, reflection, generated code, configuration references, or language-specific call relationships. Option D creates duplicated context and aggregation complexity while still limiting each reviewer to predetermined dependents. Option B changes the reasoning instructions but supplies no mechanism for checking unchanged files. Tool-enabled, just-in-time retrieval is therefore the most adaptable and reliable architecture for cross-file review.

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

Request B benefits substantially more from an explicit multi-phase workflow because it is broad, judgment-intensive, and likely to affect multiple execution paths. Improving error handling requires the agent to identify current failure modes, determine which exceptions should be caught, preserve useful diagnostic information, prevent partial state corruption, and verify that the resulting behavior remains consistent across the module. An analyze → propose → implement → review sequence separates those concerns and creates checkpoints before consequential edits are made.

Request A is comparatively deterministic. The function and target name are already defined, and the task primarily requires locating references, applying the rename, and running tests or static analysis. Anthropic’s Claude Code guidance states that planning is most useful when the approach is uncertain, the work spans multiple files, or the developer is unfamiliar with the affected code. For a small change that can be described as a straightforward diff, direct implementation is usually preferable. ( https://code.claude.com/docs/en/best-practices )

Anthropic also characterizes prompt chaining as appropriate when a task can be divided into fixed stages and additional latency is justified by increased accuracy. Request B fits that pattern because analysis and review materially reduce the risk of introducing swallowed exceptions or inconsistent recovery behavior. ( https://www.anthropic.com/research/building-effective-agents )

Official references/topics: Prompt Chaining; Plan Before Editing; Multi-Phase Coding Workflows; Verification and Review.

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 defects are coupled, so changing all three simultaneously would make it difficult to determine which modification caused an improvement or regression. Option C establishes a controlled sequence: correct the foundational column geometry, verify the resulting layout, format dates within the stabilized columns, and finally tune page breaks using the resulting content heights.

Anthropic recommends tight feedback loops and early course correction. It also advises supplying Claude with an executable or observable verification mechanism, such as a test, build result, generated fixture, or screenshot comparison. Claude can then make a focused change, inspect the output, and iterate until that specific condition is satisfied. ( https://code.claude.com/docs/en/best-practices )

Option A discards useful context from the functioning database implementation. Option B changes multiple interacting variables in one pass, making failures harder to isolate. Option D provides a useful visual target but does not replace precise technical constraints or incremental verification.

Each stage should have explicit acceptance criteria—for example, minimum column widths, expected date strings, and page-break fixtures using short and long content. Once a stage passes, its test becomes a regression guard for subsequent changes.

Official references/topics: Incremental Refinement; Tight Feedback Loops; Observable Verification; Regression Control.

Option C allows orchestration effort to scale according to the actual evidence and processing requirements of each request. A factual lookup might require one search operation and a direct coordinator response, while comparative research may justify parallel search, document analysis, synthesis, and formal report generation.

Anthropic’s orchestrator-workers guidance describes a central model dynamically decomposing a task, choosing workers, and combining their results. This pattern is particularly appropriate when required subtasks cannot be predicted reliably in advance. Anthropic’s multi-agent research architecture similarly uses a lead agent to analyze the query and determine an appropriate research strategy.

Option A creates an inflexible two-route system and still sends every non-factual query through the most expensive workflow. Option B requires labeled training data, an externally maintained classifier, and a stable definition of the optimal agent combination. Option D is less expensive to implement but becomes brittle as query types evolve beyond predetermined categories. Dynamic coordination uses the model’s existing reasoning ability to assess source requirements, analytical depth, expected output, and uncertainty before invoking only the specialists that materially improve the result.

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

The decisive trade-off is whether the workflow can tolerate asynchronous completion. Anthropic’s Message Batches API documentation states that batch requests receive a 50% discount and that most batches finish within one hour, but processing can continue for as long as 24 hours. Therefore, the review process is suitable for batching only if potentially delayed feedback remains useful.

Option C directly tests that operational requirement. The reviews are already non-blocking, which makes batching promising, but non-blocking does not automatically mean that feedback delivered many hours later still has value. If developers have already merged and moved to unrelated work, delayed security findings may increase remediation cost or remain unaddressed.

Option A is manageable through each request’s unique custom_id, which allows results to be correlated regardless of return order. Option B is incorrect because batch requests can contain supported multi-turn conversation histories and tool-use configurations; each request is processed independently, but it need not represent a single conversational turn. Option D reverses the relevant consideration: batch processing is not intended to provide near-instantaneous responses. The real question is whether the cost saving justifies its longer and nondeterministic completion time.

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

Limited review capacity should be concentrated on records with the highest probability of semantic error. Schema validation confirms that the response has the correct structure and data types; it does not establish that the extracted values are accurate. Ambiguous wording, contradictory passages, missing evidence, and model-reported uncertainty are direct indicators that an extraction requires human judgment.

Anthropic’s reliability guidance recommends permitting Claude to express uncertainty, grounding factual outputs in source material, and validating critical information because hallucination-reduction methods do not eliminate errors completely. These principles support routing uncertain or evidentially conflicted records to reviewers rather than treating syntactically valid output as automatically trustworthy. ( https://docs.anthropic.com/en/docs/test-and-evaluate/strengthen-guardrails/reduce-hallucinations )

Option B may waste reviewer capacity on clear, well-supported values while overlooking ambiguous errors in other fields. Option C is reactive: downstream acceptance does not guarantee semantic correctness, and silent errors may never produce processing failures. Option D provides an unbiased estimate of overall quality and should be retained as a secondary audit mechanism, but random selection is not the most efficient way to intercept risky records when only 5% can be reviewed.

In production, model confidence should not be treated as a calibrated probability by itself. It should be combined with objective signals such as contradictory source spans, missing citations, OCR quality, validation warnings, document type, and business impact.

Official references/topics: Human-in-the-Loop Review, Uncertainty Handling, Source Grounding, Risk-Based Escalation.