CCAR-F Anthropic Claude Certified Architect – Foundations Free Practice Exam Questions (2026 Updated)

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.

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

Option D is the closest match to Claude Code’s documented editing procedure. The Claude Code tools reference explains that Edit performs exact string replacement and requires old_string to appear exactly once. When the text occurs multiple times, the prescribed response is to include sufficient surrounding context to identify one occurrence uniquely. For this insertion, the match should span a distinctive boundary between the preceding function and the following function. It does not literally need 30 lines; it needs the smallest exact block that is demonstrably unique, but option D is the only answer expressing that method.

Option A would modify every occurrence of a repeated pattern and could insert the helper function multiple times. Option B places the function at the end rather than at the required architectural location. Option C can technically work, but Write replaces the complete file and increases the change surface. Anthropic explicitly states that Write creates or overwrites full files, while partial modifications should use Edit. A targeted, uniquely anchored Edit preserves all unrelated content and produces a smaller, safer diff.

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

The checklist is a reusable, task-specific procedure that should load only when a pull-request review is being performed. A /review command provides an explicit invocation mechanism, prevents repeated copy-and-paste, and keeps the checklist out of unrelated coding, debugging, and documentation sessions.

In current Claude Code terminology, custom commands have been consolidated into skills. A .claude/skills/review/SKILL.md file creates a /review command, while the legacy .claude/commands/review.md format remains supported. Anthropic recommends skills when users repeatedly supply the same checklist or multi-step procedure; unlike CLAUDE.md content, the skill body is loaded only when invoked or determined relevant. ( https://code.claude.com/docs/en/skills )

Option B introduces an isolated agent context when the requirement is primarily to inject a repeatable review procedure. A subagent could be useful for independent verification, but it is not necessary merely to avoid repasting the checklist. Option C bloats every session with instructions that apply only to code review. Option D controls editing permissions and planning behavior; it does not encode review criteria.

The review skill can also pre-authorize read-only tools and accept a pull-request identifier or branch as an argument.

Official references/topics: Claude Code Skills; Custom Slash Commands; On-Demand Instructions; Reusable Review Workflows.

The schema already supports the correct representation of missing evidence: null . The remaining defect is behavioral. Claude must be explicitly instructed that absence of information is a valid outcome and that values may be populated only when directly supported by the supplied article.

Anthropic’s hallucination-reduction guidance recommends explicitly permitting Claude to express uncertainty, grounding outputs in the source, and retracting claims that lack supporting evidence. It also recommends restricting the model to the provided documents rather than allowing unsupported external knowledge. ( https://docs.anthropic.com/en/docs/test-and-evaluate/strengthen-guardrails/reduce-hallucinations ) Option C translates those controls directly into the extraction contract: when no source evidence exists, the model returns null .

Option A may improve baseline performance but does not remove the architectural ambiguity that encourages completion of missing fields. Option B is counterproductive because non-nullable required fields force the model to provide values even when the article contains none. Structured validation would confirm that the response is syntactically valid while accepting fabricated content. Option D adds cost, latency, and another probabilistic model decision; a second model can repeat or endorse the original hallucination.

A robust implementation should supplement the instruction with source spans or quotations for populated fields and automated checks where feasible. Nevertheless, among the options, explicit null behavior is the direct and most effective correction.

Official references/topics: Reduce Hallucinations; External-Knowledge Restriction; Nullable JSON Schema Fields; Grounded Extraction.

An unchanged retry repeats the same task specification and therefore commonly reproduces the same invalid interpretation. The validator has generated precise corrective information— quantity requires a float, but the model returned the range string 2 to 3 . Supplying that error in a follow-up turn converts a generic retry into an iterative repair operation.

Anthropic identifies iterative refinement as a method for detecting and correcting inconsistencies by feeding an earlier output back into a subsequent request with targeted instructions. ( https://docs.anthropic.com/en/docs/test-and-evaluate/strengthen-guardrails/reduce-hallucinations ) Option A applies that pattern directly. Claude receives the invalid output, the exact Pydantic error, and an instruction to return a schema-compliant correction. The application should cap retries, retain the original source, and escalate cases that cannot be represented without information loss.

Option B does not guarantee correct formatting; lower temperature may make the same wrong output more repeatable. Option C can be valuable for systematic OCR or source-format problems, but it is unnecessarily broad when the immediate failure is already described by the validator. Option D increases cost and complexity without first using the actionable feedback available from the existing validation layer.

For supported models, native Structured Outputs should also be considered because they guarantee schema-conformant JSON and can prevent many Pydantic shape failures before they occur. ( https://platform.claude.com/docs/en/build-with-claude/structured-outputs )

Official references/topics: Iterative Refinement; Validation-Error Feedback; Bounded Retry Loops; Structured Outputs.

Stratified random sampling provides both an ongoing quality-control mechanism and an unbiased measurement framework. By reviewing a fixed proportion of high-confidence outputs across meaningful strata—such as document type, field, source format, and business risk—the organization can estimate the residual error rate, compare performance across releases, and discover failure patterns that were not anticipated when existing rules were designed.

Anthropic recommends measurable success criteria and evaluations that mirror the real-world task distribution, including edge cases. Evaluation volume and repeatability are important because improvements must be demonstrated empirically rather than inferred from isolated examples. ( https://docs.anthropic.com/en/docs/build-with-claude/develop-tests ) A weekly sampling program creates a stable benchmark and allows confidence intervals, trend analysis, regression detection, and error-taxonomy updates.

Option A detects only disagreements between stochastic extractions. Two attempts may produce the same plausible but incorrect answer, so agreement is not equivalent to factual correctness. Option B addresses known patterns but will miss new failure modes and may generate excessive false positives. Option C actually lowers the review threshold in the wrong direction: documents between 70% and 85% would be treated as automated rather than reviewed if the routing rule remains “below threshold,” and changing thresholds alone does not measure high-confidence error prevalence.

Official references/topics: Evaluation Design; Representative Test Distributions; Continuous Reliability Measurement; Human-in-the-Loop Sampling.

The problem is an undefined relevance threshold. Claude is finding technically valid observations, but the prompt does not clearly distinguish actionable defects from acceptable conventions and low-value style preferences. Option A establishes explicit positive and negative reporting criteria, allowing the model to apply the team’s actual definition of a useful finding during generation.

Anthropic’s prompt-engineering guidance emphasizes clear, specific instructions and well-defined success criteria. The managed Code Review documentation similarly recommends defining skipped categories, generated paths, severity rules, and evidence requirements. Reporting “bugs affecting correctness or security” while excluding “formatting handled by CI and documented local conventions” is substantially more precise than asking the model to be generally conservative.

Option B adds cost, latency, another probabilistic decision, and a new evaluation surface before improving the original prompt. Option C confuses confidence with importance: Claude may be highly confident about a trivial style observation. Option D is dangerously broad because it can suppress legitimate but uncertain bugs, reducing recall. Explicit relevance criteria address the demonstrated failure directly while preserving the model’s ability to investigate and report genuine correctness or security problems.

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

Option B follows the Claude Agent SDK’s subagent context model. A normal subagent begins with a fresh context window and does not inherit the parent agent’s conversation history or prior tool results. Anthropic’s Subagents in the SDK documentation states that the information passed from parent to subagent is the spawning tool’s prompt string; required file paths, decisions, errors, or findings must therefore be included in that prompt. In this scenario, the coordinator should supply both agents’ relevant findings, source metadata, and explicit synthesis instructions. “Complete findings” means the full required result artifacts, not every intermediate search trace. Option C incorrectly assumes automatic context inheritance. Option A introduces callbacks that are neither necessary nor the standard handoff mechanism. Option D can be a valid custom architecture when a shared store has deliberately been implemented, but the question does not establish such infrastructure, and identifiers alone do not give the subagent information. The prompt should use clear sections or structured objects to distinguish web findings, document findings, sources, unresolved conflicts, and expected output. This preserves context isolation while providing everything the synthesis task actually requires.

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

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

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

Option A identifies the direct configuration contradiction. Each system prompt defines a specialized responsibility, but the corresponding tool allowlist presents unrelated actions as available capabilities. The synthesis agent may therefore interpret web searching as an acceptable way to fill evidence gaps, while the report generator may perform document analysis instead of limiting itself to report production.

Anthropic’s subagent documentation defines subagents as focused workers with their own prompts and specific tool access. Its tool-definition guidance also recommends reducing selection ambiguity by presenting clear, relevant tools. The appropriate correction is least-capability configuration: expose search tools to the search agent, document tools to the analyzer, synthesis utilities to the synthesizer, and formatting or output tools to the report generator.

Option B may affect token efficiency but does not explain the role-specific misuse pattern. Option C concerns delegation, whereas the improper calls occur after successful delegation. Option D is tempting, but Anthropic does not define four or five tools as a universal reliability threshold; 18 tools alone does not prove threshold failure. The decisive defect is misalignment between declared roles and permitted capabilities.

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

Option B applies Anthropic’s dedicated asynchronous bulk-processing mechanism while preserving the existing model and prompt for every commit. The Message Batches API accepts independent Messages API requests, each identified by a unique custom_id, and charges both input and output usage at 50% of standard API prices. The approximately 12-hour latency allowance makes the release-notes workload well suited to batching because immediate results are unnecessary.

Option A may reduce wall-clock completion time, but concurrency does not alter the API’s per-token price. Option C changes the task structure and risks exceeding context or output limits, mixing commit-level classifications, complicating retries, and making it harder to associate errors with individual commits. A single large request also does not automatically consume fewer tokens because the model must still process all commit content. Option D violates the requirement to retain the same model tier and output-quality profile. Batch results may arrive in an order different from submission order, so the pipeline must associate every response with its original commit through custom_id. This provides lower cost without changing the individual review prompts. Anthropic Message Batches documentation

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

Option A combines lossless persistence with selective restoration. Each agent should checkpoint structured records containing completed document identifiers, extracted findings, source provenance, unresolved work, verification status, and schema version. A coordinator-level manifest can record which stages completed and where their artifacts are stored. On recovery, the coordinator skips completed documents and injects only the state required by each restarted agent.

Anthropic’s effective context-engineering guidance recommends structured notes stored outside the active context window and reloaded when needed. This preserves critical dependencies and progress without replaying an entire execution history.

Option B fragments recovery ownership across agents and makes cross-agent consistency, versioning, and dependency validation difficult. Option C preserves extensive logs but wastes context on redundant tool calls, obsolete instructions, and intermediate messages. Option D is useful for relevance retrieval but semantic search can omit exact details and should not serve as the authoritative recovery record. Structured checkpoints and a validated manifest provide deterministic recovery, efficient context reconstruction, auditability, and precise provenance. Writes should be atomic so partially produced exports are never mistaken for completed work.

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

A mandatory compliance threshold must be enforced outside probabilistic model reasoning. A PreToolUse hook can inspect every attempted process_refund call before execution, compare its amount with the $500 threshold, and deny the call when the limit is exceeded. The host application can then create the human-escalation case using the validated customer and order context.

Anthropic describes hooks as deterministic controls that ensure required actions occur instead of relying on the model to choose them. Agent SDK documentation confirms that a single denying PreToolUse hook blocks the tool call, including MCP tools matched through their qualified tool names. ( https://docs.anthropic.com/en/docs/claude-code/hooks-guide )

Options A and B improve expected behavior but cannot guarantee compliance. The stated production failure rate demonstrates that prompting alone is insufficient. Option C prevents the refund from completing, but the subsequent escalation still depends on Claude correctly interpreting the returned error and invoking the human tool. It therefore enforces the financial block but not the complete escalation requirement.

Option D enforces both sides of the policy at the orchestration boundary: deny the unauthorized action and route the case to an approved human process. The escalation action should be idempotent and auditable.

Official references/topics: PreToolUse hooks, deterministic policy enforcement, MCP tool interception, human-approval controls.

The Messages API exposes stop_reason specifically so the application can determine why Claude stopped generating and what action is required next. A value of tool_use means Claude is requesting one or more tools and expects the application to execute them and return corresponding tool_result blocks. A value of end_turn means Claude has naturally completed the response. ( https://platform.claude.com/docs/en/build-with-claude/handling-stop-reasons )

Anthropic’s agent-loop tutorial implements this as a loop that continues executing tools and returning results while stop_reason remains tool_use . Once the value changes, the response is treated according to the new terminal or continuation condition. ( https://platform.claude.com/docs/en/agents-and-tools/tool-use/build-a-tool-using-agent )

Option A is unreliable because an assistant response can contain both text and tool-use blocks. Text alone does not prove that the workflow is complete. Option B requires the application to predict that no further tool call is needed, defeating Claude’s ability to adapt from tool results. Option D is an important safety limit but is not the primary completion signal; an arbitrary maximum may terminate a valid workflow prematurely.

The harness should check stop_reason , process every requested tool call, append results to the conversation, and maintain a separate maximum-turn safeguard against runaway loops.

Official references/topics: Messages API stop reasons, tool-use loops, tool-result continuation, bounded orchestration.

Option C preserves the semantic strengths of each information type instead of forcing heterogeneous evidence into one presentation structure. Financial values share comparable fields and therefore belong in a table. News developments require connected prose to preserve chronology and causality. Patent technology areas are naturally represented as grouped or prioritized lists.

Anthropic’s prompting best practices recommend giving explicit output-format instructions and matching the requested format to the intended communication goal. The synthesis prompt should therefore include rendering rules for each recognized content type while maintaining common provenance fields behind the presentation.

Option A damages numerical comparability and makes trends harder to scan. Option B can be useful as an internal exchange schema, but presenting the entire briefing as uniform JSON does not produce an effective executive document. Option D normalizes transport but does not correct the synthesis agent’s bullet-only rendering policy; a common representation can still be displayed badly. The correct design separates structured internal interchange from audience-facing presentation. The synthesis agent should preserve citations and metadata while selecting the most legible form for each class of evidence.

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

This migration is a high-impact, cross-module change with several independent breaking changes. Before editing, Claude must determine how the callback-based API is currently used, where the restructured User fields propagate, whether deprecated methods are wrapped or re-exported, and which downstream modules depend on the affected behavior. Plan mode is therefore the correct starting point because it allows Claude to inspect the repository, identify affected code paths, and produce an implementation strategy without modifying source files.

Anthropic recommends separating exploration and planning from implementation when the approach is uncertain, the change affects multiple files, or the developer is unfamiliar with the impacted code. Direct execution is better reserved for small, clearly scoped changes that can be described as a simple diff. ( https://code.claude.com/docs/en/best-practices )

Option A applies transformations before establishing whether every usage follows the same pattern. Option B turns the test suite into a reactive discovery mechanism and may miss untested behavior. Option D provides useful migration documentation but assumes all 45 files can be changed uniformly. The reliable sequence is exploration, impact mapping, migration planning, implementation, and verification against tests and type checks.

Official references/topics: Plan Mode; Explore–Plan–Implement Workflow; Multi-File Migration Planning; Verification.

Option B expresses both independent delegations in the same orchestration turn, allowing the runtime to execute them concurrently and return their results together. The current Claude Agent SDK calls the subagent-spawning capability the Agent tool; Task is its former name. Anthropic’s SDK subagent documentation explicitly identifies parallel analysis as a primary subagent use case. Claude tool responses can also contain multiple tool_use blocks , enabling independent calls to be handled as one parallel group rather than as serial model turns. Option A shortens each execution but does not remove the unnecessary wait between them and may reduce analysis quality. Option C provides useful behavioral guidance, but instructions alone do not establish the required response structure; the coordinator must actually emit both calls together. Option D duplicates coordinator execution, complicates state management, and creates unnecessary aggregation work. The correct flow is parallel fan-out from one coordinator, followed by a synchronization point that validates both results before synthesis begins. Failures should be tracked independently so that only the unsuccessful branch requires retrying.

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

Option B identifies the missing executable capability. Defining specialized agents makes their configurations available, but the coordinator must still be permitted to call the tool that invokes them. Without that tool, Claude can describe an intended delegation in ordinary text but cannot create a subagent execution.

The current Claude Agent SDK documentation requires " Agent " in allowedTools to auto-approve subagent invocations. The tool was renamed from " Task " to " Agent " in Claude Code 2.1.63, so the terminology in the original candidate question required correction. Older integrations may still expose " Task " in initialization or permission records.

Option A is unlikely because properly written AgentDefinition.description values already tell Claude when each agent should be used. Option C misinterprets context isolation: the parent supplies the subagent’s assignment through the Agent tool’s prompt, and no additional automatic forwarding setting is required. Option D would normally produce truncation evidence or a max_tokens stop reason rather than silent absence of every invocation. The coordinator needs both agent definitions and permission to use the invocation tool.

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

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.

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