Anthropic CCA-F (Claude Certified Architect - Foundations (CCAR-F)) Practice Test 15

Question 140

In a technical review of a customer refund workflow, the architect must address the following constraints together: a consequential claim receives independent human sign-off; the team can diagnose which fields repeatedly fail extraction. Which change set is most defensible?

  1. accept model confidence as a substitute for authorization; and record validation failure codes and field paths per attempt
  2. route high-impact or low-evidence results to an authorized reviewer; and log only the final success-or-failure boolean
  3. accept model confidence as a substitute for authorization; and log only the final success-or-failure boolean
  4. route high-impact or low-evidence results to an authorized reviewer; and record validation failure codes and field paths per attempt

Explanation

Correct Answer

D:

In a customer refund workflow, human approval supplies accountability where a mistaken model result has material cost; alongside this, granular observability reveals schema weaknesses and document patterns, satisfying the distinct requirements that a consequential claim receives independent human sign-off and that the team can diagnose which fields repeatedly fail extraction.

Incorrect Answers

A:

In a customer refund workflow, granular observability reveals schema weaknesses and document patterns, but a model score does not confer business or legal authority; therefore the separate requirement that a consequential claim receives independent human sign-off would remain unsatisfied.

B:

In a customer refund workflow, human approval supplies accountability where a mistaken model result has material cost, but an aggregate flag hides the source of extraction errors; therefore the separate requirement that the team can diagnose which fields repeatedly fail extraction would remain unsatisfied.

C:

In a customer refund workflow, a model score does not confer business or legal authority and an aggregate flag hides the source of extraction errors; the design would fail both conditions: a consequential claim receives independent human sign-off and the team can diagnose which fields repeatedly fail extraction.

Question 141

Tests for a build verification pipeline will pass only if a pipeline gate reflects objective test outcomes and if a small approved typo fix is completed without excessive planning. Which proposed design directly satisfies both checks?

  1. accept a green status based on a model-written test summary alone; and launch a multi-stage planning effort for a single known line
  2. run tests and use actual exit codes and artifacts for the pass decision; and launch a multi-stage planning effort for a single known line
  3. run tests and use actual exit codes and artifacts for the pass decision; and use direct execution for the limited reviewed edit
  4. accept a green status based on a model-written test summary alone; and use direct execution for the limited reviewed edit
  5. implement only run tests and use actual exit codes and artifacts for the pass decision; make no corresponding change for the second requirement

Explanation

Correct Answer

C:

In a build verification pipeline, external deterministic checks prevent an assistant summary from declaring unexecuted tests successful; alongside this, a bounded low-risk change does not require a long exploratory workflow, satisfying the distinct requirements that a pipeline gate reflects objective test outcomes and that a small approved typo fix is completed without excessive planning.

Incorrect Answers

A:

In a build verification pipeline, a textual report may not correspond to any test execution and extra ceremony adds latency without materially lowering risk; the design would fail both conditions: a pipeline gate reflects objective test outcomes and a small approved typo fix is completed without excessive planning.

B:

In a build verification pipeline, external deterministic checks prevent an assistant summary from declaring unexecuted tests successful, but extra ceremony adds latency without materially lowering risk; therefore the separate requirement that a small approved typo fix is completed without excessive planning would remain unsatisfied.

D:

In a build verification pipeline, a bounded low-risk change does not require a long exploratory workflow, but a textual report may not correspond to any test execution; therefore the separate requirement that a pipeline gate reflects objective test outcomes would remain unsatisfied.

E:

In a build verification pipeline, external deterministic checks prevent an assistant summary from declaring unexecuted tests successful, but the independent mechanism for the other criterion is absent: a bounded low-risk change does not require a long exploratory workflow; as written, the design does not ensure that a small approved typo fix is completed without excessive planning.

Question 142

An architecture review of a source-grounded policy synthesis service finds two missing guarantees: client-side tool requests trigger another model turn after execution; a large research job combines specialized findings into one answer. What two-part change closes both gaps?

  1. end the loop whenever assistant text appears; and have all subagents independently publish the final answer
  2. implement only use a coordinator that delegates focused tasks and owns final synthesis; make no corresponding change for the first requirement
  3. branch on stop_reason tool_use and execute returned tool_use blocks; and use a coordinator that delegates focused tasks and owns final synthesis
  4. branch on stop_reason tool_use and execute returned tool_use blocks; and have all subagents independently publish the final answer
  5. end the loop whenever assistant text appears; and use a coordinator that delegates focused tasks and owns final synthesis

Explanation

Correct Answer

C:

In a source-grounded policy synthesis service, the response explicitly signals pending client execution and the loop must provide results before another model decision; alongside this, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, satisfying the distinct requirements that client-side tool requests trigger another model turn after execution and that a large research job combines specialized findings into one answer.

Incorrect Answers

A:

In a source-grounded policy synthesis service, text may accompany a tool request and is not the completion signal and independent final outputs offer no single point to reconcile contradictions; the design would fail both conditions: client-side tool requests trigger another model turn after execution and a large research job combines specialized findings into one answer.

B:

In a source-grounded policy synthesis service, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, but the independent mechanism for the other criterion is absent: the response explicitly signals pending client execution and the loop must provide results before another model decision; as written, the design does not ensure that client-side tool requests trigger another model turn after execution.

D:

In a source-grounded policy synthesis service, the response explicitly signals pending client execution and the loop must provide results before another model decision, but independent final outputs offer no single point to reconcile contradictions; therefore the separate requirement that a large research job combines specialized findings into one answer would remain unsatisfied.

E:

In a source-grounded policy synthesis service, the hub can integrate distinct subagent outputs and resolve overlap without peer-to-peer chatter, but text may accompany a tool request and is not the completion signal; therefore the separate requirement that client-side tool requests trigger another model turn after execution would remain unsatisfied.

Question 143

An architecture review of a risk-analysis research network finds two missing guarantees: a report separates documented findings from its own inference; one agent's draft is reviewed independently for errors. What two-part change closes both gaps?

  1. label direct source facts separately from analytical conclusions; and use a separate review pass with explicit criteria
  2. present every deduction as a direct source quotation; and ask the draft generator to declare its own work perfect
  3. label direct source facts separately from analytical conclusions; and ask the draft generator to declare its own work perfect
  4. present every deduction as a direct source quotation; and use a separate review pass with explicit criteria

Explanation

Correct Answer

A:

In a risk-analysis research network, distinguishing evidence from interpretation prevents inference being misattributed to a document; alongside this, independent criticism exposes omissions that unstructured self-praise can miss, satisfying the distinct requirements that a report separates documented findings from its own inference and that one agent's draft is reviewed independently for errors.

Incorrect Answers

B:

In a risk-analysis research network, unsupported attribution misrepresents what the source actually says and self-assessment without a second criterion-based pass is weak evidence; the design would fail both conditions: a report separates documented findings from its own inference and one agent's draft is reviewed independently for errors.

C:

In a risk-analysis research network, distinguishing evidence from interpretation prevents inference being misattributed to a document, but self-assessment without a second criterion-based pass is weak evidence; therefore the separate requirement that one agent's draft is reviewed independently for errors would remain unsatisfied.

D:

In a risk-analysis research network, independent criticism exposes omissions that unstructured self-praise can miss, but unsupported attribution misrepresents what the source actually says; therefore the separate requirement that a report separates documented findings from its own inference would remain unsatisfied.

Question 144

When designing a risk-analysis research network, the requirement is not satisfied unless independent research branches can finish without waiting on one another and near-overlapping retrieval tools are selected by actual boundary. Which implementation addresses the two independent conditions?

  1. chain every research agent in a fixed serial pipeline; and rely exclusively on short tool names for routing
  2. chain every research agent in a fixed serial pipeline; and document examples and conditions where each tool must not be used
  3. dispatch the independent branches concurrently through the coordinator; and document examples and conditions where each tool must not be used
  4. dispatch the independent branches concurrently through the coordinator; and rely exclusively on short tool names for routing

Explanation

Correct Answer

C:

In a risk-analysis research network, parallel delegation reduces latency when individual investigations do not consume each other's outputs; alongside this, contrastive guidance helps tool choice when resource names look similar, satisfying the distinct requirements that independent research branches can finish without waiting on one another and that near-overlapping retrieval tools are selected by actual boundary.

Incorrect Answers

A:

In a risk-analysis research network, unnecessary sequential handoffs increase latency for independent subtasks and names alone may not capture the distinction in scope or authorization; the design would fail both conditions: independent research branches can finish without waiting on one another and near-overlapping retrieval tools are selected by actual boundary.

B:

In a risk-analysis research network, contrastive guidance helps tool choice when resource names look similar, but unnecessary sequential handoffs increase latency for independent subtasks; therefore the separate requirement that independent research branches can finish without waiting on one another would remain unsatisfied.

D:

In a risk-analysis research network, parallel delegation reduces latency when individual investigations do not consume each other's outputs, but names alone may not capture the distinction in scope or authorization; therefore the separate requirement that near-overlapping retrieval tools are selected by actual boundary would remain unsatisfied.

Question 145

When designing a legacy service decomposition, the requirement is not satisfied unless two teams' analyses are reconciled before publication and a new source file is created from supplied content. Which implementation addresses the two independent conditions?

  1. add a synthesis stage with explicit conflict-resolution criteria; and use Grep to create the source file
  2. add a synthesis stage with explicit conflict-resolution criteria; and use Write for file creation
  3. publish whichever branch finishes last; and use Grep to create the source file
  4. publish whichever branch finishes last; and use Write for file creation

Explanation

Correct Answer

B:

In a legacy service decomposition, merging divergent work requires an authoritative step rather than choosing by arrival time; alongside this, writing a new artifact is appropriate when no existing target needs surgical modification, satisfying the distinct requirements that two teams' analyses are reconciled before publication and that a new source file is created from supplied content.

Incorrect Answers

A:

In a legacy service decomposition, merging divergent work requires an authoritative step rather than choosing by arrival time, but search utilities do not create code artifacts; therefore the separate requirement that a new source file is created from supplied content would remain unsatisfied.

C:

In a legacy service decomposition, run order is not an evidence or quality standard and search utilities do not create code artifacts; the design would fail both conditions: two teams' analyses are reconciled before publication and a new source file is created from supplied content.

D:

In a legacy service decomposition, writing a new artifact is appropriate when no existing target needs surgical modification, but run order is not an evidence or quality standard; therefore the separate requirement that two teams' analyses are reconciled before publication would remain unsatisfied.

Question 146

Tests for a mobile client bug-fix task will pass only if context reduction does not erase unresolved obligations and if a straightforward lookup avoids unnecessary agent coordination. Which proposed design directly satisfies both checks?

  1. track pending approvals and required next steps in durable task state; and spawn a coordinator plus multiple specialists for every trivial query
  2. track pending approvals and required next steps in durable task state; and use one focused tool-assisted agent for the bounded task
  3. assume the agent will recall every open action from memory; and use one focused tool-assisted agent for the bounded task
  4. assume the agent will recall every open action from memory; and spawn a coordinator plus multiple specialists for every trivial query

Explanation

Correct Answer

B:

In a mobile client bug-fix task, persisted obligations survive when natural-language history is shortened; alongside this, orchestration overhead is not justified when there is no useful specialization or concurrency, satisfying the distinct requirements that context reduction does not erase unresolved obligations and that a straightforward lookup avoids unnecessary agent coordination.

Incorrect Answers

A:

In a mobile client bug-fix task, persisted obligations survive when natural-language history is shortened, but extra agents add latency and handoff risk without new capabilities; therefore the separate requirement that a straightforward lookup avoids unnecessary agent coordination would remain unsatisfied.

C:

In a mobile client bug-fix task, orchestration overhead is not justified when there is no useful specialization or concurrency, but window truncation can drop an outstanding approval or escalation; therefore the separate requirement that context reduction does not erase unresolved obligations would remain unsatisfied.

D:

In a mobile client bug-fix task, window truncation can drop an outstanding approval or escalation and extra agents add latency and handoff risk without new capabilities; the design would fail both conditions: context reduction does not erase unresolved obligations and a straightforward lookup avoids unnecessary agent coordination.

Question 147

An audit of a pull-request review pipeline identifies two unmet requirements: an exploratory branch can be compared with a baseline later and a formatter handles diverse legitimate examples consistently. Select TWO actions that remedy those particular deficiencies.

  1. supply only a bare instruction to keep formatting consistent
  2. give a small set of representative input-output demonstrations
  3. overwrite the baseline notes with the trial branch's results
  4. preserve both branch identifiers and outcome summaries

Explanation

Correct Answers

B:

For a pull-request review pipeline, few-shot examples show the intended mapping more concretely than broad style adjectives, which directly establishes that a formatter handles diverse legitimate examples consistently; the separate requirement that an exploratory branch can be compared with a baseline later is handled by a different action.

D:

For a pull-request review pipeline, tracking lineage makes result comparison possible without confusing which session produced an artifact, which directly establishes that an exploratory branch can be compared with a baseline later; the separate requirement that a formatter handles diverse legitimate examples consistently is handled by a different action.

Incorrect Answers

A:

For a pull-request review pipeline, abstract instructions leave many output choices open, so this option cannot establish that a formatter handles diverse legitimate examples consistently; correctly addressing an exploratory branch can be compared with a baseline later elsewhere does not repair that deficiency.

C:

For a pull-request review pipeline, losing provenance prevents trustworthy evaluation, so this option cannot establish that an exploratory branch can be compared with a baseline later; correctly addressing a formatter handles diverse legitimate examples consistently elsewhere does not repair that deficiency.

Question 148

During review of a customer refund workflow, an unmet criterion states that every high-impact tool invocation produces an audit event. Which measure resolves this specific gap?

  1. interrupt or deny the tool until an authorization callback approves it
  2. register a PreToolUse hook that checks the operation against policy
  3. record the tool name, permitted inputs, outcome, and task identifier in a hook
  4. use a PostToolUse processing hook to standardize the returned data
  5. infer tool activity from the final natural-language answer

Explanation

Correct Answer

C:

For a customer refund workflow, runtime instrumentation observes actual proposed or completed tool activity; this directly establishes that every high-impact tool invocation produces an audit event instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although execution gates make the approval binding on the selected action and inputs, that only supports the distinct goal that a destructive tool receives human authorization at execution time, not the requirement that every high-impact tool invocation produces an audit event in a customer refund workflow.

B:

Although pre-execution interception can reject a disallowed call rather than relying on post-hoc advice, that only supports the distinct goal that sensitive tool calls are denied before they reach an executor, not the requirement that every high-impact tool invocation produces an audit event in a customer refund workflow.

D:

Although post-execution interception can clean result fields and attach useful status without changing the model's tool selection, that only supports the distinct goal that tool output is normalized before it enters the agent context, not the requirement that every high-impact tool invocation produces an audit event in a customer refund workflow.

E:

In a customer refund workflow, a summary can omit failed calls or delegated actions; as a result, the stated requirement that every high-impact tool invocation produces an audit event would still not be met.

Question 149

An audit of a repository release validation process asks how to make sure that a repeatable code-review procedure is available as a named workflow. Which implementation should be selected?

  1. configure the skill to run in an isolated forked context where supported
  2. create a documented reusable skill in SKILL.md
  3. define how the skill accepts and uses invocation arguments
  4. retype the entire procedure in every conversation

Explanation

Correct Answer

B:

For a repository release validation process, skills package instructions and supporting resources for invocation across similar tasks; this directly establishes that a repeatable code-review procedure is available as a named workflow instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although a fork isolates exploratory work and returns a concise result to its caller, that only supports the distinct goal that a delegated skill should not fill the caller's active context, not the requirement that a repeatable code-review procedure is available as a named workflow in a repository release validation process.

C:

Although parameterized workflows apply one reviewed procedure to different resources without hardcoding targets, that only supports the distinct goal that a shared skill can take a supplied target name or file path, not the requirement that a repeatable code-review procedure is available as a named workflow in a repository release validation process.

D:

In a repository release validation process, manual repetition produces drift and loses shared revisions; as a result, the stated requirement that a repeatable code-review procedure is available as a named workflow would still not be met.

Question 150

In a technical review of an internal developer coding workflow, the architect must address the following constraints together: workload growth does not cause uncontrolled parallel fan-out; delegated investigations stay within bounded scope. Which change set is most defensible?

  1. launch all possible child tasks at once without resource controls; and ask every subagent to investigate everything it can find
  2. limit concurrency and schedule independent jobs against execution budgets; and specify the question, allowed sources, expected output, and stopping criterion
  3. launch all possible child tasks at once without resource controls; and specify the question, allowed sources, expected output, and stopping criterion
  4. limit concurrency and schedule independent jobs against execution budgets; and ask every subagent to investigate everything it can find

Explanation

Correct Answer

B:

In an internal developer coding workflow, bounded orchestration balances throughput with tool quotas and downstream service capacity; alongside this, a task contract prevents specialist exploration from swallowing the coordinator's larger goal, satisfying the distinct requirements that workload growth does not cause uncontrolled parallel fan-out and that delegated investigations stay within bounded scope.

Incorrect Answers

A:

In an internal developer coding workflow, unbounded fan-out can overwhelm tools and blow through cost budgets and unbounded exploration dilutes signal and inflates context and latency; the design would fail both conditions: workload growth does not cause uncontrolled parallel fan-out and delegated investigations stay within bounded scope.

C:

In an internal developer coding workflow, a task contract prevents specialist exploration from swallowing the coordinator's larger goal, but unbounded fan-out can overwhelm tools and blow through cost budgets; therefore the separate requirement that workload growth does not cause uncontrolled parallel fan-out would remain unsatisfied.

D:

In an internal developer coding workflow, bounded orchestration balances throughput with tool quotas and downstream service capacity, but unbounded exploration dilutes signal and inflates context and latency; therefore the separate requirement that delegated investigations stay within bounded scope would remain unsatisfied.

Claude Certified Architect - Foundations (CCAR-F) (CCA-F) Practice Tests