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

Question 370

For a test failure triage bot, acceptance depends on demonstrating that independent stages of a complex job run efficiently. Which approach is the strongest fit?

  1. use one focused tool-assisted agent for the bounded task
  2. place evidence validation before the drafting stage
  3. divide work along independent outputs and run those stages in parallel
  4. add a synthesis stage with explicit conflict-resolution criteria
  5. split the job into an arbitrary fixed chain of agents

Explanation

Correct Answer

C:

For a test failure triage bot, dependency-aware decomposition avoids serial work when branches do not consume one another; this directly establishes that independent stages of a complex job run efficiently instead of relying on an unrelated workflow control.

Incorrect Answers

A:

Although orchestration overhead is not justified when there is no useful specialization or concurrency, that only supports the distinct goal that a straightforward lookup avoids unnecessary agent coordination, not the requirement that independent stages of a complex job run efficiently in a test failure triage bot.

B:

Although a dependent stage must receive validated inputs to avoid propagating unsupported conclusions, that only supports the distinct goal that the report is not drafted before evidence is checked, not the requirement that independent stages of a complex job run efficiently in a test failure triage bot.

D:

Although merging divergent work requires an authoritative step rather than choosing by arrival time, that only supports the distinct goal that two teams' analyses are reconciled before publication, not the requirement that independent stages of a complex job run efficiently in a test failure triage bot.

E:

In a test failure triage bot, a rigid sequence creates waits even where no dependency exists; as a result, the stated requirement that independent stages of a complex job run efficiently would still not be met.

Question 371

In a pull-request regression detection job, the acceptance criteria require that the review produces a small, auditable patch and that policy decisions use measurable conditions rather than tone. Which paired implementation meets both?

  1. iterate with focused diffs rather than wholesale regeneration; and ask the model to use its general intuition about severity
  2. iterate with focused diffs rather than wholesale regeneration; and describe exact observable triggers and exception rules
  3. replace every file in the component to ensure consistency; and describe exact observable triggers and exception rules
  4. replace every file in the component to ensure consistency; and ask the model to use its general intuition about severity

Explanation

Correct Answer

B:

In a pull-request regression detection job, narrow changes are easier to test and evaluate against explicit requirements; alongside this, operationalized criteria reduce disagreement across similar inputs, satisfying the distinct requirements that the review produces a small, auditable patch and that policy decisions use measurable conditions rather than tone.

Incorrect Answers

A:

In a pull-request regression detection job, narrow changes are easier to test and evaluate against explicit requirements, but unquantified intuition varies between cases and reviewers; therefore the separate requirement that policy decisions use measurable conditions rather than tone would remain unsatisfied.

C:

In a pull-request regression detection job, operationalized criteria reduce disagreement across similar inputs, but unnecessary regeneration can erase working behavior; therefore the separate requirement that the review produces a small, auditable patch would remain unsatisfied.

D:

In a pull-request regression detection job, unnecessary regeneration can erase working behavior and unquantified intuition varies between cases and reviewers; the design would fail both conditions: the review produces a small, auditable patch and policy decisions use measurable conditions rather than tone.

Question 372

While preparing a pre-merge code inspection workflow for deployment, engineers must ensure that CI failures provide actionable evidence to maintainers; they must also ensure that long project guidance is divided into maintainable source files. Which combination best satisfies those requirements?

  1. discard the runner logs and keep only the assistant's final sentence; and use CLAUDE.md imports to organize referenced instructions
  2. discard the runner logs and keep only the assistant's final sentence; and duplicate full instruction paragraphs in every directory
  3. persist structured errors, relevant logs, and a bounded diagnostic summary; and use CLAUDE.md imports to organize referenced instructions
  4. persist structured errors, relevant logs, and a bounded diagnostic summary; and duplicate full instruction paragraphs in every directory

Explanation

Correct Answer

C:

In a pre-merge code inspection workflow, stable artifacts help maintainers reproduce the problem without rerunning a chat; alongside this, modular imports keep a short entry point while preserving reviewed details in separate files, satisfying the distinct requirements that CI failures provide actionable evidence to maintainers and that long project guidance is divided into maintainable source files.

Incorrect Answers

A:

In a pre-merge code inspection workflow, modular imports keep a short entry point while preserving reviewed details in separate files, but the missing trace impedes diagnosis of command or infrastructure failures; therefore the separate requirement that CI failures provide actionable evidence to maintainers would remain unsatisfied.

B:

In a pre-merge code inspection workflow, the missing trace impedes diagnosis of command or infrastructure failures and copying guidance encourages drift when policies change; the design would fail both conditions: CI failures provide actionable evidence to maintainers and long project guidance is divided into maintainable source files.

D:

In a pre-merge code inspection workflow, stable artifacts help maintainers reproduce the problem without rerunning a chat, but copying guidance encourages drift when policies change; therefore the separate requirement that long project guidance is divided into maintainable source files would remain unsatisfied.

Question 373

Before expanding a procurement document processing system, the owner must demonstrate that a large batch shares a consistent evaluation rubric, while also demonstrating that a failed high-stakes step prevents a false final success signal. Which design provides both controls?

  1. freeze the prompt version and schema for the submission set; and enforce required-stage completion before publishing a success status
  2. freeze the prompt version and schema for the submission set; and ignore errors after the first successful agent completion
  3. change the classification criteria mid-batch without version tracking; and enforce required-stage completion before publishing a success status
  4. change the classification criteria mid-batch without version tracking; and ignore errors after the first successful agent completion

Explanation

Correct Answer

A:

In a procurement document processing system, versioned common instructions make independently processed records comparable; alongside this, a final gate must account for every mandatory stage rather than aggregate optimistic text, satisfying the distinct requirements that a large batch shares a consistent evaluation rubric and that a failed high-stakes step prevents a false final success signal.

Incorrect Answers

B:

In a procurement document processing system, versioned common instructions make independently processed records comparable, but later failures can invalidate the claimed result; therefore the separate requirement that a failed high-stakes step prevents a false final success signal would remain unsatisfied.

C:

In a procurement document processing system, a final gate must account for every mandatory stage rather than aggregate optimistic text, but mixed rubrics undermine consistent downstream aggregation; therefore the separate requirement that a large batch shares a consistent evaluation rubric would remain unsatisfied.

D:

In a procurement document processing system, mixed rubrics undermine consistent downstream aggregation and later failures can invalidate the claimed result; the design would fail both conditions: a large batch shares a consistent evaluation rubric and a failed high-stakes step prevents a false final success signal.

Question 374

For a repository maintenance copilot, a reviewer identifies two independent obligations: separate code modules can be inspected in parallel and a coding agent inspects a known source file without changing it. Which proposal should be approved?

  1. spawn independent specialists in the same delegation stage; and run arbitrary shell commands to modify the file during inspection
  2. spawn independent specialists in the same delegation stage; and use Read on the identified file
  3. make the second specialist wait for the first even though their modules are independent; and run arbitrary shell commands to modify the file during inspection
  4. make the second specialist wait for the first even though their modules are independent; and use Read on the identified file

Explanation

Correct Answer

B:

In a repository maintenance copilot, concurrent subagents can examine non-overlapping modules before the coordinator merges their reports; alongside this, file reading provides exact content for analysis without executing the project, satisfying the distinct requirements that separate code modules can be inspected in parallel and that a coding agent inspects a known source file without changing it.

Incorrect Answers

A:

In a repository maintenance copilot, concurrent subagents can examine non-overlapping modules before the coordinator merges their reports, but mutation is unnecessary for a read-only code review; therefore the separate requirement that a coding agent inspects a known source file without changing it would remain unsatisfied.

C:

In a repository maintenance copilot, serialization wastes time without supplying a dependency and mutation is unnecessary for a read-only code review; the design would fail both conditions: separate code modules can be inspected in parallel and a coding agent inspects a known source file without changing it.

D:

In a repository maintenance copilot, file reading provides exact content for analysis without executing the project, but serialization wastes time without supplying a dependency; therefore the separate requirement that separate code modules can be inspected in parallel would remain unsatisfied.

Question 375

In a technical review of a cross-platform application migration, the architect must address the following constraints together: an exploratory branch can be compared with a baseline later; untrusted project MCP definitions receive approval in interactive Claude Code sessions. Which change set is most defensible?

  1. overwrite the baseline notes with the trial branch's results; and review and approve project-scoped server configuration before connecting interactively
  2. preserve both branch identifiers and outcome summaries; and automatically approve every MCP definition found in a cloned repository
  3. overwrite the baseline notes with the trial branch's results; and automatically approve every MCP definition found in a cloned repository
  4. preserve both branch identifiers and outcome summaries; and review and approve project-scoped server configuration before connecting interactively

Explanation

Correct Answer

D:

In a cross-platform application migration, tracking lineage makes result comparison possible without confusing which session produced an artifact; alongside this, interactive project trust checks limit execution of unfamiliar server commands and endpoints, satisfying the distinct requirements that an exploratory branch can be compared with a baseline later and that untrusted project MCP definitions receive approval in interactive Claude Code sessions.

Incorrect Answers

A:

In a cross-platform application migration, interactive project trust checks limit execution of unfamiliar server commands and endpoints, but losing provenance prevents trustworthy evaluation; therefore the separate requirement that an exploratory branch can be compared with a baseline later would remain unsatisfied.

B:

In a cross-platform application migration, tracking lineage makes result comparison possible without confusing which session produced an artifact, but repository content can include unexpected executable commands and unattended sessions require explicit policy controls; therefore the separate requirement that untrusted project MCP definitions receive approval in interactive Claude Code sessions would remain unsatisfied.

C:

In a cross-platform application migration, losing provenance prevents trustworthy evaluation and repository content can include unexpected executable commands and unattended sessions require explicit policy controls; the design would fail both conditions: an exploratory branch can be compared with a baseline later and untrusted project MCP definitions receive approval in interactive Claude Code sessions.

Question 376

For a repository release validation process, a reviewer identifies two independent obligations: a delegated skill should not fill the caller's active context and a CI job invokes Claude without a terminal conversation. Which proposal should be approved?

  1. configure the skill to run in an isolated forked context where supported; and run Claude Code in non-interactive print mode with -p
  2. load all investigation steps into the same conversation by default; and launch an interactive Claude terminal in an unattended runner
  3. load all investigation steps into the same conversation by default; and run Claude Code in non-interactive print mode with -p
  4. configure the skill to run in an isolated forked context where supported; and launch an interactive Claude terminal in an unattended runner

Explanation

Correct Answer

A:

In a repository release validation process, a fork isolates exploratory work and returns a concise result to its caller; alongside this, headless invocation permits scripted automation and exits after the requested task, satisfying the distinct requirements that a delegated skill should not fill the caller's active context and that a CI job invokes Claude without a terminal conversation.

Incorrect Answers

B:

In a repository release validation process, the caller's window accumulates unnecessary intermediate details and an interactive session can block automation waiting for a person; the design would fail both conditions: a delegated skill should not fill the caller's active context and a CI job invokes Claude without a terminal conversation.

C:

In a repository release validation process, headless invocation permits scripted automation and exits after the requested task, 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.

D:

In a repository release validation process, a fork isolates exploratory work and returns a concise result to its caller, but an interactive session can block automation waiting for a person; therefore the separate requirement that a CI job invokes Claude without a terminal conversation would remain unsatisfied.

Question 377

The architect for a tender-response data extractor needs to ensure that a risk prompt handles missing supporting evidence honestly. What should the team implement?

  1. instruct the model to return unknown or needs-review when evidence is absent
  2. specify inclusion criteria and explicit exclusion conditions
  3. define explicit positive evidence and an abstain or review category
  4. require a definitive yes-or-no answer for every incomplete record

Explanation

Correct Answer

A:

For a tender-response data extractor, a defined abstention path avoids forced confident judgments without facts; this directly establishes that a risk prompt handles missing supporting evidence honestly instead of relying on an unrelated workflow control.

Incorrect Answers

B:

Although negative boundaries teach the model when a near-match must not trigger, that only supports the distinct goal that the system distinguishes acceptable and unacceptable edge cases, not the requirement that a risk prompt handles missing supporting evidence honestly in a tender-response data extractor.

C:

Although clear decision thresholds separate direct evidence from weak similarity, that only supports the distinct goal that a classifier avoids marking uncertain cases as confirmed violations, not the requirement that a risk prompt handles missing supporting evidence honestly in a tender-response data extractor.

D:

In a tender-response data extractor, forced binaries hide uncertainty as false certainty; as a result, the stated requirement that a risk prompt handles missing supporting evidence honestly would still not be met.

Question 378

For an unfamiliar monorepo investigation, a reviewer identifies two independent obligations: dependent analysis begins only when source retrieval is complete and the model can distinguish two similar business tools. Which proposal should be approved?

  1. start the analysis and retrieval agents together without shared results; and give each tool a specific purpose and exclusion examples in its description
  2. run retrieval before analysis and pass its validated artifacts; and give each tool a specific purpose and exclusion examples in its description
  3. start the analysis and retrieval agents together without shared results; and give both tools vague names with identical generic descriptions
  4. run retrieval before analysis and pass its validated artifacts; and give both tools vague names with identical generic descriptions

Explanation

Correct Answer

B:

In an unfamiliar monorepo investigation, a downstream agent needs actual upstream findings rather than an assumed future result; alongside this, discriminative descriptions reduce wrong routing when operations sound alike, satisfying the distinct requirements that dependent analysis begins only when source retrieval is complete and that the model can distinguish two similar business tools.

Incorrect Answers

A:

In an unfamiliar monorepo investigation, discriminative descriptions reduce wrong routing when operations sound alike, 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, the analysis branch cannot evaluate evidence it has not received and a model cannot reliably select on boundaries that the interface never explains; the design would fail both conditions: dependent analysis begins only when source retrieval is complete and the model can distinguish two similar business tools.

D:

In an unfamiliar monorepo investigation, a downstream agent needs actual upstream findings rather than an assumed future result, but a model cannot reliably select on boundaries that the interface never explains; therefore the separate requirement that the model can distinguish two similar business tools would remain unsatisfied.

Question 379

An incident postmortem for a repository search copilot requires controls so that separate code modules can be inspected in parallel and that workload growth does not cause uncontrolled parallel fan-out. Which paired remedy covers both failure modes?

  1. make the second specialist wait for the first even though their modules are independent; and limit concurrency and schedule independent jobs against execution budgets
  2. make the second specialist wait for the first even though their modules are independent; and launch all possible child tasks at once without resource controls
  3. spawn independent specialists in the same delegation stage; and limit concurrency and schedule independent jobs against execution budgets
  4. spawn independent specialists in the same delegation stage; and launch all possible child tasks at once without resource controls

Explanation

Correct Answer

C:

In a repository search copilot, concurrent subagents can examine non-overlapping modules before the coordinator merges their reports; alongside this, bounded orchestration balances throughput with tool quotas and downstream service capacity, satisfying the distinct requirements that separate code modules can be inspected in parallel and that workload growth does not cause uncontrolled parallel fan-out.

Incorrect Answers

A:

In a repository search copilot, bounded orchestration balances throughput with tool quotas and downstream service capacity, but serialization wastes time without supplying a dependency; therefore the separate requirement that separate code modules can be inspected in parallel would remain unsatisfied.

B:

In a repository search copilot, serialization wastes time without supplying a dependency and unbounded fan-out can overwhelm tools and blow through cost budgets; the design would fail both conditions: separate code modules can be inspected in parallel and workload growth does not cause uncontrolled parallel fan-out.

D:

In a repository search copilot, concurrent subagents can examine non-overlapping modules before the coordinator merges their reports, but unbounded fan-out can overwhelm tools and blow through cost budgets; therefore the separate requirement that workload growth does not cause uncontrolled parallel fan-out would remain unsatisfied.

Question 380

An incident postmortem for a structured report conversion service requires controls so that an extraction error is caught before storage and that a machine consumer receives a schema-compliant JSON object. Which paired remedy covers both failure modes?

  1. write the response to the database without checking required invariants; and use supported structured JSON output with a declared schema
  2. validate parsed data against application rules and source constraints; and use supported structured JSON output with a declared schema
  3. write the response to the database without checking required invariants; and rely only on a sentence requesting JSON with no validation
  4. validate parsed data against application rules and source constraints; and rely only on a sentence requesting JSON with no validation
  5. implement only validate parsed data against application rules and source constraints; make no corresponding change for the second requirement

Explanation

Correct Answer

B:

In a structured report conversion service, local validation detects missing cross-field relationships even when the JSON is syntactically valid; alongside this, constrained output enforces parseable structure and required field types at generation, satisfying the distinct requirements that an extraction error is caught before storage and that a machine consumer receives a schema-compliant JSON object.

Incorrect Answers

A:

In a structured report conversion service, constrained output enforces parseable structure and required field types at generation, but valid-looking output may still violate business rules; therefore the separate requirement that an extraction error is caught before storage would remain unsatisfied.

C:

In a structured report conversion service, valid-looking output may still violate business rules and prompt-only formatting can still produce malformed or incomplete results; the design would fail both conditions: an extraction error is caught before storage and a machine consumer receives a schema-compliant JSON object.

D:

In a structured report conversion service, local validation detects missing cross-field relationships even when the JSON is syntactically valid, but prompt-only formatting can still produce malformed or incomplete results; therefore the separate requirement that a machine consumer receives a schema-compliant JSON object would remain unsatisfied.

E:

In a structured report conversion service, local validation detects missing cross-field relationships even when the JSON is syntactically valid, but the independent mechanism for the other criterion is absent: constrained output enforces parseable structure and required field types at generation; as written, the design does not ensure that a machine consumer receives a schema-compliant JSON object.

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