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

Question 400

An audit of an automated CI review service asks how to make sure that CI failures provide actionable evidence to maintainers. Which implementation should be selected?

  1. run Claude Code in non-interactive print mode with -p
  2. scope runner credentials, worktree access, and allowed tools to its task
  3. persist structured errors, relevant logs, and a bounded diagnostic summary
  4. discard the runner logs and keep only the assistant's final sentence

Explanation

Correct Answer

C:

For an automated CI review service, stable artifacts help maintainers reproduce the problem without rerunning a chat; this directly establishes that CI failures provide actionable evidence to maintainers instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although headless invocation permits scripted automation and exits after the requested task, that only supports the distinct goal that a CI job invokes Claude without a terminal conversation, not the requirement that CI failures provide actionable evidence to maintainers in an automated CI review service.

B:

Although CI identity and tool permissions control real write capabilities independent of model instructions, that only supports the distinct goal that a pull-request bot runs with minimum necessary authority, not the requirement that CI failures provide actionable evidence to maintainers in an automated CI review service.

D:

In an automated CI review service, the missing trace impedes diagnosis of command or infrastructure failures; as a result, the stated requirement that CI failures provide actionable evidence to maintainers would still not be met.

Question 401

For a document field validation service, a reviewer identifies two independent obligations: sensitive tool calls are denied before they reach an executor and a truncated response is not mistaken for successful completion. Which proposal should be approved?

  1. write a stronger instruction in the system prompt; and handle max_tokens as truncation rather than end_turn
  2. write a stronger instruction in the system prompt; and interpret every non-tool stop reason as a successful final answer
  3. register a PreToolUse hook that checks the operation against policy; and handle max_tokens as truncation rather than end_turn
  4. register a PreToolUse hook that checks the operation against policy; and interpret every non-tool stop reason as a successful final answer
  5. implement only handle max_tokens as truncation rather than end_turn; make no corresponding change for the first requirement

Explanation

Correct Answer

C:

In a document field validation service, pre-execution interception can reject a disallowed call rather than relying on post-hoc advice; alongside this, reaching an output limit is a stop condition but does not establish task completion, satisfying the distinct requirements that sensitive tool calls are denied before they reach an executor and that a truncated response is not mistaken for successful completion.

Incorrect Answers

A:

In a document field validation service, reaching an output limit is a stop condition but does not establish task completion, but an instruction alone does not provide deterministic execution-time authorization; therefore the separate requirement that sensitive tool calls are denied before they reach an executor would remain unsatisfied.

B:

In a document field validation service, an instruction alone does not provide deterministic execution-time authorization and a length-limited result may be incomplete or unusable; the design would fail both conditions: sensitive tool calls are denied before they reach an executor and a truncated response is not mistaken for successful completion.

D:

In a document field validation service, pre-execution interception can reject a disallowed call rather than relying on post-hoc advice, but a length-limited result may be incomplete or unusable; therefore the separate requirement that a truncated response is not mistaken for successful completion would remain unsatisfied.

E:

In a document field validation service, reaching an output limit is a stop condition but does not establish task completion, but the independent mechanism for the other criterion is absent: pre-execution interception can reject a disallowed call rather than relying on post-hoc advice; as written, the design does not ensure that sensitive tool calls are denied before they reach an executor.

Question 402

An audit of a developer codebase exploration assistant identifies two unmet requirements: regressions introduced during refinement are detected and fixed and long project guidance is divided into maintainable source files. Select TWO actions that remedy those particular deficiencies.

  1. use CLAUDE.md imports to organize referenced instructions
  2. duplicate full instruction paragraphs in every directory
  3. restore or revise the problematic change and retest affected paths
  4. keep layering patches without checking the last stable behavior

Explanation

Correct Answers

A:

For a developer codebase exploration assistant, modular imports keep a short entry point while preserving reviewed details in separate files, which directly establishes that long project guidance is divided into maintainable source files; the separate requirement that regressions introduced during refinement are detected and fixed is handled by a different action.

C:

For a developer codebase exploration assistant, iteration includes detecting regressions and returning to a passing state, which directly establishes that regressions introduced during refinement are detected and fixed; the separate requirement that long project guidance is divided into maintainable source files is handled by a different action.

Incorrect Answers

B:

For a developer codebase exploration assistant, copying guidance encourages drift when policies change, so this option cannot establish that long project guidance is divided into maintainable source files; correctly addressing regressions introduced during refinement are detected and fixed elsewhere does not repair that deficiency.

D:

For a developer codebase exploration assistant, cumulative changes can bury the source of failure, so this option cannot establish that regressions introduced during refinement are detected and fixed; correctly addressing long project guidance is divided into maintainable source files elsewhere does not repair that deficiency.

Question 403

Before expanding a release-triage developer agent, the owner must demonstrate that several requested client tools are returned in one response, while also demonstrating that specialized agents work with only relevant permissions. Which design provides both controls?

  1. execute every tool_use block and return a result with each corresponding ID; and give every subagent the coordinator's complete tool inventory
  2. execute every tool_use block and return a result with each corresponding ID; and define each subagent role and expose the minimum matching tools
  3. execute only the first returned tool call; and give every subagent the coordinator's complete tool inventory
  4. execute only the first returned tool call; and define each subagent role and expose the minimum matching tools

Explanation

Correct Answer

B:

In a release-triage developer agent, a multi-tool assistant turn can request independent actions and must receive all matching outcomes; alongside this, tool scoping shrinks both decision confusion and the blast radius of delegated actions, satisfying the distinct requirements that several requested client tools are returned in one response and that specialized agents work with only relevant permissions.

Incorrect Answers

A:

In a release-triage developer agent, a multi-tool assistant turn can request independent actions and must receive all matching outcomes, but unneeded write or network tools expand risk without improving the specialist task; therefore the separate requirement that specialized agents work with only relevant permissions would remain unsatisfied.

C:

In a release-triage developer agent, the unanswered tool uses remain unresolved and later reasoning loses evidence and unneeded write or network tools expand risk without improving the specialist task; the design would fail both conditions: several requested client tools are returned in one response and specialized agents work with only relevant permissions.

D:

In a release-triage developer agent, tool scoping shrinks both decision confusion and the blast radius of delegated actions, 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 404

The release gate for a contract clause extraction workflow requires that schema-valid output is also checked against source evidence; it also requires that the coordinator can identify which subagent produced a broken artifact. Which TWO actions meet the specified checks? Choose TWO.

  1. validate semantic constraints and provenance in application logic
  2. propagate task IDs, error codes, and correlation references
  3. assume a schema-conforming response is factually correct
  4. replace all nested errors with a generic coordinator failure

Explanation

Correct Answers

A:

For a contract clause extraction workflow, JSON shape does not prove that an extracted claim is supported by the document, which directly establishes that schema-valid output is also checked against source evidence; the separate requirement that the coordinator can identify which subagent produced a broken artifact is handled by a different action.

B:

For a contract clause extraction workflow, tracing execution lineage helps route the incident to the right failing component, which directly establishes that the coordinator can identify which subagent produced a broken artifact; the separate requirement that schema-valid output is also checked against source evidence is handled by a different action.

Incorrect Answers

C:

For a contract clause extraction workflow, syntactic conformance cannot guarantee source-level truth, so this option cannot establish that schema-valid output is also checked against source evidence; correctly addressing the coordinator can identify which subagent produced a broken artifact elsewhere does not repair that deficiency.

D:

For a contract clause extraction workflow, the original failing operation becomes opaque, so this option cannot establish that the coordinator can identify which subagent produced a broken artifact; correctly addressing schema-valid output is also checked against source evidence elsewhere does not repair that deficiency.

Question 405

In a technical review of a code policy conformance job, the architect must address the following constraints together: the report is not drafted before evidence is checked; sensitive tool calls are denied before they reach an executor. Which change set is most defensible?

  1. start drafting at the same time as the source search and assume success; and write a stronger instruction in the system prompt
  2. place evidence validation before the drafting stage; and write a stronger instruction in the system prompt
  3. place evidence validation before the drafting stage; and register a PreToolUse hook that checks the operation against policy
  4. start drafting at the same time as the source search and assume success; and register a PreToolUse hook that checks the operation against policy

Explanation

Correct Answer

C:

In a code policy conformance job, a dependent stage must receive validated inputs to avoid propagating unsupported conclusions; alongside this, pre-execution interception can reject a disallowed call rather than relying on post-hoc advice, satisfying the distinct requirements that the report is not drafted before evidence is checked and that sensitive tool calls are denied before they reach an executor.

Incorrect Answers

A:

In a code policy conformance job, the writer may treat unverified or absent evidence as real and an instruction alone does not provide deterministic execution-time authorization; the design would fail both conditions: the report is not drafted before evidence is checked and sensitive tool calls are denied before they reach an executor.

B:

In a code policy conformance job, a dependent stage must receive validated inputs to avoid propagating unsupported conclusions, but an instruction alone does not provide deterministic execution-time authorization; therefore the separate requirement that sensitive tool calls are denied before they reach an executor would remain unsatisfied.

D:

In a code policy conformance job, pre-execution interception can reject a disallowed call rather than relying on post-hoc advice, but the writer may treat unverified or absent evidence as real; therefore the separate requirement that the report is not drafted before evidence is checked would remain unsatisfied.

Question 406

For a claims form processing assistant, acceptance depends on demonstrating that a failed MCP operation is visible as an error to the client. Which approach is the strongest fit?

  1. return a non-retryable validation error with the field and expected constraint
  2. mark the tool result as an error and supply structured failure details
  3. include a retryable classification and bounded retry advice
  4. return a success-shaped value saying the operation probably worked

Explanation

Correct Answer

B:

For a claims form processing assistant, explicit error status separates failed execution from valid data content; this directly establishes that a failed MCP operation is visible as an error to the client instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although field-specific feedback lets the caller fix the input before resubmission, that only supports the distinct goal that invalid parameters lead to a clear correction rather than a blind retry, not the requirement that a failed MCP operation is visible as an error to the client in a claims form processing assistant.

C:

Although typed transient failures allow backoff without treating permanent errors the same way, that only supports the distinct goal that temporary service faults can be retried selectively, not the requirement that a failed MCP operation is visible as an error to the client in a claims form processing assistant.

D:

In a claims form processing assistant, downstream agents can mistake a failure for verified business data; as a result, the stated requirement that a failed MCP operation is visible as an error to the client would still not be met.

Question 407

An incident postmortem for a returns-policy assistant requires controls so that fast-changing information is checked against its publication date and that a payment-changing action obtains explicit user authorization. Which paired remedy covers both failure modes?

  1. record source timestamps and refresh time-sensitive evidence; and treat a request for information as permission to mutate the account
  2. reuse an old cached claim without its date; and confirm the intended action and scope before invoking the write
  3. record source timestamps and refresh time-sensitive evidence; and confirm the intended action and scope before invoking the write
  4. reuse an old cached claim without its date; and treat a request for information as permission to mutate the account

Explanation

Correct Answer

C:

In a returns-policy assistant, freshness determines whether an otherwise credible fact applies now; alongside this, consent is specific to the side effect and cannot be inferred from a general inquiry, satisfying the distinct requirements that fast-changing information is checked against its publication date and that a payment-changing action obtains explicit user authorization.

Incorrect Answers

A:

In a returns-policy assistant, freshness determines whether an otherwise credible fact applies now, but asking a question does not approve a financial change; therefore the separate requirement that a payment-changing action obtains explicit user authorization would remain unsatisfied.

B:

In a returns-policy assistant, consent is specific to the side effect and cannot be inferred from a general inquiry, 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.

D:

In a returns-policy assistant, stale evidence may no longer describe the current state and asking a question does not approve a financial change; the design would fail both conditions: fast-changing information is checked against its publication date and a payment-changing action obtains explicit user authorization.

Question 408

The release checklist for a static analysis automation explicitly checks that only a nested service uses specialized implementation rules; it also checks that the implementation plan receives stakeholder sign-off. What coordinated solution meets the checklist?

  1. put all service-only details in the repository root instruction file; and treat the agent's internally generated plan as implicit approval
  2. put all service-only details in the repository root instruction file; and present ordered changes, risks, and verification steps before switching to execution
  3. place a dedicated CLAUDE.md in the relevant directory; and treat the agent's internally generated plan as implicit approval
  4. place a dedicated CLAUDE.md in the relevant directory; and present ordered changes, risks, and verification steps before switching to execution

Explanation

Correct Answer

D:

In a static analysis automation, directory-specific context can refine instructions for work under that subtree; alongside this, an explicit review point aligns the agent's work with the authorized scope, satisfying the distinct requirements that only a nested service uses specialized implementation rules and that the implementation plan receives stakeholder sign-off.

Incorrect Answers

A:

In a static analysis automation, globalizing narrow rules adds irrelevant instructions to unrelated work and the system cannot infer external authorization from its own reasoning; the design would fail both conditions: only a nested service uses specialized implementation rules and the implementation plan receives stakeholder sign-off.

B:

In a static analysis automation, an explicit review point aligns the agent's work with the authorized scope, but globalizing narrow rules adds irrelevant instructions to unrelated work; therefore the separate requirement that only a nested service uses specialized implementation rules would remain unsatisfied.

C:

In a static analysis automation, directory-specific context can refine instructions for work under that subtree, but the system cannot infer external authorization from its own reasoning; therefore the separate requirement that the implementation plan receives stakeholder sign-off would remain unsatisfied.

Question 409

An incident postmortem for a service refactoring initiative requires controls so that delegated investigations stay within bounded scope and that a missing MCP capability is diagnosed before changing prompts. Which paired remedy covers both failure modes?

  1. specify the question, allowed sources, expected output, and stopping criterion; and verify server connection, transport, and exposed tool availability
  2. ask every subagent to investigate everything it can find; and verify server connection, transport, and exposed tool availability
  3. ask every subagent to investigate everything it can find; and increase the system prompt length to compensate for disconnected tools
  4. specify the question, allowed sources, expected output, and stopping criterion; and increase the system prompt length to compensate for disconnected tools

Explanation

Correct Answer

A:

In a service refactoring initiative, a task contract prevents specialist exploration from swallowing the coordinator's larger goal; alongside this, tool discovery depends on a live configured integration, not just the prompt wording, satisfying the distinct requirements that delegated investigations stay within bounded scope and that a missing MCP capability is diagnosed before changing prompts.

Incorrect Answers

B:

In a service refactoring initiative, tool discovery depends on a live configured integration, not just the prompt wording, but unbounded exploration dilutes signal and inflates context and latency; therefore the separate requirement that delegated investigations stay within bounded scope would remain unsatisfied.

C:

In a service refactoring initiative, unbounded exploration dilutes signal and inflates context and latency and a model cannot call a capability absent from its available tool registry; the design would fail both conditions: delegated investigations stay within bounded scope and a missing MCP capability is diagnosed before changing prompts.

D:

In a service refactoring initiative, a task contract prevents specialist exploration from swallowing the coordinator's larger goal, but a model cannot call a capability absent from its available tool registry; therefore the separate requirement that a missing MCP capability is diagnosed before changing prompts would remain unsatisfied.

Question 410

A team operating a customer refund workflow wants to establish two separate behaviors: every high-impact tool invocation produces an audit event; in addition, a new agent gets only durable context from a completed job. Which plan implements both?

  1. record the tool name, permitted inputs, outcome, and task identifier in a hook; and initialize a fresh session with a verified structured summary
  2. infer tool activity from the final natural-language answer; and initialize a fresh session with a verified structured summary
  3. record the tool name, permitted inputs, outcome, and task identifier in a hook; and paste a full historical transcript into every new session
  4. infer tool activity from the final natural-language answer; and paste a full historical transcript into every new session

Explanation

Correct Answer

A:

In a customer refund workflow, runtime instrumentation observes actual proposed or completed tool activity; alongside this, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, satisfying the distinct requirements that every high-impact tool invocation produces an audit event and that a new agent gets only durable context from a completed job.

Incorrect Answers

B:

In a customer refund workflow, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, but a summary can omit failed calls or delegated actions; therefore the separate requirement that every high-impact tool invocation produces an audit event would remain unsatisfied.

C:

In a customer refund workflow, runtime instrumentation observes actual proposed or completed tool activity, but irrelevant turns can consume context and revive outdated assumptions; therefore the separate requirement that a new agent gets only durable context from a completed job would remain unsatisfied.

D:

In a customer refund workflow, a summary can omit failed calls or delegated actions and irrelevant turns can consume context and revive outdated assumptions; the design would fail both conditions: every high-impact tool invocation produces an audit event and a new agent gets only durable context from a completed job.

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