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

Question 1

The release checklist for an unfamiliar monorepo investigation explicitly checks that dependent analysis begins only when source retrieval is complete; it also checks that the assistant locates files containing a particular symbol or string. What coordinated solution meets the checklist?

  1. start the analysis and retrieval agents together without shared results; and scan only filenames with Glob
  2. start the analysis and retrieval agents together without shared results; and use Grep to search file contents
  3. run retrieval before analysis and pass its validated artifacts; and scan only filenames with Glob
  4. run retrieval before analysis and pass its validated artifacts; and use Grep to search file contents

Explanation

Correct Answer

D:

In an unfamiliar monorepo investigation, a downstream agent needs actual upstream findings rather than an assumed future result; alongside this, text search locates occurrences efficiently before focused reading, satisfying the distinct requirements that dependent analysis begins only when source retrieval is complete and that the assistant locates files containing a particular symbol or string.

Incorrect Answers

A:

In an unfamiliar monorepo investigation, the analysis branch cannot evaluate evidence it has not received and path matching does not inspect symbol occurrences inside files; the design would fail both conditions: dependent analysis begins only when source retrieval is complete and the assistant locates files containing a particular symbol or string.

B:

In an unfamiliar monorepo investigation, text search locates occurrences efficiently before focused reading, but the analysis branch cannot evaluate evidence it has not received; therefore the separate requirement that dependent analysis begins only when source retrieval is complete would remain unsatisfied.

C:

In an unfamiliar monorepo investigation, a downstream agent needs actual upstream findings rather than an assumed future result, 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.

Question 2

In a billing-dispute support agent, the immediate design requirement is that quality drift is detected after a workflow launches. Which change most directly establishes that behavior?

  1. validate one development example and never review production output
  2. route high-impact or low-evidence results to an authorized reviewer
  3. require source and business-rule checks regardless of model agreement
  4. sample outcomes for periodic human QA against known criteria

Explanation

Correct Answer

D:

For a billing-dispute support agent, ongoing calibration can reveal changed input distributions and silent error patterns; this directly establishes that quality drift is detected after a workflow launches instead of relying on an unrelated workflow control.

Incorrect Answers

A:

In a billing-dispute support agent, production inputs may differ from the initial examples; as a result, the stated requirement that quality drift is detected after a workflow launches would still not be met.

B:

Although human approval supplies accountability where a mistaken model result has material cost, that only supports the distinct goal that a consequential claim receives independent human sign-off, not the requirement that quality drift is detected after a workflow launches in a billing-dispute support agent.

C:

Although correlated model errors can survive consensus without external verification, that only supports the distinct goal that a conclusion supported by model agreement is also tested against source evidence, not the requirement that quality drift is detected after a workflow launches in a billing-dispute support agent.

Question 3

In an order-status triage agent, the immediate design requirement is that a failed retrieval agent does not masquerade as having found no matches. Which change most directly establishes that behavior?

  1. propagate task IDs, error codes, and correlation references
  2. return a typed failure status with its origin to the coordinator
  3. convert every retrieval failure into an empty list
  4. enforce required-stage completion before publishing a success status

Explanation

Correct Answer

B:

For an order-status triage agent, an operational error must remain distinguishable from a valid empty result; this directly establishes that a failed retrieval agent does not masquerade as having found no matches instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although tracing execution lineage helps route the incident to the right failing component, that only supports the distinct goal that the coordinator can identify which subagent produced a broken artifact, not the requirement that a failed retrieval agent does not masquerade as having found no matches in an order-status triage agent.

C:

In an order-status triage agent, the final report could incorrectly claim no sources exist; as a result, the stated requirement that a failed retrieval agent does not masquerade as having found no matches would still not be met.

D:

Although a final gate must account for every mandatory stage rather than aggregate optimistic text, that only supports the distinct goal that a failed high-stakes step prevents a false final success signal, not the requirement that a failed retrieval agent does not masquerade as having found no matches in an order-status triage agent.

Question 4

In a technical review of a mobile client bug-fix task, the architect must address the following constraints together: an exploratory branch can be compared with a baseline later; API conventions apply only to source files under an API directory. Which change set is most defensible?

  1. preserve both branch identifiers and outcome summaries; and add a .claude/rules file with paths matching the API subtree
  2. overwrite the baseline notes with the trial branch's results; and put API-specific formatting rules in always-on project guidance
  3. preserve both branch identifiers and outcome summaries; and put API-specific formatting rules in always-on project guidance
  4. overwrite the baseline notes with the trial branch's results; and add a .claude/rules file with paths matching the API subtree

Explanation

Correct Answer

A:

In a mobile client bug-fix task, tracking lineage makes result comparison possible without confusing which session produced an artifact; alongside this, path-scoped rules load when the target context matches, keeping unrelated tasks clean, satisfying the distinct requirements that an exploratory branch can be compared with a baseline later and that API conventions apply only to source files under an API directory.

Incorrect Answers

B:

In a mobile client bug-fix task, losing provenance prevents trustworthy evaluation and frontend and documentation tasks then receive irrelevant instructions; the design would fail both conditions: an exploratory branch can be compared with a baseline later and API conventions apply only to source files under an API directory.

C:

In a mobile client bug-fix task, tracking lineage makes result comparison possible without confusing which session produced an artifact, but frontend and documentation tasks then receive irrelevant instructions; therefore the separate requirement that API conventions apply only to source files under an API directory would remain unsatisfied.

D:

In a mobile client bug-fix task, path-scoped rules load when the target context matches, keeping unrelated tasks clean, but losing provenance prevents trustworthy evaluation; therefore the separate requirement that an exploratory branch can be compared with a baseline later would remain unsatisfied.

Question 5

The architecture of a pull-request regression detection job must meet these three criteria: only one approved write tool is callable in a sensitive stage; tool-call logging does not modify a successful tool result; a new source file is created from supplied content. Choose THREE measures, one for each requirement.

  1. rewrite every tool result as a free-form paraphrase
  2. let the model select from a broad global list of tools
  3. use Grep to create the source file
  4. use Write for file creation
  5. use an observation-only hook for telemetry when rewriting is unnecessary
  6. restrict the stage's allowed tool set and verify permissions in the executor

Explanation

Correct Answers

D:

For a pull-request regression detection job, writing a new artifact is appropriate when no existing target needs surgical modification, which directly establishes that a new source file is created from supplied content; the separate requirement that only one approved write tool is callable in a sensitive stage is handled by a different action.

E:

For a pull-request regression detection job, separating instrumentation from mutation reduces the risk of corrupting evidence, which directly establishes that tool-call logging does not modify a successful tool result; the separate requirement that a new source file is created from supplied content is handled by a different action.

F:

For a pull-request regression detection job, 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 tool-call logging does not modify a successful tool result is handled by a different action.

Incorrect Answers

A:

For a pull-request regression detection job, summaries can discard fields that subsequent steps require, so this option cannot establish that tool-call logging does not modify a successful tool result; correctly addressing a new source file is created from supplied content elsewhere does not repair that deficiency.

B:

For a pull-request regression detection job, 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 tool-call logging does not modify a successful tool result elsewhere does not repair that deficiency.

C:

For a pull-request regression detection job, search utilities do not create code artifacts, so this option cannot establish that a new source file is created from supplied content; correctly addressing only one approved write tool is callable in a sensitive stage elsewhere does not repair that deficiency.

Question 6

In a release-triage developer agent, the engineering team must guarantee that a tool result includes enough fields to support audit and follow-on actions. What is the most appropriate control?

  1. return structured identifiers, status, and provenance with the data
  2. separate read-only lookup from side-effecting update interfaces
  3. return only a friendly summary with no source identifier
  4. document examples and conditions where each tool must not be used
  5. declare an operation enum in the schema and reject values outside it in the tool handler

Explanation

Correct Answer

A:

For a release-triage developer agent, machine-readable outputs let downstream stages validate exactly what was retrieved; this directly establishes that a tool result includes enough fields to support audit and follow-on actions instead of relying on an unrelated workflow control.

Incorrect Answers

B:

Although clear operation boundaries support least privilege and understandable approvals, that only supports the distinct goal that each tool interface has a single clear operation boundary, not the requirement that a tool result includes enough fields to support audit and follow-on actions in a release-triage developer agent.

C:

In a release-triage developer agent, a paraphrase hides the record needed for verification or follow-up; as a result, the stated requirement that a tool result includes enough fields to support audit and follow-on actions would still not be met.

D:

Although contrastive guidance helps tool choice when resource names look similar, that only supports the distinct goal that near-overlapping retrieval tools are selected by actual boundary, not the requirement that a tool result includes enough fields to support audit and follow-on actions in a release-triage developer agent.

E:

Although schema constraints guide valid selections and runtime validation blocks unsupported operation values, that only supports the distinct goal that a selector accepts only supported operation names, not the requirement that a tool result includes enough fields to support audit and follow-on actions in a release-triage developer agent.

Question 7

When designing a developer codebase exploration assistant, the requirement is not satisfied unless two nested packages follow distinct framework conventions and the assistant locates files containing a particular symbol or string. Which implementation addresses the two independent conditions?

  1. write one ambiguous instruction for both packages; and scan only filenames with Glob
  2. write one ambiguous instruction for both packages; and use Grep to search file contents
  3. create separate path-specific rule files for each package; and scan only filenames with Glob
  4. create separate path-specific rule files for each package; and use Grep to search file contents

Explanation

Correct Answer

D:

In a developer codebase exploration assistant, scoped conventions avoid contradictory patterns between codebases sharing a monorepo; alongside this, text search locates occurrences efficiently before focused reading, satisfying the distinct requirements that two nested packages follow distinct framework conventions and that the assistant locates files containing a particular symbol or string.

Incorrect Answers

A:

In a developer codebase exploration assistant, the model must guess which framework convention applies and path matching does not inspect symbol occurrences inside files; the design would fail both conditions: two nested packages follow distinct framework conventions and the assistant locates files containing a particular symbol or string.

B:

In a developer codebase exploration assistant, text search locates occurrences efficiently before focused reading, 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 developer codebase exploration assistant, scoped conventions avoid contradictory patterns between codebases sharing a monorepo, 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.

Question 8

Before expanding a service refactoring initiative, the owner must demonstrate that all contributors receive the repository's stable engineering conventions, while also demonstrating that a high-risk workflow only invokes specifically approved capabilities. Which design provides both controls?

  1. put concise shared guidance in the repository root CLAUDE.md; and declare allowed-tools for the skill and enforce executor permissions
  2. put concise shared guidance in the repository root CLAUDE.md; and rely on a sentence asking the agent not to use risky tools
  3. put team-wide rules only in one developer's user-level instructions; and rely on a sentence asking the agent not to use risky tools
  4. put team-wide rules only in one developer's user-level instructions; and declare allowed-tools for the skill and enforce executor permissions

Explanation

Correct Answer

A:

In a service refactoring initiative, project instructions travel with the codebase and establish common architecture and build constraints; alongside this, tool restrictions narrow the agent's operational capability while the skill runs, satisfying the distinct requirements that all contributors receive the repository's stable engineering conventions and that a high-risk workflow only invokes specifically approved capabilities.

Incorrect Answers

B:

In a service refactoring initiative, project instructions travel with the codebase and establish common architecture and build constraints, but instruction-only boundaries cannot substitute for actual tool authorization; therefore the separate requirement that a high-risk workflow only invokes specifically approved capabilities would remain unsatisfied.

C:

In a service refactoring initiative, personal files do not distribute the intended conventions to other contributors and instruction-only boundaries cannot substitute for actual tool authorization; the design would fail both conditions: all contributors receive the repository's stable engineering conventions and a high-risk workflow only invokes specifically approved capabilities.

D:

In a service refactoring initiative, tool restrictions narrow the agent's operational capability while the skill runs, but personal files do not distribute the intended conventions to other contributors; therefore the separate requirement that all contributors receive the repository's stable engineering conventions would remain unsatisfied.

Question 9

The release gate for a source-grounded policy synthesis service requires that offline extraction cost is controlled without missing a service-level deadline; it also requires that one agent's draft is reviewed independently for errors. Which TWO actions meet the specified checks? Choose TWO.

  1. select the lowest-cost async path even for strict real-time actions
  2. compare batch turnaround with the workload's time requirements
  3. ask the draft generator to declare its own work perfect
  4. use a separate review pass with explicit criteria

Explanation

Correct Answers

B:

For a source-grounded policy synthesis service, asynchronous savings are appropriate only when delayed completion is acceptable, which directly establishes that offline extraction cost is controlled without missing a service-level deadline; the separate requirement that one agent's draft is reviewed independently for errors is handled by a different action.

D:

For a source-grounded policy synthesis service, independent criticism exposes omissions that unstructured self-praise can miss, which directly establishes that one agent's draft is reviewed independently for errors; the separate requirement that offline extraction cost is controlled without missing a service-level deadline is handled by a different action.

Incorrect Answers

A:

For a source-grounded policy synthesis service, meeting a live deadline can matter more than per-request savings, so this option cannot establish that offline extraction cost is controlled without missing a service-level deadline; correctly addressing one agent's draft is reviewed independently for errors elsewhere does not repair that deficiency.

C:

For a source-grounded policy synthesis service, self-assessment without a second criterion-based pass is weak evidence, so this option cannot establish that one agent's draft is reviewed independently for errors; correctly addressing offline extraction cost is controlled without missing a service-level deadline elsewhere does not repair that deficiency.

Question 10

For a nightly code quality job, acceptance depends on demonstrating that resuming a session does not bypass present-day authorization. Which approach is the strongest fit?

  1. treat old approval messages as unlimited authorization for later writes
  2. preserve both branch identifiers and outcome summaries
  3. resume the stored session by its identifier
  4. recheck permissions and current resource state before new side effects
  5. initialize a fresh session with a verified structured summary

Explanation

Correct Answer

D:

For a nightly code quality job, conversation continuity is not a replacement for live access control or fresh tool state; this directly establishes that resuming a session does not bypass present-day authorization instead of relying on an unrelated workflow control.

Incorrect Answers

A:

In a nightly code quality job, permissions and operational context can change between sessions; as a result, the stated requirement that resuming a session does not bypass present-day authorization would still not be met.

B:

Although tracking lineage makes result comparison possible without confusing which session produced an artifact, that only supports the distinct goal that an exploratory branch can be compared with a baseline later, not the requirement that resuming a session does not bypass present-day authorization in a nightly code quality job.

C:

Although session resumption retains the recorded conversation and avoids rebuilding the entire task from scratch, that only supports the distinct goal that a developer returns to an interrupted session with prior reasoning, not the requirement that resuming a session does not bypass present-day authorization in a nightly code quality job.

E:

Although a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, that only supports the distinct goal that a new agent gets only durable context from a completed job, not the requirement that resuming a session does not bypass present-day authorization in a nightly code quality job.

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