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

Question 90

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

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

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

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

B:

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

C:

In a compliance interpretation research team, conversation continuity is not a replacement for live access control or fresh tool state, but the unanswered tool uses remain unresolved and later reasoning loses evidence; therefore the separate requirement that several requested client tools are returned in one response would remain unsatisfied.

Question 91

Production readiness for a payment microservice repository depends on ensuring that an alternate implementation is explored without rewriting the original branch and that the repository assistant discovers filenames matching a pattern. Select the most appropriate combined approach.

  1. continue changing the original session as though it were an isolated experiment; and search entire file contents with Grep to find paths by naming pattern
  2. implement only use Glob to locate candidate paths; make no corresponding change for the first requirement
  3. fork the existing session into a separate line of exploration; and use Glob to locate candidate paths
  4. continue changing the original session as though it were an isolated experiment; and use Glob to locate candidate paths
  5. fork the existing session into a separate line of exploration; and search entire file contents with Grep to find paths by naming pattern

Explanation

Correct Answer

C:

In a payment microservice repository, a fork supports competing paths while preserving the original session history; alongside this, path globbing finds files by names and directory structure before content inspection, satisfying the distinct requirements that an alternate implementation is explored without rewriting the original branch and that the repository assistant discovers filenames matching a pattern.

Incorrect Answers

A:

In a payment microservice repository, the experiment then shares and alters the active thread's direction and content search answers a different question and may miss empty files; the design would fail both conditions: an alternate implementation is explored without rewriting the original branch and the repository assistant discovers filenames matching a pattern.

B:

In a payment microservice repository, path globbing finds files by names and directory structure before content inspection, but the independent mechanism for the other criterion is absent: a fork supports competing paths while preserving the original session history; as written, the design does not ensure that an alternate implementation is explored without rewriting the original branch.

D:

In a payment microservice repository, path globbing finds files by names and directory structure before content inspection, but the experiment then shares and alters the active thread's direction; therefore the separate requirement that an alternate implementation is explored without rewriting the original branch would remain unsatisfied.

E:

In a payment microservice repository, a fork supports competing paths while preserving the original session history, but content search answers a different question and may miss empty files; therefore the separate requirement that the repository assistant discovers filenames matching a pattern would remain unsatisfied.

Question 92

In a contract clause extraction workflow, the acceptance criteria require that a paused server-side tool loop can continue without losing work and that conflicting sources are not silently flattened into one answer. Which paired implementation meets both?

  1. restart from a blank conversation whenever pause_turn occurs; and report the disagreement and explain evidence quality or recency
  2. restart from a blank conversation whenever pause_turn occurs; and choose one assertion and omit the contradiction without investigation
  3. preserve the paused assistant response and resume the server-tool turn; and choose one assertion and omit the contradiction without investigation
  4. preserve the paused assistant response and resume the server-tool turn; and report the disagreement and explain evidence quality or recency

Explanation

Correct Answer

D:

In a contract clause extraction workflow, pause_turn indicates an internal tool loop pause rather than a user-facing conclusion; alongside this, explicit conflicts preserve uncertainty rather than manufacturing unanimity, satisfying the distinct requirements that a paused server-side tool loop can continue without losing work and that conflicting sources are not silently flattened into one answer.

Incorrect Answers

A:

In a contract clause extraction workflow, explicit conflicts preserve uncertainty rather than manufacturing unanimity, but dropping tool context can repeat work and omit intermediate evidence; therefore the separate requirement that a paused server-side tool loop can continue without losing work would remain unsatisfied.

B:

In a contract clause extraction workflow, dropping tool context can repeat work and omit intermediate evidence and suppressed disagreement creates false confidence; the design would fail both conditions: a paused server-side tool loop can continue without losing work and conflicting sources are not silently flattened into one answer.

C:

In a contract clause extraction workflow, pause_turn indicates an internal tool loop pause rather than a user-facing conclusion, but suppressed disagreement creates false confidence; therefore the separate requirement that conflicting sources are not silently flattened into one answer would remain unsatisfied.

Question 93

In a technical review of a service refactoring initiative, the architect must address the following constraints together: specialized agents work with only relevant permissions; a large investigation spans unrelated subsystems. Which change set is most defensible?

  1. define each subagent role and expose the minimum matching tools; and give every specialist the complete monorepo transcript
  2. give every subagent the coordinator's complete tool inventory; and delegate bounded subsystem searches and merge path-based findings
  3. give every subagent the coordinator's complete tool inventory; and give every specialist the complete monorepo transcript
  4. define each subagent role and expose the minimum matching tools; and delegate bounded subsystem searches and merge path-based findings

Explanation

Correct Answer

D:

In a service refactoring initiative, tool scoping shrinks both decision confusion and the blast radius of delegated actions; alongside this, subsystem partitioning permits parallel work without duplicating full repository context, satisfying the distinct requirements that specialized agents work with only relevant permissions and that a large investigation spans unrelated subsystems.

Incorrect Answers

A:

In a service refactoring initiative, tool scoping shrinks both decision confusion and the blast radius of delegated actions, but each branch pays the same large context cost and increases noise; therefore the separate requirement that a large investigation spans unrelated subsystems would remain unsatisfied.

B:

In a service refactoring initiative, subsystem partitioning permits parallel work without duplicating full repository context, but unneeded write or network tools expand risk without improving the specialist task; therefore the separate requirement that specialized agents work with only relevant permissions would remain unsatisfied.

C:

In a service refactoring initiative, unneeded write or network tools expand risk without improving the specialist task and each branch pays the same large context cost and increases noise; the design would fail both conditions: specialized agents work with only relevant permissions and a large investigation spans unrelated subsystems.

Question 94

When designing an internal developer coding workflow, the requirement is not satisfied unless a delegated skill should not fill the caller's active context and a missing MCP capability is diagnosed before changing prompts. Which implementation addresses the two independent conditions?

  1. configure the skill to run in an isolated forked context where supported; and verify server connection, transport, and exposed tool availability
  2. load all investigation steps into the same conversation by default; and increase the system prompt length to compensate for disconnected tools
  3. load all investigation steps into the same conversation by default; and verify server connection, transport, and exposed tool availability
  4. configure the skill to run in an isolated forked context where supported; and increase the system prompt length to compensate for disconnected tools

Explanation

Correct Answer

A:

In an internal developer coding workflow, a fork isolates exploratory work and returns a concise result to its caller; alongside this, tool discovery depends on a live configured integration, not just the prompt wording, satisfying the distinct requirements that a delegated skill should not fill the caller's active context and that a missing MCP capability is diagnosed before changing prompts.

Incorrect Answers

B:

In an internal developer coding workflow, the caller's window accumulates unnecessary intermediate details and a model cannot call a capability absent from its available tool registry; the design would fail both conditions: a delegated skill should not fill the caller's active context and a missing MCP capability is diagnosed before changing prompts.

C:

In an internal developer coding workflow, tool discovery depends on a live configured integration, not just the prompt wording, 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 an internal developer coding workflow, a fork isolates exploratory work and returns a concise result to its caller, 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.

Question 95

The release checklist for a mobile client bug-fix task explicitly checks that agents exchange outputs without losing important structure; it also checks that the agent executes tests and examines their exit status. What coordinated solution meets the checklist?

  1. define artifact schemas and handoff contracts between roles; and use Bash with an approved test command
  2. implement only define artifact schemas and handoff contracts between roles; make no corresponding change for the second requirement
  3. define artifact schemas and handoff contracts between roles; and inspect the test configuration only with Read and claim tests passed
  4. pass raw chat logs between every stage; and use Bash with an approved test command
  5. pass raw chat logs between every stage; and inspect the test configuration only with Read and claim tests passed

Explanation

Correct Answer

A:

In a mobile client bug-fix task, bounded interfaces make missing fields and incompatible assumptions visible; alongside this, the shell can run build tools and return execution feedback that Read cannot supply, satisfying the distinct requirements that agents exchange outputs without losing important structure and that the agent executes tests and examines their exit status.

Incorrect Answers

B:

In a mobile client bug-fix task, bounded interfaces make missing fields and incompatible assumptions visible, but the independent mechanism for the other criterion is absent: the shell can run build tools and return execution feedback that Read cannot supply; as written, the design does not ensure that the agent executes tests and examines their exit status.

C:

In a mobile client bug-fix task, bounded interfaces make missing fields and incompatible assumptions visible, but reading configuration does not execute a test suite; therefore the separate requirement that the agent executes tests and examines their exit status would remain unsatisfied.

D:

In a mobile client bug-fix task, the shell can run build tools and return execution feedback that Read cannot supply, but unstructured context is noisy and can obscure the decision fields; therefore the separate requirement that agents exchange outputs without losing important structure would remain unsatisfied.

E:

In a mobile client bug-fix task, unstructured context is noisy and can obscure the decision fields and reading configuration does not execute a test suite; the design would fail both conditions: agents exchange outputs without losing important structure and the agent executes tests and examines their exit status.

Question 96

For a tender-response data extractor, acceptance depends on demonstrating that a function call accepts only valid argument shapes. Which approach is the strongest fit?

  1. define the tool input schema, enable strict tool use where available, and validate inputs in the handler
  2. enforce the approved status enum with structured output and validate it in the consumer
  3. allow arbitrary keys and silently coerce incorrect types
  4. allow null in the field schema and define its semantics

Explanation

Correct Answer

A:

For a tender-response data extractor, strict tool inputs constrain generation, and handler validation provides a final enforceable argument boundary; this directly establishes that a function call accepts only valid argument shapes instead of relying on an unrelated workflow control.

Incorrect Answers

B:

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 function call accepts only valid argument shapes in a tender-response data extractor.

C:

In a tender-response data extractor, unvalidated coercion can change intended operations or silently drop important fields; as a result, the stated requirement that a function call accepts only valid argument shapes would still not be met.

D:

Although explicit nullable types distinguish genuine absence from empty or invented data, that only supports the distinct goal that a missing value is represented without fabricating a string, not the requirement that a function call accepts only valid argument shapes in a tender-response data extractor.

Question 97

Production readiness for a cross-platform application migration depends on ensuring that a delegated skill should not fill the caller's active context and that ambiguous requirements are resolved before a destructive migration. Select the most appropriate combined approach.

  1. implement only configure the skill to run in an isolated forked context where supported; make no corresponding change for the second requirement
  2. configure the skill to run in an isolated forked context where supported; and clarify scope and acceptance criteria while planning
  3. configure the skill to run in an isolated forked context where supported; and make assumptions and migrate production files immediately
  4. load all investigation steps into the same conversation by default; and clarify scope and acceptance criteria while planning
  5. load all investigation steps into the same conversation by default; and make assumptions and migrate production files immediately

Explanation

Correct Answer

B:

In a cross-platform application migration, a fork isolates exploratory work and returns a concise result to its caller; alongside this, a reviewed plan should resolve unknown targets and rollback expectations before writes, satisfying the distinct requirements that a delegated skill should not fill the caller's active context and that ambiguous requirements are resolved before a destructive migration.

Incorrect Answers

A:

In a cross-platform application migration, a fork isolates exploratory work and returns a concise result to its caller, but the independent mechanism for the other criterion is absent: a reviewed plan should resolve unknown targets and rollback expectations before writes; as written, the design does not ensure that ambiguous requirements are resolved before a destructive migration.

C:

In a cross-platform application migration, a fork isolates exploratory work and returns a concise result to its caller, but guessed intent can create costly irreversible changes; therefore the separate requirement that ambiguous requirements are resolved before a destructive migration would remain unsatisfied.

D:

In a cross-platform application migration, a reviewed plan should resolve unknown targets and rollback expectations before writes, 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.

E:

In a cross-platform application migration, the caller's window accumulates unnecessary intermediate details and guessed intent can create costly irreversible changes; the design would fail both conditions: a delegated skill should not fill the caller's active context and ambiguous requirements are resolved before a destructive migration.

Question 98

In a technical review of a subscription support service, the architect must address the following constraints together: critical account identifiers survive a long support conversation; quality drift is detected after a workflow launches. Which change set is most defensible?

  1. rely only on a conversational summary of the earliest turns; and sample outcomes for periodic human QA against known criteria
  2. rely only on a conversational summary of the earliest turns; and validate one development example and never review production output
  3. store verified IDs and decisions in an explicit structured case-facts record; and sample outcomes for periodic human QA against known criteria
  4. store verified IDs and decisions in an explicit structured case-facts record; and validate one development example and never review production output

Explanation

Correct Answer

C:

In a subscription support service, durable structured state prevents essential exact values being lost during summarization; alongside this, ongoing calibration can reveal changed input distributions and silent error patterns, satisfying the distinct requirements that critical account identifiers survive a long support conversation and that quality drift is detected after a workflow launches.

Incorrect Answers

A:

In a subscription support service, ongoing calibration can reveal changed input distributions and silent error patterns, but compression can omit or alter identifiers that later actions require; therefore the separate requirement that critical account identifiers survive a long support conversation would remain unsatisfied.

B:

In a subscription support service, compression can omit or alter identifiers that later actions require and production inputs may differ from the initial examples; the design would fail both conditions: critical account identifiers survive a long support conversation and quality drift is detected after a workflow launches.

D:

In a subscription support service, durable structured state prevents essential exact values being lost during summarization, but production inputs may differ from the initial examples; therefore the separate requirement that quality drift is detected after a workflow launches would remain unsatisfied.

Question 99

For a pull-request regression detection job, acceptance depends on demonstrating that regressions introduced during refinement are detected and fixed. Which approach is the strongest fit?

  1. restore or revise the problematic change and retest affected paths
  2. keep layering patches without checking the last stable behavior
  3. inspect failure evidence and revise the smallest relevant change
  4. iterate with focused diffs rather than wholesale regeneration

Explanation

Correct Answer

A:

For a pull-request regression detection job, iteration includes detecting regressions and returning to a passing state; this directly establishes that regressions introduced during refinement are detected and fixed instead of relying on an unrelated workflow control.

Incorrect Answers

B:

In a pull-request regression detection job, cumulative changes can bury the source of failure; as a result, the stated requirement that regressions introduced during refinement are detected and fixed would still not be met.

C:

Although test-driven feedback pinpoints a specific unmet behavior for the next iteration, that only supports the distinct goal that a patch that fails regression tests is diagnosed and corrected, not the requirement that regressions introduced during refinement are detected and fixed in a pull-request regression detection job.

D:

Although narrow changes are easier to test and evaluate against explicit requirements, that only supports the distinct goal that the review produces a small, auditable patch, not the requirement that regressions introduced during refinement are detected and fixed in a pull-request regression detection job.

Question 100

Production readiness for a returns-and-billing assistant depends on ensuring that a corrected attempt preserves a record of prior validation findings and that source identity survives multi-agent research handoffs. Select the most appropriate combined approach.

  1. retain the original source, response version, and retry feedback; and carry citation identifiers and retrieval context through synthesis
  2. replace all earlier outputs without recording the validation history; and strip all citation fields before sending the writer its inputs
  3. retain the original source, response version, and retry feedback; and strip all citation fields before sending the writer its inputs
  4. replace all earlier outputs without recording the validation history; and carry citation identifiers and retrieval context through synthesis

Explanation

Correct Answer

A:

In a returns-and-billing assistant, traceable attempts allow auditors to distinguish correction from silent overwrite; alongside this, provenance metadata must remain attached when intermediate summaries are merged, satisfying the distinct requirements that a corrected attempt preserves a record of prior validation findings and that source identity survives multi-agent research handoffs.

Incorrect Answers

B:

In a returns-and-billing assistant, the reason for a changed value becomes untraceable and the writer cannot reliably reconstruct which source supports each conclusion; the design would fail both conditions: a corrected attempt preserves a record of prior validation findings and source identity survives multi-agent research handoffs.

C:

In a returns-and-billing assistant, traceable attempts allow auditors to distinguish correction from silent overwrite, but the writer cannot reliably reconstruct which source supports each conclusion; therefore the separate requirement that source identity survives multi-agent research handoffs would remain unsatisfied.

D:

In a returns-and-billing assistant, provenance metadata must remain attached when intermediate summaries are merged, but the reason for a changed value becomes untraceable; therefore the separate requirement that a corrected attempt preserves a record of prior validation findings would remain unsatisfied.

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