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

Question 830

Production readiness for a database migration coding project depends on ensuring that a high-risk workflow only invokes specifically approved capabilities and that only one approved write tool is callable in a sensitive stage. Select the most appropriate combined approach.

  1. rely on a sentence asking the agent not to use risky tools; and let the model select from a broad global list of tools
  2. declare allowed-tools for the skill and enforce executor permissions; and let the model select from a broad global list of tools
  3. rely on a sentence asking the agent not to use risky tools; and restrict the stage's allowed tool set and verify permissions in the executor
  4. declare allowed-tools for the skill and enforce executor permissions; and restrict the stage's allowed tool set and verify permissions in the executor

Explanation

Correct Answer

D:

In a database migration coding project, tool restrictions narrow the agent's operational capability while the skill runs; alongside this, capability scoping narrows possible side effects before model selection, satisfying the distinct requirements that a high-risk workflow only invokes specifically approved capabilities and that only one approved write tool is callable in a sensitive stage.

Incorrect Answers

A:

In a database migration coding project, instruction-only boundaries cannot substitute for actual tool authorization and excess capabilities create avoidable routing and authorization risk; the design would fail both conditions: a high-risk workflow only invokes specifically approved capabilities and only one approved write tool is callable in a sensitive stage.

B:

In a database migration coding project, tool restrictions narrow the agent's operational capability while the skill runs, 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.

C:

In a database migration coding project, capability scoping narrows possible side effects before model selection, 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.

Question 831

The architecture of a merchant support assistant must meet these three criteria: repeated delivery of one action request cannot create duplicate writes; every high-impact tool invocation produces an audit event; important workflow state survives context compression or process restarts. Choose THREE measures, one for each requirement.

  1. use an idempotency key and confirm the prior commit before retrying
  2. depend on the model remembering a prior value forever
  3. blindly resubmit the same write after every timeout
  4. infer tool activity from the final natural-language answer
  5. record the tool name, permitted inputs, outcome, and task identifier in a hook
  6. persist authoritative task facts and artifact IDs outside ephemeral conversation text

Explanation

Correct Answers

A:

For a merchant support assistant, side-effecting operations need deduplication against timeouts and repeated messages, which directly establishes that repeated delivery of one action request cannot create duplicate writes; the separate requirement that every high-impact tool invocation produces an audit event is handled by a different action.

E:

For a merchant support assistant, runtime instrumentation observes actual proposed or completed tool activity, which directly establishes that every high-impact tool invocation produces an audit event; the separate requirement that important workflow state survives context compression or process restarts is handled by a different action.

F:

For a merchant support assistant, external durable state can be reloaded and checked when the session window changes, which directly establishes that important workflow state survives context compression or process restarts; the separate requirement that repeated delivery of one action request cannot create duplicate writes is handled by a different action.

Incorrect Answers

B:

For a merchant support assistant, context limits and summarization can lose exact identifiers, so this option cannot establish that important workflow state survives context compression or process restarts; correctly addressing repeated delivery of one action request cannot create duplicate writes elsewhere does not repair that deficiency.

C:

For a merchant support assistant, the first attempt might have committed despite a missing acknowledgment, so this option cannot establish that repeated delivery of one action request cannot create duplicate writes; correctly addressing every high-impact tool invocation produces an audit event elsewhere does not repair that deficiency.

D:

For a merchant support assistant, a summary can omit failed calls or delegated actions, so this option cannot establish that every high-impact tool invocation produces an audit event; correctly addressing important workflow state survives context compression or process restarts elsewhere does not repair that deficiency.

Question 832

While preparing a customer refund workflow for deployment, engineers must ensure that a transient upstream outage is retried safely; they must also ensure that a tool result includes enough fields to support audit and follow-on actions. Which combination best satisfies those requirements?

  1. retry access-denied and invalid-input errors indefinitely; and return structured identifiers, status, and provenance with the data
  2. apply a bounded backoff only to classified retryable errors; and return only a friendly summary with no source identifier
  3. retry access-denied and invalid-input errors indefinitely; and return only a friendly summary with no source identifier
  4. apply a bounded backoff only to classified retryable errors; and return structured identifiers, status, and provenance with the data

Explanation

Correct Answer

D:

In a customer refund workflow, transient failures can heal without re-running permanently invalid requests; alongside this, machine-readable outputs let downstream stages validate exactly what was retrieved, satisfying the distinct requirements that a transient upstream outage is retried safely and that a tool result includes enough fields to support audit and follow-on actions.

Incorrect Answers

A:

In a customer refund workflow, machine-readable outputs let downstream stages validate exactly what was retrieved, but permanent failures require a fix or escalation rather than repetition; therefore the separate requirement that a transient upstream outage is retried safely would remain unsatisfied.

B:

In a customer refund workflow, transient failures can heal without re-running permanently invalid requests, but a paraphrase hides the record needed for verification or follow-up; therefore the separate requirement that a tool result includes enough fields to support audit and follow-on actions would remain unsatisfied.

C:

In a customer refund workflow, permanent failures require a fix or escalation rather than repetition and a paraphrase hides the record needed for verification or follow-up; the design would fail both conditions: a transient upstream outage is retried safely and a tool result includes enough fields to support audit and follow-on actions.

Question 833

A team operating a structured report conversion service wants to establish two separate behaviors: a machine consumer receives a schema-compliant JSON object; in addition, offline extraction cost is controlled without missing a service-level deadline. Which plan implements both?

  1. use supported structured JSON output with a declared schema; and select the lowest-cost async path even for strict real-time actions
  2. use supported structured JSON output with a declared schema; and compare batch turnaround with the workload's time requirements
  3. rely only on a sentence requesting JSON with no validation; and compare batch turnaround with the workload's time requirements
  4. rely only on a sentence requesting JSON with no validation; and select the lowest-cost async path even for strict real-time actions

Explanation

Correct Answer

B:

In a structured report conversion service, constrained output enforces parseable structure and required field types at generation; alongside this, asynchronous savings are appropriate only when delayed completion is acceptable, satisfying the distinct requirements that a machine consumer receives a schema-compliant JSON object and that offline extraction cost is controlled without missing a service-level deadline.

Incorrect Answers

A:

In a structured report conversion service, constrained output enforces parseable structure and required field types at generation, but meeting a live deadline can matter more than per-request savings; therefore the separate requirement that offline extraction cost is controlled without missing a service-level deadline would remain unsatisfied.

C:

In a structured report conversion service, asynchronous savings are appropriate only when delayed completion is acceptable, 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.

D:

In a structured report conversion service, prompt-only formatting can still produce malformed or incomplete results and meeting a live deadline can matter more than per-request savings; the design would fail both conditions: a machine consumer receives a schema-compliant JSON object and offline extraction cost is controlled without missing a service-level deadline.

Question 834

An incident postmortem for a pull-request review pipeline requires controls so that the coordinator can identify which subagent produced a broken artifact and that multiple draft branches are merged without contradictory statements. Which paired remedy covers both failure modes?

  1. propagate task IDs, error codes, and correlation references; and create a reconciliation stage that checks citations and resolves overlaps
  2. propagate task IDs, error codes, and correlation references; and concatenate every agent's conclusion into the final report
  3. replace all nested errors with a generic coordinator failure; and create a reconciliation stage that checks citations and resolves overlaps
  4. replace all nested errors with a generic coordinator failure; and concatenate every agent's conclusion into the final report

Explanation

Correct Answer

A:

In a pull-request review pipeline, tracing execution lineage helps route the incident to the right failing component; alongside this, synthesis must select mutually consistent claims with defensible evidence, satisfying the distinct requirements that the coordinator can identify which subagent produced a broken artifact and that multiple draft branches are merged without contradictory statements.

Incorrect Answers

B:

In a pull-request review pipeline, tracing execution lineage helps route the incident to the right failing component, but raw merger preserves disagreements and duplicated statements; therefore the separate requirement that multiple draft branches are merged without contradictory statements would remain unsatisfied.

C:

In a pull-request review pipeline, synthesis must select mutually consistent claims with defensible evidence, but the original failing operation becomes opaque; therefore the separate requirement that the coordinator can identify which subagent produced a broken artifact would remain unsatisfied.

D:

In a pull-request review pipeline, the original failing operation becomes opaque and raw merger preserves disagreements and duplicated statements; the design would fail both conditions: the coordinator can identify which subagent produced a broken artifact and multiple draft branches are merged without contradictory statements.

Question 835

A readiness review for a multi-source competitor research system requires that an alternate implementation is explored without rewriting the original branch; that only one approved write tool is callable in a sensitive stage; and that sensitive tool calls are denied before they reach an executor. Which THREE actions directly implement those distinct requirements? Choose THREE.

  1. register a PreToolUse hook that checks the operation against policy
  2. write a stronger instruction in the system prompt
  3. fork the existing session into a separate line of exploration
  4. restrict the stage's allowed tool set and verify permissions in the executor
  5. let the model select from a broad global list of tools
  6. continue changing the original session as though it were an isolated experiment

Explanation

Correct Answers

A:

For a multi-source competitor research system, pre-execution interception can reject a disallowed call rather than relying on post-hoc advice, which directly establishes that sensitive tool calls are denied before they reach an executor; the separate requirement that an alternate implementation is explored without rewriting the original branch is handled by a different action.

C:

For a multi-source competitor research system, a fork supports competing paths while preserving the original session history, which directly establishes that an alternate implementation is explored without rewriting the original branch; the separate requirement that only one approved write tool is callable in a sensitive stage is handled by a different action.

D:

For a multi-source competitor research system, 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 sensitive tool calls are denied before they reach an executor is handled by a different action.

Incorrect Answers

B:

For a multi-source competitor research system, an instruction alone does not provide deterministic execution-time authorization, so this option cannot establish that sensitive tool calls are denied before they reach an executor; correctly addressing an alternate implementation is explored without rewriting the original branch elsewhere does not repair that deficiency.

E:

For a multi-source competitor research system, 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 sensitive tool calls are denied before they reach an executor elsewhere does not repair that deficiency.

F:

For a multi-source competitor research system, the experiment then shares and alters the active thread's direction, so this option cannot establish that an alternate implementation is explored without rewriting the original branch; correctly addressing only one approved write tool is callable in a sensitive stage elsewhere does not repair that deficiency.

Question 836

An audit of a contract clause extraction workflow asks how to make sure that an MCP tool failure can be traced across systems. Which implementation should be selected?

  1. propagate a stable correlation ID and machine-readable error code
  2. mark the tool result as an error and supply structured failure details
  3. include a retryable classification and bounded retry advice
  4. replace every failure with the same unstructured unknown error
  5. return a non-retryable validation error with the field and expected constraint

Explanation

Correct Answer

A:

For a contract clause extraction workflow, cross-service identifiers connect the user's symptom to upstream logs without exposing secrets; this directly establishes that an MCP tool failure can be traced across systems instead of relying on an unrelated workflow control.

Incorrect Answers

B:

Although explicit error status separates failed execution from valid data content, that only supports the distinct goal that a failed MCP operation is visible as an error to the client, not the requirement that an MCP tool failure can be traced across systems in a contract clause extraction workflow.

C:

Although typed transient failures allow backoff without treating permanent errors the same way, that only supports the distinct goal that temporary service faults can be retried selectively, not the requirement that an MCP tool failure can be traced across systems in a contract clause extraction workflow.

D:

In a contract clause extraction workflow, undifferentiated errors prevent meaningful triage; as a result, the stated requirement that an MCP tool failure can be traced across systems would still not be met.

E:

Although field-specific feedback lets the caller fix the input before resubmission, that only supports the distinct goal that invalid parameters lead to a clear correction rather than a blind retry, not the requirement that an MCP tool failure can be traced across systems in a contract clause extraction workflow.

Question 837

An incident postmortem for a structured case-file ingestion workflow requires controls so that a failed retrieval agent does not masquerade as having found no matches and that a long workflow preserves confirmed facts separately from speculation. Which paired remedy covers both failure modes?

  1. return a typed failure status with its origin to the coordinator; and mark verified, user-reported, and unknown state explicitly
  2. convert every retrieval failure into an empty list; and mark verified, user-reported, and unknown state explicitly
  3. return a typed failure status with its origin to the coordinator; and combine guesses and verified attributes in one unqualified summary
  4. convert every retrieval failure into an empty list; and combine guesses and verified attributes in one unqualified summary

Explanation

Correct Answer

A:

In a structured case-file ingestion workflow, an operational error must remain distinguishable from a valid empty result; alongside this, epistemic labels stop a tentative suggestion becoming a confirmed action parameter, satisfying the distinct requirements that a failed retrieval agent does not masquerade as having found no matches and that a long workflow preserves confirmed facts separately from speculation.

Incorrect Answers

B:

In a structured case-file ingestion workflow, epistemic labels stop a tentative suggestion becoming a confirmed action parameter, but the final report could incorrectly claim no sources exist; therefore the separate requirement that a failed retrieval agent does not masquerade as having found no matches would remain unsatisfied.

C:

In a structured case-file ingestion workflow, an operational error must remain distinguishable from a valid empty result, but downstream operations may rely on an assumption as though it were checked; therefore the separate requirement that a long workflow preserves confirmed facts separately from speculation would remain unsatisfied.

D:

In a structured case-file ingestion workflow, the final report could incorrectly claim no sources exist and downstream operations may rely on an assumption as though it were checked; the design would fail both conditions: a failed retrieval agent does not masquerade as having found no matches and a long workflow preserves confirmed facts separately from speculation.

Question 838

In a shared-library improvement effort, the immediate design requirement is that secrets are not embedded in a shared MCP setup. Which change most directly establishes that behavior?

  1. place long-lived access tokens directly in .mcp.json
  2. verify server connection, transport, and exposed tool availability
  3. inject credentials through approved environment or secret-management mechanisms
  4. configure a compatible MCP server and expose its declared tools to the client

Explanation

Correct Answer

C:

For a shared-library improvement effort, separating credentials from versioned configuration limits accidental disclosure; this directly establishes that secrets are not embedded in a shared MCP setup instead of relying on an unrelated workflow control.

Incorrect Answers

A:

In a shared-library improvement effort, repository history can expose tokens to everyone with code access; as a result, the stated requirement that secrets are not embedded in a shared MCP setup would still not be met.

B:

Although tool discovery depends on a live configured integration, not just the prompt wording, that only supports the distinct goal that a missing MCP capability is diagnosed before changing prompts, not the requirement that secrets are not embedded in a shared MCP setup in a shared-library improvement effort.

D:

Although MCP bridges a client to provider-defined capabilities rather than inventing a Claude built-in, that only supports the distinct goal that the assistant can use external service capabilities via MCP, not the requirement that secrets are not embedded in a shared MCP setup in a shared-library improvement effort.

Question 839

An architecture review of a monorepo feature modernization project finds two missing guarantees: a shared skill can take a supplied target name or file path; long project guidance is divided into maintainable source files. What two-part change closes both gaps?

  1. copy a separate static instruction file for every target path; and use CLAUDE.md imports to organize referenced instructions
  2. define how the skill accepts and uses invocation arguments; and duplicate full instruction paragraphs in every directory
  3. define how the skill accepts and uses invocation arguments; and use CLAUDE.md imports to organize referenced instructions
  4. copy a separate static instruction file for every target path; and duplicate full instruction paragraphs in every directory

Explanation

Correct Answer

C:

In a monorepo feature modernization project, parameterized workflows apply one reviewed procedure to different resources without hardcoding targets; alongside this, modular imports keep a short entry point while preserving reviewed details in separate files, satisfying the distinct requirements that a shared skill can take a supplied target name or file path and that long project guidance is divided into maintainable source files.

Incorrect Answers

A:

In a monorepo feature modernization project, modular imports keep a short entry point while preserving reviewed details in separate files, but duplicated procedures are costly to maintain and can diverge; therefore the separate requirement that a shared skill can take a supplied target name or file path would remain unsatisfied.

B:

In a monorepo feature modernization project, parameterized workflows apply one reviewed procedure to different resources without hardcoding targets, 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.

D:

In a monorepo feature modernization project, duplicated procedures are costly to maintain and can diverge and copying guidance encourages drift when policies change; the design would fail both conditions: a shared skill can take a supplied target name or file path and long project guidance is divided into maintainable source files.

Question 840

Production readiness for a monorepo testing overhaul depends on ensuring that ambiguous requirements are resolved before a destructive migration and that a new agent gets only durable context from a completed job. Select the most appropriate combined approach.

  1. make assumptions and migrate production files immediately; and initialize a fresh session with a verified structured summary
  2. make assumptions and migrate production files immediately; and paste a full historical transcript into every new session
  3. clarify scope and acceptance criteria while planning; and initialize a fresh session with a verified structured summary
  4. clarify scope and acceptance criteria while planning; and paste a full historical transcript into every new session

Explanation

Correct Answer

C:

In a monorepo testing overhaul, a reviewed plan should resolve unknown targets and rollback expectations before writes; alongside this, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, satisfying the distinct requirements that ambiguous requirements are resolved before a destructive migration and that a new agent gets only durable context from a completed job.

Incorrect Answers

A:

In a monorepo testing overhaul, a bounded handoff transfers necessary facts without carrying discarded trial-and-error context, but guessed intent can create costly irreversible changes; therefore the separate requirement that ambiguous requirements are resolved before a destructive migration would remain unsatisfied.

B:

In a monorepo testing overhaul, guessed intent can create costly irreversible changes and irrelevant turns can consume context and revive outdated assumptions; the design would fail both conditions: ambiguous requirements are resolved before a destructive migration and a new agent gets only durable context from a completed job.

D:

In a monorepo testing overhaul, a reviewed plan should resolve unknown targets and rollback expectations before writes, but irrelevant turns can consume context and revive outdated assumptions; therefore the separate requirement that a new agent gets only durable context from a completed job would remain unsatisfied.

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