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

Question 80

The release checklist for a pull-request review pipeline explicitly checks that a team compares two candidate patches against the same baseline; it also checks that conflicting guidance from different files is detected before rollout. What coordinated solution meets the checklist?

  1. choose whichever patch has the more persuasive natural-language summary; and assume the model will infer which contradictory rule to follow
  2. evaluate alternatives using the same tests and scoped diffs; and assume the model will infer which contradictory rule to follow
  3. evaluate alternatives using the same tests and scoped diffs; and audit overlapping CLAUDE.md files and resolve instruction contradictions
  4. choose whichever patch has the more persuasive natural-language summary; and audit overlapping CLAUDE.md files and resolve instruction contradictions

Explanation

Correct Answer

C:

In a pull-request review pipeline, consistent acceptance evidence reveals which candidate improves the relevant behavior; alongside this, clear ownership and scope prevent two directions from competing in the same coding task, satisfying the distinct requirements that a team compares two candidate patches against the same baseline and that conflicting guidance from different files is detected before rollout.

Incorrect Answers

A:

In a pull-request review pipeline, rhetorical fluency does not establish code correctness and unresolved conflicts create inconsistent output across directories; the design would fail both conditions: a team compares two candidate patches against the same baseline and conflicting guidance from different files is detected before rollout.

B:

In a pull-request review pipeline, consistent acceptance evidence reveals which candidate improves the relevant behavior, but unresolved conflicts create inconsistent output across directories; therefore the separate requirement that conflicting guidance from different files is detected before rollout would remain unsatisfied.

D:

In a pull-request review pipeline, clear ownership and scope prevent two directions from competing in the same coding task, but rhetorical fluency does not establish code correctness; therefore the separate requirement that a team compares two candidate patches against the same baseline would remain unsatisfied.

Question 81

An architecture review of a procurement research assistant finds two missing guarantees: the reviewer does not simply echo the generator's confidence; a classification uses a limited approved category set. What two-part change closes both gaps?

  1. provide the generator's score as the sole review criterion; and allow a free-form category for each case
  2. give the reviewer the source and rubric, not only the draft's self-rating; and allow a free-form category for each case
  3. provide the generator's score as the sole review criterion; and define precise output labels and mapping rules
  4. give the reviewer the source and rubric, not only the draft's self-rating; and define precise output labels and mapping rules

Explanation

Correct Answer

D:

In a procurement research assistant, independent evidence lets a critic challenge unsupported assertions; alongside this, controlled categories reduce schema drift and make downstream analytics comparable, satisfying the distinct requirements that the reviewer does not simply echo the generator's confidence and that a classification uses a limited approved category set.

Incorrect Answers

A:

In a procurement research assistant, anchoring on a self-assigned grade hides actual defects and unbounded labels fragment the intended taxonomy; the design would fail both conditions: the reviewer does not simply echo the generator's confidence and a classification uses a limited approved category set.

B:

In a procurement research assistant, independent evidence lets a critic challenge unsupported assertions, but unbounded labels fragment the intended taxonomy; therefore the separate requirement that a classification uses a limited approved category set would remain unsatisfied.

C:

In a procurement research assistant, controlled categories reduce schema drift and make downstream analytics comparable, but anchoring on a self-assigned grade hides actual defects; therefore the separate requirement that the reviewer does not simply echo the generator's confidence would remain unsatisfied.

Question 82

In a nightly code quality job, the design must ensure that conflicting guidance from different files is detected before rollout and that a small approved typo fix is completed without excessive planning. Choose TWO independent changes that directly meet these two requirements.

  1. assume the model will infer which contradictory rule to follow
  2. launch a multi-stage planning effort for a single known line
  3. use direct execution for the limited reviewed edit
  4. audit overlapping CLAUDE.md files and resolve instruction contradictions

Explanation

Correct Answers

C:

For a nightly code quality job, a bounded low-risk change does not require a long exploratory workflow, which directly establishes that a small approved typo fix is completed without excessive planning; the separate requirement that conflicting guidance from different files is detected before rollout is handled by a different action.

D:

For a nightly code quality job, clear ownership and scope prevent two directions from competing in the same coding task, which directly establishes that conflicting guidance from different files is detected before rollout; the separate requirement that a small approved typo fix is completed without excessive planning is handled by a different action.

Incorrect Answers

A:

For a nightly code quality job, unresolved conflicts create inconsistent output across directories, so this option cannot establish that conflicting guidance from different files is detected before rollout; correctly addressing a small approved typo fix is completed without excessive planning elsewhere does not repair that deficiency.

B:

For a nightly code quality job, extra ceremony adds latency without materially lowering risk, so this option cannot establish that a small approved typo fix is completed without excessive planning; correctly addressing conflicting guidance from different files is detected before rollout elsewhere does not repair that deficiency.

Question 83

The release checklist for a claims form processing assistant explicitly checks that a partially successful multi-agent job reports its limitations; it also checks that conflicting model assessments of a disputed claim are reconciled against evidence. What coordinated solution meets the checklist?

  1. aggregate per-agent success and incomplete-state metadata; and resolve the dispute against cited source evidence rather than majority vote
  2. mark the whole request successful when any one branch returns data; and select whichever answer appears in the most generated responses
  3. mark the whole request successful when any one branch returns data; and resolve the dispute against cited source evidence rather than majority vote
  4. aggregate per-agent success and incomplete-state metadata; and select whichever answer appears in the most generated responses

Explanation

Correct Answer

A:

In a claims form processing assistant, partial status lets the coordinator qualify conclusions and retry missing branches; alongside this, independent verification distinguishes a well-grounded minority view from shared guessing, satisfying the distinct requirements that a partially successful multi-agent job reports its limitations and that conflicting model assessments of a disputed claim are reconciled against evidence.

Incorrect Answers

B:

In a claims form processing assistant, some required evidence may still be missing and agreement among models is not a substitute for factual grounding; the design would fail both conditions: a partially successful multi-agent job reports its limitations and conflicting model assessments of a disputed claim are reconciled against evidence.

C:

In a claims form processing assistant, independent verification distinguishes a well-grounded minority view from shared guessing, but some required evidence may still be missing; therefore the separate requirement that a partially successful multi-agent job reports its limitations would remain unsatisfied.

D:

In a claims form processing assistant, partial status lets the coordinator qualify conclusions and retry missing branches, but agreement among models is not a substitute for factual grounding; therefore the separate requirement that conflicting model assessments of a disputed claim are reconciled against evidence would remain unsatisfied.

Question 84

An audit of a source code audit helper identifies two unmet requirements: only a nested service uses specialized implementation rules and API conventions apply only to source files under an API directory. Select TWO actions that remedy those particular deficiencies.

  1. put API-specific formatting rules in always-on project guidance
  2. put all service-only details in the repository root instruction file
  3. add a .claude/rules file with paths matching the API subtree
  4. place a dedicated CLAUDE.md in the relevant directory

Explanation

Correct Answers

C:

For a source code audit helper, path-scoped rules load when the target context matches, keeping unrelated tasks clean, which directly establishes that API conventions apply only to source files under an API directory; the separate requirement that only a nested service uses specialized implementation rules is handled by a different action.

D:

For a source code audit helper, directory-specific context can refine instructions for work under that subtree, which directly establishes that only a nested service uses specialized implementation rules; the separate requirement that API conventions apply only to source files under an API directory is handled by a different action.

Incorrect Answers

A:

For a source code audit helper, frontend and documentation tasks then receive irrelevant instructions, so this option cannot establish that API conventions apply only to source files under an API directory; correctly addressing only a nested service uses specialized implementation rules elsewhere does not repair that deficiency.

B:

For a source code audit helper, globalizing narrow rules adds irrelevant instructions to unrelated work, so this option cannot establish that only a nested service uses specialized implementation rules; correctly addressing API conventions apply only to source files under an API directory elsewhere does not repair that deficiency.

Question 85

When designing an after-sales issue resolver, the requirement is not satisfied unless important workflow state survives context compression or process restarts and every high-impact tool invocation produces an audit event. Which implementation addresses the two independent conditions?

  1. depend on the model remembering a prior value forever; and infer tool activity from the final natural-language answer
  2. depend on the model remembering a prior value forever; and record the tool name, permitted inputs, outcome, and task identifier in a hook
  3. persist authoritative task facts and artifact IDs outside ephemeral conversation text; and record the tool name, permitted inputs, outcome, and task identifier in a hook
  4. persist authoritative task facts and artifact IDs outside ephemeral conversation text; and infer tool activity from the final natural-language answer

Explanation

Correct Answer

C:

In an after-sales issue resolver, external durable state can be reloaded and checked when the session window changes; alongside this, runtime instrumentation observes actual proposed or completed tool activity, satisfying the distinct requirements that important workflow state survives context compression or process restarts and that every high-impact tool invocation produces an audit event.

Incorrect Answers

A:

In an after-sales issue resolver, context limits and summarization can lose exact identifiers and a summary can omit failed calls or delegated actions; the design would fail both conditions: important workflow state survives context compression or process restarts and every high-impact tool invocation produces an audit event.

B:

In an after-sales issue resolver, runtime instrumentation observes actual proposed or completed tool activity, but context limits and summarization can lose exact identifiers; therefore the separate requirement that important workflow state survives context compression or process restarts would remain unsatisfied.

D:

In an after-sales issue resolver, external durable state can be reloaded and checked when the session window changes, 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.

Question 86

An audit of a shared-library improvement effort asks how to make sure that a downstream subagent acts on concrete upstream results. Which implementation should be selected?

  1. pass the preceding artifact identifier and a focused summary to the next agent
  2. pass the necessary task context and references explicitly at invocation
  3. spawn independent specialists in the same delegation stage
  4. send only a generic instruction to continue the work

Explanation

Correct Answer

A:

For a shared-library improvement effort, explicit handoff preserves the specific result that the dependent stage must process; this directly establishes that a downstream subagent acts on concrete upstream results instead of relying on an unrelated workflow control.

Incorrect Answers

B:

Although subagents do not automatically inherit the coordinator's entire conversational history, that only supports the distinct goal that a delegated agent receives the background it needs to act, not the requirement that a downstream subagent acts on concrete upstream results in a shared-library improvement effort.

C:

Although concurrent subagents can examine non-overlapping modules before the coordinator merges their reports, that only supports the distinct goal that separate code modules can be inspected in parallel, not the requirement that a downstream subagent acts on concrete upstream results in a shared-library improvement effort.

D:

In a shared-library improvement effort, the later agent cannot know which evidence or state was produced previously; as a result, the stated requirement that a downstream subagent acts on concrete upstream results would still not be met.

Question 87

Production readiness for a shipping-exception helpdesk depends on ensuring that client-side tool requests trigger another model turn after execution and that a conversational task does not invoke tools needlessly. Select the most appropriate combined approach.

  1. branch on stop_reason tool_use and execute returned tool_use blocks; and use automatic tool choice when a call is optional
  2. implement only branch on stop_reason tool_use and execute returned tool_use blocks; make no corresponding change for the second requirement
  3. end the loop whenever assistant text appears; and use automatic tool choice when a call is optional
  4. branch on stop_reason tool_use and execute returned tool_use blocks; and force a tool on every message regardless of intent
  5. end the loop whenever assistant text appears; and force a tool on every message regardless of intent

Explanation

Correct Answer

A:

In a shipping-exception helpdesk, the response explicitly signals pending client execution and the loop must provide results before another model decision; alongside this, auto allows the model to answer directly when no external side effect or fresh data is needed, satisfying the distinct requirements that client-side tool requests trigger another model turn after execution and that a conversational task does not invoke tools needlessly.

Incorrect Answers

B:

In a shipping-exception helpdesk, the response explicitly signals pending client execution and the loop must provide results before another model decision, but the independent mechanism for the other criterion is absent: auto allows the model to answer directly when no external side effect or fresh data is needed; as written, the design does not ensure that a conversational task does not invoke tools needlessly.

C:

In a shipping-exception helpdesk, auto allows the model to answer directly when no external side effect or fresh data is needed, 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.

D:

In a shipping-exception helpdesk, the response explicitly signals pending client execution and the loop must provide results before another model decision, but mandatory calls add latency and can invoke irrelevant operations; therefore the separate requirement that a conversational task does not invoke tools needlessly would remain unsatisfied.

E:

In a shipping-exception helpdesk, text may accompany a tool request and is not the completion signal and mandatory calls add latency and can invoke irrelevant operations; the design would fail both conditions: client-side tool requests trigger another model turn after execution and a conversational task does not invoke tools needlessly.

Question 88

An audit of a source-navigation tool for new hires identifies two unmet requirements: only one approved write tool is callable in a sensitive stage and the repository assistant discovers filenames matching a pattern. Select TWO actions that remedy those particular deficiencies.

  1. restrict the stage's allowed tool set and verify permissions in the executor
  2. use Glob to locate candidate paths
  3. let the model select from a broad global list of tools
  4. search entire file contents with Grep to find paths by naming pattern

Explanation

Correct Answers

A:

For a source-navigation tool for new hires, capability scoping narrows possible side effects before model selection, which directly establishes that only one approved write tool is callable in a sensitive stage; the separate requirement that the repository assistant discovers filenames matching a pattern is handled by a different action.

B:

For a source-navigation tool for new hires, path globbing finds files by names and directory structure before content inspection, which directly establishes that the repository assistant discovers filenames matching a pattern; the separate requirement that only one approved write tool is callable in a sensitive stage is handled by a different action.

Incorrect Answers

C:

For a source-navigation tool for new hires, excess capabilities create avoidable routing and authorization risk, so this option cannot establish that only one approved write tool is callable in a sensitive stage; correctly addressing the repository assistant discovers filenames matching a pattern elsewhere does not repair that deficiency.

D:

For a source-navigation tool for new hires, content search answers a different question and may miss empty files, so this option cannot establish that the repository assistant discovers filenames matching a pattern; correctly addressing only one approved write tool is callable in a sensitive stage elsewhere does not repair that deficiency.

Question 89

The release checklist for an account recovery support process explicitly checks that context reduction does not erase unresolved obligations; it also checks that the system distinguishes acceptable and unacceptable edge cases. What coordinated solution meets the checklist?

  1. track pending approvals and required next steps in durable task state; and specify inclusion criteria and explicit exclusion conditions
  2. track pending approvals and required next steps in durable task state; and provide only a broad topic label as the classification rule
  3. assume the agent will recall every open action from memory; and specify inclusion criteria and explicit exclusion conditions
  4. assume the agent will recall every open action from memory; and provide only a broad topic label as the classification rule

Explanation

Correct Answer

A:

In an account recovery support process, persisted obligations survive when natural-language history is shortened; alongside this, negative boundaries teach the model when a near-match must not trigger, satisfying the distinct requirements that context reduction does not erase unresolved obligations and that the system distinguishes acceptable and unacceptable edge cases.

Incorrect Answers

B:

In an account recovery support process, persisted obligations survive when natural-language history is shortened, but generic labels leave ambiguous boundary cases undefined; therefore the separate requirement that the system distinguishes acceptable and unacceptable edge cases would remain unsatisfied.

C:

In an account recovery support process, negative boundaries teach the model when a near-match must not trigger, 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 an account recovery support process, window truncation can drop an outstanding approval or escalation and generic labels leave ambiguous boundary cases undefined; the design would fail both conditions: context reduction does not erase unresolved obligations and the system distinguishes acceptable and unacceptable edge cases.

Question 90

For a compliance interpretation research team, a reviewer identifies two independent obligations: resuming a session does not bypass present-day authorization and several requested client tools are returned in one response. Which proposal should be approved?

  1. treat old approval messages as unlimited authorization for later writes; and execute every tool_use block and return a result with each corresponding ID
  2. treat old approval messages as unlimited authorization for later writes; and execute only the first returned tool call
  3. recheck permissions and current resource state before new side effects; and execute only the first returned tool call
  4. recheck permissions and current resource state before new side effects; and execute every tool_use block and return a result with each corresponding ID

Explanation

Correct Answer

D:

In a compliance interpretation research team, conversation continuity is not a replacement for live access control or fresh tool state; alongside this, a multi-tool assistant turn can request independent actions and must receive all matching outcomes, satisfying the distinct requirements that resuming a session does not bypass present-day authorization and that several requested client tools are returned in one response.

Incorrect Answers

A:

In a compliance interpretation research team, a multi-tool assistant turn can request independent actions and must receive all matching outcomes, but permissions and operational context can change between sessions; therefore the separate requirement that resuming a session does not bypass present-day authorization would remain unsatisfied.

B:

In a compliance interpretation research team, permissions and operational context can change between sessions and the unanswered tool uses remain unresolved and later reasoning loses evidence; the design would fail both conditions: resuming a session does not bypass present-day authorization and several requested client tools are returned in one response.

C:

In a compliance interpretation research team, conversation continuity is not a replacement for live access control or fresh tool state, 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.

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