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

Question 190

The release gate for an order-cancellation service requires that a selector accepts only supported operation names; it also requires that a truncated response is not mistaken for successful completion. Which TWO actions meet the specified checks? Choose TWO.

  1. declare an operation enum in the schema and reject values outside it in the tool handler
  2. handle max_tokens as truncation rather than end_turn
  3. interpret every non-tool stop reason as a successful final answer
  4. ask the model to invent a suitable action string

Explanation

Correct Answers

A:

For an order-cancellation service, schema constraints guide valid selections and runtime validation blocks unsupported operation values, which directly establishes that a selector accepts only supported operation names; the separate requirement that a truncated response is not mistaken for successful completion is handled by a different action.

B:

For an order-cancellation service, reaching an output limit is a stop condition but does not establish task completion, which directly establishes that a truncated response is not mistaken for successful completion; the separate requirement that a selector accepts only supported operation names is handled by a different action.

Incorrect Answers

C:

For an order-cancellation service, a length-limited result may be incomplete or unusable, so this option cannot establish that a truncated response is not mistaken for successful completion; correctly addressing a selector accepts only supported operation names elsewhere does not repair that deficiency.

D:

For an order-cancellation service, free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist, so this option cannot establish that a selector accepts only supported operation names; correctly addressing a truncated response is not mistaken for successful completion elsewhere does not repair that deficiency.

Question 191

Tests for a large-codebase architecture explorer will pass only if a selector accepts only supported operation names and if only one approved write tool is callable in a sensitive stage. Which proposed design directly satisfies both checks?

  1. ask the model to invent a suitable action string; and restrict the stage's allowed tool set and verify permissions in the executor
  2. declare an operation enum in the schema and reject values outside it in the tool handler; and restrict the stage's allowed tool set and verify permissions in the executor
  3. declare an operation enum in the schema and reject values outside it in the tool handler; and let the model select from a broad global list of tools
  4. ask the model to invent a suitable action string; and let the model select from a broad global list of tools

Explanation

Correct Answer

B:

In a large-codebase architecture explorer, schema constraints guide valid selections and runtime validation blocks unsupported operation values; alongside this, capability scoping narrows possible side effects before model selection, satisfying the distinct requirements that a selector accepts only supported operation names and that only one approved write tool is callable in a sensitive stage.

Incorrect Answers

A:

In a large-codebase architecture explorer, capability scoping narrows possible side effects before model selection, but free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist; therefore the separate requirement that a selector accepts only supported operation names would remain unsatisfied.

C:

In a large-codebase architecture explorer, schema constraints guide valid selections and runtime validation blocks unsupported operation values, but excess capabilities create avoidable routing and authorization risk; therefore the separate requirement that only one approved write tool is callable in a sensitive stage would remain unsatisfied.

D:

In a large-codebase architecture explorer, free-form labels can name unimplemented operations, and a prompt is not an enforced allowlist and excess capabilities create avoidable routing and authorization risk; the design would fail both conditions: a selector accepts only supported operation names and only one approved write tool is callable in a sensitive stage.

Question 192

When designing a monorepo feature modernization project, the requirement is not satisfied unless a delegated skill should not fill the caller's active context and only one approved write tool is callable in a sensitive stage. Which implementation addresses the two independent conditions?

  1. load all investigation steps into the same conversation by default; and restrict the stage's allowed tool set and verify permissions in the executor
  2. load all investigation steps into the same conversation by default; and let the model select from a broad global list of tools
  3. configure the skill to run in an isolated forked context where supported; and restrict the stage's allowed tool set and verify permissions in the executor
  4. configure the skill to run in an isolated forked context where supported; and let the model select from a broad global list of tools

Explanation

Correct Answer

C:

In a monorepo feature modernization project, a fork isolates exploratory work and returns a concise result to its caller; alongside this, capability scoping narrows possible side effects before model selection, satisfying the distinct requirements that a delegated skill should not fill the caller's active context and that only one approved write tool is callable in a sensitive stage.

Incorrect Answers

A:

In a monorepo feature modernization project, capability scoping narrows possible side effects before model selection, but the caller's window accumulates unnecessary intermediate details; therefore the separate requirement that a delegated skill should not fill the caller's active context would remain unsatisfied.

B:

In a monorepo feature modernization project, the caller's window accumulates unnecessary intermediate details and excess capabilities create avoidable routing and authorization risk; the design would fail both conditions: a delegated skill should not fill the caller's active context and only one approved write tool is callable in a sensitive stage.

D:

In a monorepo feature modernization project, a fork isolates exploratory work and returns a concise result to its caller, but excess capabilities create avoidable routing and authorization risk; therefore the separate requirement that only one approved write tool is callable in a sensitive stage would remain unsatisfied.

Question 193

The architect for a customer account helpdesk agent needs to ensure that a truncated response is not mistaken for successful completion. What should the team implement?

  1. return tool_result blocks using the original tool_use_id values
  2. execute every tool_use block and return a result with each corresponding ID
  3. interpret every non-tool stop reason as a successful final answer
  4. preserve the paused assistant response and resume the server-tool turn
  5. handle max_tokens as truncation rather than end_turn

Explanation

Correct Answer

E:

For a customer account helpdesk agent, reaching an output limit is a stop condition but does not establish task completion; this directly establishes that a truncated response is not mistaken for successful completion instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although correlation identifiers bind asynchronous or parallel results to the right requests, that only supports the distinct goal that tool responses are associated with the exact invocations that produced them, not the requirement that a truncated response is not mistaken for successful completion in a customer account helpdesk agent.

B:

Although a multi-tool assistant turn can request independent actions and must receive all matching outcomes, that only supports the distinct goal that several requested client tools are returned in one response, not the requirement that a truncated response is not mistaken for successful completion in a customer account helpdesk agent.

C:

In a customer account helpdesk agent, a length-limited result may be incomplete or unusable; as a result, the stated requirement that a truncated response is not mistaken for successful completion would still not be met.

D:

Although pause_turn indicates an internal tool loop pause rather than a user-facing conclusion, that only supports the distinct goal that a paused server-side tool loop can continue without losing work, not the requirement that a truncated response is not mistaken for successful completion in a customer account helpdesk agent.

Question 194

An incident postmortem for a merchant support assistant requires controls so that the model can use a tool result in its next decision and that refund execution is blocked until customer identity is verified. Which paired remedy covers both failure modes?

  1. append the assistant tool-use response and matching user tool_result blocks to history; and enforce a prerequisite gate in application logic before the write tool
  2. put the tool output only in application logs; and ask the assistant in prose to remember verification first
  3. append the assistant tool-use response and matching user tool_result blocks to history; and ask the assistant in prose to remember verification first
  4. put the tool output only in application logs; and enforce a prerequisite gate in application logic before the write tool

Explanation

Correct Answer

A:

In a merchant support assistant, Claude needs the prior request and the execution output in the conversation for the next inference; alongside this, deterministic preconditions protect an irreversible operation even if the model proposes it early, satisfying the distinct requirements that the model can use a tool result in its next decision and that refund execution is blocked until customer identity is verified.

Incorrect Answers

B:

In a merchant support assistant, unseen logs cannot inform the model's next decision and a prompt is advisory and does not technically block an unauthorized tool call; the design would fail both conditions: the model can use a tool result in its next decision and refund execution is blocked until customer identity is verified.

C:

In a merchant support assistant, Claude needs the prior request and the execution output in the conversation for the next inference, but a prompt is advisory and does not technically block an unauthorized tool call; therefore the separate requirement that refund execution is blocked until customer identity is verified would remain unsatisfied.

D:

In a merchant support assistant, deterministic preconditions protect an irreversible operation even if the model proposes it early, but unseen logs cannot inform the model's next decision; therefore the separate requirement that the model can use a tool result in its next decision would remain unsatisfied.

Question 195

In a procurement research assistant, the acceptance criteria require that a required validation step runs before the final response even when the model does not support forced tool choice and that a failed MCP operation is visible as an error to the client. Which paired implementation meets both?

  1. implement only mark the tool result as an error and supply structured failure details; make no corresponding change for the first requirement
  2. enforce the validator in application control flow, using forced tool_choice only with compatible models; and mark the tool result as an error and supply structured failure details
  3. enforce the validator in application control flow, using forced tool_choice only with compatible models; and return a success-shaped value saying the operation probably worked
  4. rely on a prompt asking the model to call the validator; and return a success-shaped value saying the operation probably worked
  5. rely on a prompt asking the model to call the validator; and mark the tool result as an error and supply structured failure details

Explanation

Correct Answer

B:

In a procurement research assistant, application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings; alongside this, explicit error status separates failed execution from valid data content, satisfying the distinct requirements that a required validation step runs before the final response even when the model does not support forced tool choice and that a failed MCP operation is visible as an error to the client.

Incorrect Answers

A:

In a procurement research assistant, explicit error status separates failed execution from valid data content, but the independent mechanism for the other criterion is absent: application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings; as written, the design does not ensure that a required validation step runs before the final response even when the model does not support forced tool choice.

C:

In a procurement research assistant, application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings, but downstream agents can mistake a failure for verified business data; therefore the separate requirement that a failed MCP operation is visible as an error to the client would remain unsatisfied.

D:

In a procurement research assistant, prompt instructions do not guarantee execution of the validator or override model-specific tool-choice restrictions and downstream agents can mistake a failure for verified business data; the design would fail both conditions: a required validation step runs before the final response even when the model does not support forced tool choice and a failed MCP operation is visible as an error to the client.

E:

In a procurement research assistant, explicit error status separates failed execution from valid data content, but prompt instructions do not guarantee execution of the validator or override model-specific tool-choice restrictions; therefore the separate requirement that a required validation step runs before the final response even when the model does not support forced tool choice would remain unsatisfied.

Question 196

Tests for a purchase-order parsing service will pass only if thousands of independent documents can finish without interactive response deadlines and if fast-changing information is checked against its publication date. Which proposed design directly satisfies both checks?

  1. use asynchronous Message Batches processing for the bulk workload; and reuse an old cached claim without its date
  2. make every document a synchronous request inside the user interaction; and reuse an old cached claim without its date
  3. implement only record source timestamps and refresh time-sensitive evidence; make no corresponding change for the first requirement
  4. make every document a synchronous request inside the user interaction; and record source timestamps and refresh time-sensitive evidence
  5. use asynchronous Message Batches processing for the bulk workload; and record source timestamps and refresh time-sensitive evidence

Explanation

Correct Answer

E:

In a purchase-order parsing service, batching suits non-blocking independent requests and can reduce processing cost; alongside this, freshness determines whether an otherwise credible fact applies now, satisfying the distinct requirements that thousands of independent documents can finish without interactive response deadlines and that fast-changing information is checked against its publication date.

Incorrect Answers

A:

In a purchase-order parsing service, batching suits non-blocking independent requests and can reduce processing cost, but stale evidence may no longer describe the current state; therefore the separate requirement that fast-changing information is checked against its publication date would remain unsatisfied.

B:

In a purchase-order parsing service, serial immediate calls add latency where no caller is waiting and stale evidence may no longer describe the current state; the design would fail both conditions: thousands of independent documents can finish without interactive response deadlines and fast-changing information is checked against its publication date.

C:

In a purchase-order parsing service, freshness determines whether an otherwise credible fact applies now, but the independent mechanism for the other criterion is absent: batching suits non-blocking independent requests and can reduce processing cost; as written, the design does not ensure that thousands of independent documents can finish without interactive response deadlines.

D:

In a purchase-order parsing service, freshness determines whether an otherwise credible fact applies now, but serial immediate calls add latency where no caller is waiting; therefore the separate requirement that thousands of independent documents can finish without interactive response deadlines would remain unsatisfied.

Question 197

A readiness review for an unfamiliar monorepo investigation requires that two nested packages follow distinct framework conventions; that an existing file receives a precise localized replacement; and that the model can distinguish two similar business tools. Which THREE actions directly implement those distinct requirements? Choose THREE.

  1. create separate path-specific rule files for each package
  2. write one ambiguous instruction for both packages
  3. use Edit for an exact targeted change
  4. give both tools vague names with identical generic descriptions
  5. overwrite the whole file with a newly generated copy
  6. give each tool a specific purpose and exclusion examples in its description

Explanation

Correct Answers

A:

For an unfamiliar monorepo investigation, scoped conventions avoid contradictory patterns between codebases sharing a monorepo, which directly establishes that two nested packages follow distinct framework conventions; the separate requirement that an existing file receives a precise localized replacement is handled by a different action.

C:

For an unfamiliar monorepo investigation, surgical edits preserve unrelated lines and provide reviewable diffs, which directly establishes that an existing file receives a precise localized replacement; the separate requirement that the model can distinguish two similar business tools is handled by a different action.

F:

For an unfamiliar monorepo investigation, discriminative descriptions reduce wrong routing when operations sound alike, which directly establishes that the model can distinguish two similar business tools; the separate requirement that two nested packages follow distinct framework conventions is handled by a different action.

Incorrect Answers

B:

For an unfamiliar monorepo investigation, the model must guess which framework convention applies, so this option cannot establish that two nested packages follow distinct framework conventions; correctly addressing an existing file receives a precise localized replacement elsewhere does not repair that deficiency.

D:

For an unfamiliar monorepo investigation, a model cannot reliably select on boundaries that the interface never explains, so this option cannot establish that the model can distinguish two similar business tools; correctly addressing two nested packages follow distinct framework conventions elsewhere does not repair that deficiency.

E:

For an unfamiliar monorepo investigation, full replacement risks losing unrelated code and formatting, so this option cannot establish that an existing file receives a precise localized replacement; correctly addressing the model can distinguish two similar business tools elsewhere does not repair that deficiency.

Question 198

For a repository search copilot, a reviewer identifies two independent obligations: several requested client tools are returned in one response and the assistant locates files containing a particular symbol or string. Which proposal should be approved?

  1. execute only the first returned tool call; and scan only filenames with Glob
  2. execute every tool_use block and return a result with each corresponding ID; and use Grep to search file contents
  3. execute every tool_use block and return a result with each corresponding ID; and scan only filenames with Glob
  4. execute only the first returned tool call; and use Grep to search file contents

Explanation

Correct Answer

B:

In a repository search copilot, a multi-tool assistant turn can request independent actions and must receive all matching outcomes; alongside this, text search locates occurrences efficiently before focused reading, satisfying the distinct requirements that several requested client tools are returned in one response and that the assistant locates files containing a particular symbol or string.

Incorrect Answers

A:

In a repository search copilot, the unanswered tool uses remain unresolved and later reasoning loses evidence and path matching does not inspect symbol occurrences inside files; the design would fail both conditions: several requested client tools are returned in one response and the assistant locates files containing a particular symbol or string.

C:

In a repository search copilot, a multi-tool assistant turn can request independent actions and must receive all matching outcomes, but path matching does not inspect symbol occurrences inside files; therefore the separate requirement that the assistant locates files containing a particular symbol or string would remain unsatisfied.

D:

In a repository search copilot, text search locates occurrences efficiently before focused reading, but the unanswered tool uses remain unresolved and later reasoning loses evidence; therefore the separate requirement that several requested client tools are returned in one response would remain unsatisfied.

Question 199

In a technical review of a typed API generator project, the architect must address the following constraints together: an existing file receives a precise localized replacement; a required validation step runs before the final response even when the model does not support forced tool choice. Which change set is most defensible?

  1. use Edit for an exact targeted change; and rely on a prompt asking the model to call the validator
  2. use Edit for an exact targeted change; and enforce the validator in application control flow, using forced tool_choice only with compatible models
  3. overwrite the whole file with a newly generated copy; and enforce the validator in application control flow, using forced tool_choice only with compatible models
  4. overwrite the whole file with a newly generated copy; and rely on a prompt asking the model to call the validator

Explanation

Correct Answer

B:

In a typed API generator project, surgical edits preserve unrelated lines and provide reviewable diffs; alongside this, application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings, satisfying the distinct requirements that an existing file receives a precise localized replacement and that a required validation step runs before the final response even when the model does not support forced tool choice.

Incorrect Answers

A:

In a typed API generator project, surgical edits preserve unrelated lines and provide reviewable diffs, but prompt instructions do not guarantee execution of the validator or override model-specific tool-choice restrictions; therefore the separate requirement that a required validation step runs before the final response even when the model does not support forced tool choice would remain unsatisfied.

C:

In a typed API generator project, application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings, but full replacement risks losing unrelated code and formatting; therefore the separate requirement that an existing file receives a precise localized replacement would remain unsatisfied.

D:

In a typed API generator project, full replacement risks losing unrelated code and formatting and prompt instructions do not guarantee execution of the validator or override model-specific tool-choice restrictions; the design would fail both conditions: an existing file receives a precise localized replacement and a required validation step runs before the final response even when the model does not support forced tool choice.

Question 200

Tests for a continuous integration repair assistant will pass only if two nested packages follow distinct framework conventions and if a shared skill can take a supplied target name or file path. Which proposed design directly satisfies both checks?

  1. create separate path-specific rule files for each package; and define how the skill accepts and uses invocation arguments
  2. write one ambiguous instruction for both packages; and define how the skill accepts and uses invocation arguments
  3. write one ambiguous instruction for both packages; and copy a separate static instruction file for every target path
  4. create separate path-specific rule files for each package; and copy a separate static instruction file for every target path

Explanation

Correct Answer

A:

In a continuous integration repair assistant, scoped conventions avoid contradictory patterns between codebases sharing a monorepo; alongside this, parameterized workflows apply one reviewed procedure to different resources without hardcoding targets, satisfying the distinct requirements that two nested packages follow distinct framework conventions and that a shared skill can take a supplied target name or file path.

Incorrect Answers

B:

In a continuous integration repair assistant, parameterized workflows apply one reviewed procedure to different resources without hardcoding targets, but the model must guess which framework convention applies; therefore the separate requirement that two nested packages follow distinct framework conventions would remain unsatisfied.

C:

In a continuous integration repair assistant, the model must guess which framework convention applies and duplicated procedures are costly to maintain and can diverge; the design would fail both conditions: two nested packages follow distinct framework conventions and a shared skill can take a supplied target name or file path.

D:

In a continuous integration repair assistant, scoped conventions avoid contradictory patterns between codebases sharing a monorepo, but duplicated procedures are costly to maintain and can diverge; therefore the separate requirement that a shared skill can take a supplied target name or file path would remain unsatisfied.

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