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

Question 460

A team maintains path-aware architecture conventions in Claude Code. A critical write restriction is written only as path-specific prose. Which mechanism should be selected?

  1. Constrain edit permissions to approved paths at the execution layer
  2. Attach the review procedure to infrastructure configuration patterns
  3. Keep shared guidance in one place and scoped exceptions explicitly narrow
  4. Revise path patterns and test their effective selection
  5. Give mobile and server trees distinct scoped guidance

Explanation

Correct Answer

A:

Scoped instruction text improves intent but does not prevent a capable tool from writing elsewhere when misused. Here it serves the explicit need to back the restriction with a real filesystem or tool guard without adding a separate unverified inference.

Incorrect Answers

B:

A path-aware rule gives extra caution where necessary without slowing unrelated text edits; the benefit is tied to only infrastructure-as-code files require a plan-before-change policy. It is not the immediate control for the need to back the restriction with a real filesystem or tool guard.

C:

For the separate situation where a scoped rule repeats a contradictory general rule verbatim, redundant copies can drift; exceptions should state exactly what changes for a subset of files; the current task is to back the restriction with a real filesystem or tool guard.

D:

Rule files are not intelligent about renamed folders; matching must be maintained alongside structural refactors; it is a safeguard for a new package directory does not match the existing rules, not the specific situation described: a critical write restriction is written only as path-specific prose.

E:

This choice is relevant when the mobile app follows a different package layout from the server; relevant architecture instructions reduce accidental cross-project assumptions when a monorepo contains multiple build systems. Here, however, a critical write restriction is written only as path-specific prose.

Question 461

A code review automation runs Claude Code on inbound pull requests. A test suite is failing and the team wants diagnosis only. What should be implemented at the appropriate boundary?

  1. Inspect tainted inputs, query construction, and existing parameterization
  2. Run allowed checks and inspect logs before proposing edits
  3. Use an interview or planning step to collect expected behavior
  4. Switch from review to authorized bounded editing and validation

Explanation

Correct Answer

B:

Diagnostic evidence is needed to locate the cause; granting automatic write access in the discovery phase increases change risk.

Incorrect Answers

A:

For the separate situation where a reviewer finds a potential SQL-injection path in an unfamiliar module, security findings require traceable evidence; a pattern match alone may yield a false positive or overlook mitigations; the current task is to keep the initial pass observational.

C:

Undefined success conditions make a code change hard to test; targeted questions can establish the missing contract; it is a safeguard for an agent is asked to review a feature without knowing its acceptance criteria, not the specific situation described: a test suite is failing and the team wants diagnosis only.

D:

Separation between analysis and implementation gives the maintainer control over when automated modifications occur; the benefit is tied to a human explicitly requests a patch after reviewing generated suggestions. It is not the immediate control for the need to keep the initial pass observational.

Question 462

A research pipeline emits structured literature reviews. A publisher needs to know which assertions were repaired automatically. Which option best meets the operational need?

  1. Check claims against retrieved sources and reject unsupported assertions
  2. Require the base population or flag the statistic as incomplete
  3. Resolve citation metadata and compare it with the claimed title and authors
  4. Record initial failures, corrected fields, and validator outcomes

Explanation

Correct Answer

D:

A repair trail makes changes auditable and helps identify extraction defects hidden by a final clean object. The relevant requirement is to retain validation and correction provenance, and this measure operates at that decision point.

Incorrect Answers

A:

For the separate situation where the model keeps producing unsupported claims despite clean JSON, schema enforcement is not fact checking; a reviewer must compare meaning with evidence rather than regenerate well-formed guesses; the current task is to retain validation and correction provenance.

B:

A number without its denominator can be misleading; semantic validation must check whether the claim is interpretable; it is a safeguard for a summarized study reports a percentage without a denominator, not the specific situation described: a publisher needs to know which assertions were repaired automatically.

C:

A plausible-looking identifier can be factually wrong; checking external metadata tests referential truth beyond structure; the benefit is tied to a citation looks valid but links to a different paper title. It is not the immediate control for the need to retain validation and correction provenance.

Question 463

An operations team monitors an agent-based customer workflow in production. A production incident cannot be reproduced because tool outputs changed since execution. What is the most appropriate design choice?

  1. Record versions, response digests, and safe replay artifacts for important external results
  2. Instrument fan-out, join, and worker durations separately
  3. Verify the expected task-graph completion states before marking the request successful
  4. Correlate model turns, tool requests, task IDs, and tool outcomes in structured traces

Explanation

Correct Answer

A:

A stable record ties decisions to the data actually observed while avoiding the assumption that a live tool will return the same content later.

Incorrect Answers

B:

Per-stage timing shows whether concurrency removes a real bottleneck or merely moves latency to a saturated shared service; it is a safeguard for the team wants to compare latency of serial and parallel research designs, not the specific situation described: a production incident cannot be reproduced because tool outputs changed since execution.

C:

A polished model response is not proof that required delegated checks completed; orchestration state supplies that guarantee; the benefit is tied to a final reply is fluent although a required specialist never ran. It is not the immediate control for the need to retain reproducible evidence references.

D:

This choice is relevant when an agent makes repeated tool calls but the trace does not show why each was chosen; end-to-end correlation reveals the sequence leading to a failure without relying on a final narrative that may omit intermediate decisions. Here, however, a production incident cannot be reproduced because tool outputs changed since execution.

Question 464

An organization publishes MCP tools for searching internal technical documentation. Two tools share a capability, but one is optimized for exact identifier lookups. Which response is most reliable?

  1. Specify its corpus, query shape, and result guarantees in the description
  2. Document optional fields, cursor behavior, and what confidence actually represents
  3. Document that search outputs are excerpts with source references and may need follow-up reads
  4. Describe deterministic lookup versus semantic search use cases explicitly

Explanation

Correct Answer

D:

A direct identifier lookup gives precise retrieval when a key is known; embedding search is better for conceptual matching, not exact ID verification.

Incorrect Answers

A:

This choice is relevant when a tool named query has no indication of which index it searches; model selection depends on clear capability metadata; an opaque name leaves the assistant guessing which source will answer the user's question. Here, however, two tools share a capability, but one is optimized for exact identifier lookups.

B:

For the separate situation where a results object has optional confidence and pagination fields, typed, well-described results let the agent distinguish absent values from negative findings and paginate without assumptions; the current task is to route exact-match queries to the appropriate tool.

C:

An explicit limitation discourages Claude from treating a truncated hit as authoritative coverage of a whole document; the benefit is tied to a semantic-search tool returns ranked snippets that may not be complete documents. It is not the immediate control for the need to route exact-match queries to the appropriate tool.

Question 465

A document-processing agent decides whether to retry failed MCP calls. A validator rejects a confidence value outside its supported range. What should the team do to resolve this particular gap?

  1. Treat missing approval as a policy precondition requiring escalation
  2. Return a field-level constraint violation for the caller to repair
  3. Return a password-protection status rather than a fabricated empty conversion
  4. Use an operation ID to query authoritative completion status
  5. Use retry-aware error metadata with capped exponential backoff

Explanation

Correct Answer

B:

A type or range error requires argument correction, not infrastructure backoff or an alternate source search. For the stated case, the check is whether the system can correct a deterministic schema mismatch; this approach supplies that control.

Incorrect Answers

A:

Approval cannot be manufactured by model retries; the workflow must obtain an authorized decision outside the model; the benefit is tied to a tool reports that the user's approval is missing for a payout. It is not the immediate control for the need to correct a deterministic schema mismatch.

C:

A clear input limitation enables the user to provide an accessible document through approved channels; repeated conversion is ineffective; it is a safeguard for an XML converter receives a password-protected file it cannot read, not the specific situation described: a validator rejects a confidence value outside its supported range.

D:

For the separate situation where a network timeout leaves the outcome of a state-changing operation uncertain, retrying a financial mutation blindly can duplicate a transaction; checking durable state is safer than inferring failure from a timeout; the current task is to correct a deterministic schema mismatch.

E:

This choice is relevant when a service responds with a temporary capacity error and a recommended wait; temporary saturation may clear; paced retries can recover without causing a synchronized load spike. Here, however, a validator rejects a confidence value outside its supported range.

Question 466

An invoice-extraction team builds reliable prompting for standardized records. The same invoice is processed by multiple teams with different field naming. Which control is most directly relevant?

  1. Require a null or explicit missing status instead of an invented identifier
  2. Define a shared field glossary and mapping rules before generation
  3. Define total, subtotal, tax, and discount semantics with examples
  4. Require page or span references for important extracted fields

Explanation

Correct Answer

B:

A stable schema prevents downstream systems from interpreting identical content under inconsistent attribute names.

Incorrect Answers

A:

Missing fields should remain missing in the structured output; completeness must not be achieved by hallucinating values; it is a safeguard for a document is missing a purchase-order number, not the specific situation described: the same invoice is processed by multiple teams with different field naming.

C:

Financial field names need precise meanings; otherwise valid-looking numbers can be assigned to the wrong ledger fields; the benefit is tied to the prompt says 'extract the total' without distinguishing gross and net amounts. It is not the immediate control for the need to establish one canonical output contract.

D:

For the separate situation where a reviewer needs a confidence explanation tied to source text, evidence-linked extraction allows downstream review to inspect the actual text behind uncertain or disputed values; the current task is to establish one canonical output contract.

Question 467

A repository team decides how to package MCP integrations for collaboration. A team wants to discover available server tools without invoking any of them. How should the workflow be adjusted?

  1. Review changed schemas and run integration checks before team rollout
  2. Use a local-only MCP definition rather than committing it to shared project settings
  3. Keep the project-scoped server definition under version control without secrets
  4. List approved tools and schemas before requesting tool calls

Explanation

Correct Answer

D:

Discovery can inform architecture and permission review while avoiding side effects associated with actual operation execution.

Incorrect Answers

A:

For the separate situation where a server package is upgraded and its tool arguments change, server version changes can break tool calls even when connection setup succeeds, so schema compatibility requires testing; the current task is to separate capability discovery from execution.

B:

Local scope prevents unreviewed capabilities from silently appearing in every contributor's workspace; the benefit is tied to a developer tests an experimental local server that colleagues must not use. It is not the immediate control for the need to separate capability discovery from execution.

C:

This choice is relevant when a project-wide tool server has been approved for every contributor to that repository; versioned project configuration gives contributors consistent definitions while leaving credentials outside shared files. Here, however, a team wants to discover available server tools without invoking any of them.

Question 468

A research agent must explore conflicting hypotheses with limited resources. An expensive analysis path has low expected value after a reliable answer is found. Which implementation decision is the best fit?

  1. Enumerate documents and allocate bounded extraction tasks to each
  2. Allow a bounded agent loop to generate follow-ups from validated findings
  3. Stop additional investigation once evidence suffices and obligations are satisfied
  4. Track completed task intents and reuse valid existing findings

Explanation

Correct Answer

C:

A clear sufficiency condition avoids waste while preserving any mandatory validation or approval steps. For the stated case, the check is whether the system can introduce value-based stopping criteria; this approach supplies that control.

Incorrect Answers

A:

This choice is relevant when the search space has a fixed list of ten known documents; a finite inventory can be processed predictably without an autonomous planner deciding what to look at next. Here, however, an expensive analysis path has low expected value after a reliable answer is found.

B:

Uncertain discovery benefits from adaptive next steps; the budget and tools still require host control; the benefit is tied to an initial article may reveal unknown organizations that require follow-up queries. It is not the immediate control for the need to introduce value-based stopping criteria.

D:

For the separate situation where the coordinator keeps asking new workers for the same question, deduplicating work prevents an apparent multi-agent design from simply repeating the same investigation; the current task is to introduce value-based stopping criteria.

Question 469

A CI pipeline runs Claude Code non-interactively for pull-request review. A CI task might continue indefinitely under repeated tool calls. What should the architect specify in the design?

  1. Run Claude Code in noninteractive print mode with a bounded task prompt
  2. Run in a restricted sandbox with minimal tokens and no secret-bearing privileged steps
  3. Set job timeout, token or iteration budgets, and explicit failure behavior
  4. Request a defined JSON output format and validate its schema in the pipeline

Explanation

Correct Answer

C:

CI should fail visibly when budgets are exhausted rather than hang or silently return partial success. This matches the workflow goal to bound automated execution time and resources rather than introducing an unrelated action.

Incorrect Answers

A:

This choice is relevant when the build runner has no interactive terminal for answering Claude prompts; a headless execution path avoids UI expectations and lets CI capture the completed response as an artifact. Here, however, a CI task might continue indefinitely under repeated tool calls.

B:

Pull-request content is untrusted input; prompt instructions cannot substitute for runner isolation or secret scoping; it is a safeguard for a pull request from an untrusted fork contains instructions to exfiltrate secrets, not the specific situation described: a CI task might continue indefinitely under repeated tool calls.

D:

Structured output supports deterministic gating and avoids brittle parsing of free-form review prose; the benefit is tied to a downstream CI job must parse the review result reliably. It is not the immediate control for the need to bound automated execution time and resources.

Question 470

A team uses Claude Code to implement a business-rule change. A review discovers the acceptance criteria changed mid-implementation. Which change most directly addresses this condition?

  1. Request the exact states and exception cases before coding
  2. Run the reproducer, inspect the cause, then apply a minimal change
  3. Remove incidental changes and present a focused diff
  4. Update tests and plan based on the approved revised criteria
  5. Validate the changed module and affected integration boundaries

Explanation

Correct Answer

D:

Continuing with an obsolete contract can produce polished but wrong code; the new requirements must govern validation.

Incorrect Answers

A:

This choice is relevant when a ticket uses the word 'active' without defining qualifying account states; an undefined business term can map to several implementations; clarification prevents a seemingly plausible but wrong patch. Here, however, a review discovers the acceptance criteria changed mid-implementation.

B:

A known failure gives objective feedback; starting with a broad rewrite increases unrelated regression risk; the benefit is tied to the team has a known bug with a reproducible failing test. It is not the immediate control for the need to reconcile the implementation against the new specification.

C:

For the separate situation where the generated patch contains unrelated formatting changes, a small diff improves reviewability and makes unintended consequences easier to detect; the current task is to reconcile the implementation against the new specification.

E:

A local green test is not enough when shared interfaces are modified; neighboring consumers need coverage; it is a safeguard for the fix passes the reproducer but may affect adjacent modules, not the specific situation described: a review discovers the acceptance criteria changed mid-implementation.

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