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

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.

Question 381

The architecture of a developer codebase exploration assistant must meet these three criteria: conflicting subagent findings produce one accountable interpretation; a tool result includes enough fields to support audit and follow-on actions; specialized agents work with only relevant permissions. Choose THREE measures, one for each requirement.

  1. let the fastest subagent override other findings automatically
  2. return only a friendly summary with no source identifier
  3. define each subagent role and expose the minimum matching tools
  4. return structured identifiers, status, and provenance with the data
  5. have the coordinator compare claims and sources before synthesis
  6. give every subagent the coordinator's complete tool inventory

Explanation

Correct Answers

C:

For a developer codebase exploration assistant, tool scoping shrinks both decision confusion and the blast radius of delegated actions, which directly establishes that specialized agents work with only relevant permissions; the separate requirement that conflicting subagent findings produce one accountable interpretation is handled by a different action.

D:

For a developer codebase exploration assistant, machine-readable outputs let downstream stages validate exactly what was retrieved, which directly establishes that a tool result includes enough fields to support audit and follow-on actions; the separate requirement that specialized agents work with only relevant permissions is handled by a different action.

E:

For a developer codebase exploration assistant, central reconciliation can distinguish evidence disagreement from a formatting difference, which directly establishes that conflicting subagent findings produce one accountable interpretation; the separate requirement that a tool result includes enough fields to support audit and follow-on actions is handled by a different action.

Incorrect Answers

A:

For a developer codebase exploration assistant, completion order is not a sound evidence-ranking rule, so this option cannot establish that conflicting subagent findings produce one accountable interpretation; correctly addressing a tool result includes enough fields to support audit and follow-on actions elsewhere does not repair that deficiency.

B:

For a developer codebase exploration assistant, a paraphrase hides the record needed for verification or follow-up, so this option cannot establish that a tool result includes enough fields to support audit and follow-on actions; correctly addressing specialized agents work with only relevant permissions elsewhere does not repair that deficiency.

F:

For a developer codebase exploration assistant, unneeded write or network tools expand risk without improving the specialist task, so this option cannot establish that specialized agents work with only relevant permissions; correctly addressing conflicting subagent findings produce one accountable interpretation elsewhere does not repair that deficiency.

Question 382

A team operating a developer codebase exploration assistant wants to establish two separate behaviors: the assistant locates files containing a particular symbol or string; in addition, only one approved write tool is callable in a sensitive stage. Which plan implements both?

  1. scan only filenames with Glob; and restrict the stage's allowed tool set and verify permissions in the executor
  2. scan only filenames with Glob; and let the model select from a broad global list of tools
  3. use Grep to search file contents; and let the model select from a broad global list of tools
  4. use Grep to search file contents; and restrict the stage's allowed tool set and verify permissions in the executor

Explanation

Correct Answer

D:

In a developer codebase exploration assistant, text search locates occurrences efficiently before focused reading; alongside this, capability scoping narrows possible side effects before model selection, satisfying the distinct requirements that the assistant locates files containing a particular symbol or string and that only one approved write tool is callable in a sensitive stage.

Incorrect Answers

A:

In a developer codebase exploration assistant, capability scoping narrows possible side effects before model selection, 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.

B:

In a developer codebase exploration assistant, path matching does not inspect symbol occurrences inside files and excess capabilities create avoidable routing and authorization risk; the design would fail both conditions: the assistant locates files containing a particular symbol or string and only one approved write tool is callable in a sensitive stage.

C:

In a developer codebase exploration assistant, text search locates occurrences efficiently before focused reading, but excess capabilities create avoidable routing and authorization risk; therefore the separate requirement that only one approved write tool is callable in a sensitive stage would remain unsatisfied.

Question 383

When designing a merge-request policy gate, the requirement is not satisfied unless a developer has private preferences that should not change team guidance and only one approved write tool is callable in a sensitive stage. Which implementation addresses the two independent conditions?

  1. place personal instructions in the user-level CLAUDE.md; and let the model select from a broad global list of tools
  2. add private preferences to the shared repository CLAUDE.md; and restrict the stage's allowed tool set and verify permissions in the executor
  3. add private preferences to the shared repository CLAUDE.md; and let the model select from a broad global list of tools
  4. place personal instructions in the user-level CLAUDE.md; and restrict the stage's allowed tool set and verify permissions in the executor

Explanation

Correct Answer

D:

In a merge-request policy gate, global personal guidance is available to that user's sessions without committing preferences to the project; alongside this, capability scoping narrows possible side effects before model selection, satisfying the distinct requirements that a developer has private preferences that should not change team guidance and that only one approved write tool is callable in a sensitive stage.

Incorrect Answers

A:

In a merge-request policy gate, global personal guidance is available to that user's sessions without committing preferences to the project, but excess capabilities create avoidable routing and authorization risk; therefore the separate requirement that only one approved write tool is callable in a sensitive stage would remain unsatisfied.

B:

In a merge-request policy gate, capability scoping narrows possible side effects before model selection, but project instructions would impose one person's settings on the whole team; therefore the separate requirement that a developer has private preferences that should not change team guidance would remain unsatisfied.

C:

In a merge-request policy gate, project instructions would impose one person's settings on the whole team and excess capabilities create avoidable routing and authorization risk; the design would fail both conditions: a developer has private preferences that should not change team guidance and only one approved write tool is callable in a sensitive stage.

Question 384

During review of a contract clause extraction workflow, an unmet criterion states that a machine consumer receives a schema-compliant JSON object. Which measure resolves this specific gap?

  1. use supported structured JSON output with a declared schema
  2. rely only on a sentence requesting JSON with no validation
  3. validate semantic constraints and provenance in application logic
  4. enforce the approved status enum with structured output and validate it in the consumer

Explanation

Correct Answer

A:

For a contract clause extraction workflow, constrained output enforces parseable structure and required field types at generation; this directly establishes that a machine consumer receives a schema-compliant JSON object instead of relying on an unrelated workflow control.

Incorrect Answers

B:

In a contract clause extraction workflow, prompt-only formatting can still produce malformed or incomplete results; as a result, the stated requirement that a machine consumer receives a schema-compliant JSON object would still not be met.

C:

Although JSON shape does not prove that an extracted claim is supported by the document, that only supports the distinct goal that schema-valid output is also checked against source evidence, not the requirement that a machine consumer receives a schema-compliant JSON object in a contract clause extraction workflow.

D:

Although a constrained schema expresses the allowed labels and downstream validation rejects out-of-contract values, that only supports the distinct goal that a status field can contain only approved business states, not the requirement that a machine consumer receives a schema-compliant JSON object in a contract clause extraction workflow.

Question 385

When designing a deployment-readiness verification process, the requirement is not satisfied unless a missing MCP capability is diagnosed before changing prompts and a risky refactor is evaluated before any files change. Which implementation addresses the two independent conditions?

  1. verify server connection, transport, and exposed tool availability; and let the agent immediately edit every matching file
  2. increase the system prompt length to compensate for disconnected tools; and use plan mode to inspect dependencies and propose steps before execution
  3. increase the system prompt length to compensate for disconnected tools; and let the agent immediately edit every matching file
  4. verify server connection, transport, and exposed tool availability; and use plan mode to inspect dependencies and propose steps before execution

Explanation

Correct Answer

D:

In a deployment-readiness verification process, tool discovery depends on a live configured integration, not just the prompt wording; alongside this, planning separates investigation and approval from code mutation, satisfying the distinct requirements that a missing MCP capability is diagnosed before changing prompts and that a risky refactor is evaluated before any files change.

Incorrect Answers

A:

In a deployment-readiness verification process, tool discovery depends on a live configured integration, not just the prompt wording, but early writes can spread an unapproved assumption through the repository; therefore the separate requirement that a risky refactor is evaluated before any files change would remain unsatisfied.

B:

In a deployment-readiness verification process, planning separates investigation and approval from code mutation, 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.

C:

In a deployment-readiness verification process, a model cannot call a capability absent from its available tool registry and early writes can spread an unapproved assumption through the repository; the design would fail both conditions: a missing MCP capability is diagnosed before changing prompts and a risky refactor is evaluated before any files change.

Question 386

An incident postmortem for a test failure triage bot requires controls so that a required validation step runs before the final response even when the model does not support forced tool choice and that the review produces a small, auditable patch. Which paired remedy covers both failure modes?

  1. enforce the validator in application control flow, using forced tool_choice only with compatible models; and iterate with focused diffs rather than wholesale regeneration
  2. enforce the validator in application control flow, using forced tool_choice only with compatible models; and replace every file in the component to ensure consistency
  3. rely on a prompt asking the model to call the validator; and iterate with focused diffs rather than wholesale regeneration
  4. rely on a prompt asking the model to call the validator; and replace every file in the component to ensure consistency

Explanation

Correct Answer

A:

In a test failure triage bot, application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings; alongside this, narrow changes are easier to test and evaluate against explicit requirements, satisfying the distinct requirements that a required validation step runs before the final response even when the model does not support forced tool choice and that the review produces a small, auditable patch.

Incorrect Answers

B:

In a test failure triage bot, application-level orchestration guarantees the required stage across models, while forced tool_choice is limited to compatible models and settings, but unnecessary regeneration can erase working behavior; therefore the separate requirement that the review produces a small, auditable patch would remain unsatisfied.

C:

In a test failure triage bot, narrow changes are easier to test and evaluate against explicit requirements, but prompt instructions do not guarantee execution of the validator or override model-specific tool-choice restrictions; therefore the separate requirement that a required validation step runs before the final response even when the model does not support forced tool choice would remain unsatisfied.

D:

In a test failure triage bot, prompt instructions do not guarantee execution of the validator or override model-specific tool-choice restrictions and unnecessary regeneration can erase working behavior; the design would fail both conditions: a required validation step runs before the final response even when the model does not support forced tool choice and the review produces a small, auditable patch.

Question 387

When designing a code policy conformance job, the requirement is not satisfied unless partial completion of a multi-step operation is handled safely and a downstream subagent acts on concrete upstream results. Which implementation addresses the two independent conditions?

  1. treat the first successful tool call as proof that the entire workflow succeeded; and send only a generic instruction to continue the work
  2. track individual stage outcomes and use explicit recovery or compensating actions; and pass the preceding artifact identifier and a focused summary to the next agent
  3. track individual stage outcomes and use explicit recovery or compensating actions; and send only a generic instruction to continue the work
  4. treat the first successful tool call as proof that the entire workflow succeeded; and pass the preceding artifact identifier and a focused summary to the next agent

Explanation

Correct Answer

B:

In a code policy conformance job, an orchestrated workflow must not report overall success while a required step failed; alongside this, explicit handoff preserves the specific result that the dependent stage must process, satisfying the distinct requirements that partial completion of a multi-step operation is handled safely and that a downstream subagent acts on concrete upstream results.

Incorrect Answers

A:

In a code policy conformance job, later actions can fail after an earlier side effect and the later agent cannot know which evidence or state was produced previously; the design would fail both conditions: partial completion of a multi-step operation is handled safely and a downstream subagent acts on concrete upstream results.

C:

In a code policy conformance job, an orchestrated workflow must not report overall success while a required step failed, but the later agent cannot know which evidence or state was produced previously; therefore the separate requirement that a downstream subagent acts on concrete upstream results would remain unsatisfied.

D:

In a code policy conformance job, explicit handoff preserves the specific result that the dependent stage must process, but later actions can fail after an earlier side effect; therefore the separate requirement that partial completion of a multi-step operation is handled safely would remain unsatisfied.

Question 388

In a technical review of a mobile client bug-fix task, the architect must address the following constraints together: long project guidance is divided into maintainable source files; a repeatable code-review procedure is available as a named workflow. Which change set is most defensible?

  1. use CLAUDE.md imports to organize referenced instructions; and create a documented reusable skill in SKILL.md
  2. duplicate full instruction paragraphs in every directory; and create a documented reusable skill in SKILL.md
  3. implement only use CLAUDE.md imports to organize referenced instructions; make no corresponding change for the second requirement
  4. duplicate full instruction paragraphs in every directory; and retype the entire procedure in every conversation
  5. use CLAUDE.md imports to organize referenced instructions; and retype the entire procedure in every conversation

Explanation

Correct Answer

A:

In a mobile client bug-fix task, modular imports keep a short entry point while preserving reviewed details in separate files; alongside this, skills package instructions and supporting resources for invocation across similar tasks, satisfying the distinct requirements that long project guidance is divided into maintainable source files and that a repeatable code-review procedure is available as a named workflow.

Incorrect Answers

B:

In a mobile client bug-fix task, skills package instructions and supporting resources for invocation across similar tasks, 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.

C:

In a mobile client bug-fix task, modular imports keep a short entry point while preserving reviewed details in separate files, but the independent mechanism for the other criterion is absent: skills package instructions and supporting resources for invocation across similar tasks; as written, the design does not ensure that a repeatable code-review procedure is available as a named workflow.

D:

In a mobile client bug-fix task, copying guidance encourages drift when policies change and manual repetition produces drift and loses shared revisions; the design would fail both conditions: long project guidance is divided into maintainable source files and a repeatable code-review procedure is available as a named workflow.

E:

In a mobile client bug-fix task, modular imports keep a short entry point while preserving reviewed details in separate files, but manual repetition produces drift and loses shared revisions; therefore the separate requirement that a repeatable code-review procedure is available as a named workflow would remain unsatisfied.

Question 389

When designing a monorepo testing overhaul, the requirement is not satisfied unless the implementation plan receives stakeholder sign-off and an existing file receives a precise localized replacement. Which implementation addresses the two independent conditions?

  1. treat the agent's internally generated plan as implicit approval; and use Edit for an exact targeted change
  2. present ordered changes, risks, and verification steps before switching to execution; and overwrite the whole file with a newly generated copy
  3. treat the agent's internally generated plan as implicit approval; and overwrite the whole file with a newly generated copy
  4. present ordered changes, risks, and verification steps before switching to execution; and use Edit for an exact targeted change

Explanation

Correct Answer

D:

In a monorepo testing overhaul, an explicit review point aligns the agent's work with the authorized scope; alongside this, surgical edits preserve unrelated lines and provide reviewable diffs, satisfying the distinct requirements that the implementation plan receives stakeholder sign-off and that an existing file receives a precise localized replacement.

Incorrect Answers

A:

In a monorepo testing overhaul, surgical edits preserve unrelated lines and provide reviewable diffs, 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.

B:

In a monorepo testing overhaul, an explicit review point aligns the agent's work with the authorized scope, but full replacement risks losing unrelated code and formatting; therefore the separate requirement that an existing file receives a precise localized replacement would remain unsatisfied.

C:

In a monorepo testing overhaul, the system cannot infer external authorization from its own reasoning and full replacement risks losing unrelated code and formatting; the design would fail both conditions: the implementation plan receives stakeholder sign-off and an existing file receives a precise localized replacement.

Question 390

An incident postmortem for a multi-source competitor research system requires controls so that the system can continue when one specialist returns an explicit failure and that tool-call logging does not modify a successful tool result. Which paired remedy covers both failure modes?

  1. record per-branch status and let the coordinator choose retry or partial response; and rewrite every tool result as a free-form paraphrase
  2. treat every subagent error string as a valid research conclusion; and use an observation-only hook for telemetry when rewriting is unnecessary
  3. treat every subagent error string as a valid research conclusion; and rewrite every tool result as a free-form paraphrase
  4. record per-branch status and let the coordinator choose retry or partial response; and use an observation-only hook for telemetry when rewriting is unnecessary

Explanation

Correct Answer

D:

In a multi-source competitor research system, the orchestration layer must distinguish missing evidence from a negative factual finding; alongside this, separating instrumentation from mutation reduces the risk of corrupting evidence, satisfying the distinct requirements that the system can continue when one specialist returns an explicit failure and that tool-call logging does not modify a successful tool result.

Incorrect Answers

A:

In a multi-source competitor research system, the orchestration layer must distinguish missing evidence from a negative factual finding, but summaries can discard fields that subsequent steps require; therefore the separate requirement that tool-call logging does not modify a successful tool result would remain unsatisfied.

B:

In a multi-source competitor research system, separating instrumentation from mutation reduces the risk of corrupting evidence, but error text is operational state rather than evidence about the world; therefore the separate requirement that the system can continue when one specialist returns an explicit failure would remain unsatisfied.

C:

In a multi-source competitor research system, error text is operational state rather than evidence about the world and summaries can discard fields that subsequent steps require; the design would fail both conditions: the system can continue when one specialist returns an explicit failure and tool-call logging does not modify a successful tool result.

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