Anthropic CCAR-P (Claude Certified Architect - Professional) Practice Test 49

Question 480

An enterprise has proposed an expensive automation program but is still uncertain about upstream data access and extraction feasibility. Which discovery-gate result would justify committing to detailed solution design?

  1. Named owner coverage and support-drill completion at handoff
  2. Successful retirement with zero unplanned dependent-system failures
  3. Cycle time from detected drift to validated improvement without safety regression
  4. Closure of high-risk feasibility questions before design approval

Explanation

Correct Answer

D:

Stage gates prevent costly commitment to untested assumptions; measure closure of high-risk feasibility questions before design approval at the release gate; require validated problem scope, value hypothesis, data authority, and feasibility evidence before full design commitment.

Incorrect Answers

A:

Ownership evidence shows the service can be maintained after consultants leave; establish production owners for reliability, security, spend, data, prompts, and escalation, with verified access and runbooks; this tests named owner coverage and support-drill completion at handoff; the actual release condition is closure of high-risk feasibility questions before design approval.

B:

Dependency-aware migration tests verify that lifecycle closure is complete; inventory consumers, define migration dates and fallback, preserve data obligations, and test the rollback or retirement path; this tests successful retirement with zero unplanned dependent-system failures; the actual release condition is closure of high-risk feasibility questions before design approval.

C:

Continuous assessment links real usage to controlled change; feed production samples and feedback into versioned evals, prioritize changes, and release improvements behind regression gates; this tests cycle time from detected drift to validated improvement without safety regression; the actual release condition is closure of high-risk feasibility questions before design approval.

Question 481

A healthcare operations agent uses tools that return sensitive case narratives in error responses. What should the solution architect recommend?

  1. Sample complete traces strategically under heavy traffic
  2. Log structured tool outcomes without exposing sensitive payloads
  3. Alert on unusual high-impact tool activity
  4. Separate retrieval, provider, and tool latency budgets

Explanation

Correct Answer

B:

Record tool type, status, duration, correlation IDs, and carefully redacted diagnostic fields under controlled retention; redaction and observability must be validated together, not traded off blindly; evaluate the design with error diagnosability with seeded sensitive fields absent from collected logs.

Incorrect Answers

A:

Retain error and high-risk traces at a higher rate while sampling successful routine traffic with privacy controls; keeping every raw trace is costly and may violate retention principles without improving detection proportionally; this alternative would measure capture rate of seeded critical failures at a bounded telemetry cost; it does not establish error diagnosability with seeded sensitive fields absent from collected logs for the described use case.

C:

Monitor write volume, denials, unusual resource patterns, and action-specific thresholds with fast containment routing; general chat satisfaction metrics are too delayed and indirect to detect dangerous mutation spikes; this alternative would measure time to detect and stop a simulated unauthorized bulk-write burst; it does not establish error diagnosability with seeded sensitive fields absent from collected logs for the described use case.

D:

Instrument per-stage timing and compare each segment against its allocated latency budget before changing model configuration; optimizing generation tokens cannot repair a slow connector that dominates the critical path; this alternative would measure stage-specific p95 deltas identifying injected bottlenecks; it does not establish error diagnosability with seeded sensitive fields absent from collected logs for the described use case.

Question 482

A product recommendation assistant performs well at launch but the catalog and customer preferences evolve seasonally. Which design decision directly addresses this constraint?

  1. Compare production metrics by model and prompt version
  2. Instrument end-to-end execution spans for causal debugging
  3. Detect distribution and quality drift in ongoing samples
  4. Alert on unexpected token and cost anomalies

Explanation

Correct Answer

C:

Periodically sample representative production outputs for labeling, segment analysis, and drift signals without retaining unnecessary personal data; live sampling reveals degradation that unchanged historical tests cannot see; evaluate the design with quality delta between recent audited production samples and the launch baseline.

Incorrect Answers

A:

Partition traces and scored outcomes by deployed configuration, using release identifiers to support rollback and diagnosis; a global metric is inadequate when several behaviors are concurrently deployed; this alternative would measure detection of version-specific quality regressions in a staged rollout; it does not establish quality delta between recent audited production samples and the launch baseline for the described use case.

B:

Correlation and span IDs across components allow latency and failure attribution along the actual path; model usage totals do not reveal which integration failed within a particular request; this alternative would measure percent of failures with a complete trace to the responsible stage; it does not establish quality delta between recent audited production samples and the launch baseline for the described use case.

D:

Monitor input/output tokens, cache reads, per-stage costs, and cost-per-task anomalies with accountable ownership; request-volume alerts alone miss a sudden rise in tokens per individual workflow; this alternative would measure detection lag for injected per-request token inflation; it does not establish quality delta between recent audited production samples and the launch baseline for the described use case.

Question 483

A regulatory assistant retrieves excerpts from different editions of a policy with nearly identical language. Which approach best meets the stated requirement?

  1. Remove obsolete tool output while preserving current evidence
  2. Attach provenance metadata to selected context
  3. Allocate input and output token budgets per workflow step
  4. Compact extended sessions without discarding commitments

Explanation

Correct Answer

B:

Supply source identity, version, effective date, and retrieval relevance alongside each chunk so the model can attribute evidence correctly; metadata-aware checks distinguish legitimate historic references from current-policy answers; evaluate the design with citation correctness by effective-date version in temporal regression questions.

Incorrect Answers

A:

Prune or summarize superseded tool data, preserve timestamps and current authoritative observations, and fetch details only when needed; pruning without version markers can erase the evidence needed to explain the incident's evolution; this alternative would measure current-state citation accuracy across log-update sequences; it does not establish citation correctness by effective-date version in temporal regression questions for the described use case.

C:

Reserve output capacity and bound each stage's retrieved context and response length according to the deliverable structure; merely expanding every context window can increase cost while leaving output truncation unaddressed; this alternative would measure complete mandatory report sections under the worst supported input size; it does not establish citation correctness by effective-date version in temporal regression questions for the described use case.

D:

Store a structured, reviewable summary of decisions, open issues, and provenance; inject it at checkpoints rather than replaying every chat turn; blind summarization can lose critical exceptions unless durable commitments are explicitly represented; this alternative would measure retention of signed-off requirements after long simulated conversations; it does not establish citation correctness by effective-date version in temporal regression questions for the described use case.

Question 484

A connector bug causes a sudden tenfold increase in update calls before users report visible problems. Which action best removes the underlying failure mode?

  1. Correlate model, retrieval, and tool spans in distributed traces
  2. Log structured tool outcomes without exposing sensitive payloads
  3. Decouple retrieval, provider, and tool latency budgets
  4. Segment reliability metrics by tenant and workload
  5. Alert on unusual high-impact tool activity

Explanation

Correct Answer

E:

Monitor write volume, denials, unusual resource patterns, and action-specific thresholds with fast containment routing; action telemetry and response drills measure whether harmful changes can be contained promptly; verify the repair using time to detect and stop a simulated unauthorized bulk-write burst.

Incorrect Answers

A:

A model-only latency chart cannot explain retrieval or downstream network bottlenecks; end-to-end traces with consistent request and span identifiers identify which service and step consumed time; that control is assessed by trace completeness and correct bottleneck attribution on instrumented fault injections; the incident instead requires time to detect and stop a simulated unauthorized bulk-write burst.

B:

Full payload capture may help debugging but expands sensitive-data exposure and retention obligations; record tool type, status, duration, correlation IDs, and carefully redacted diagnostic fields under controlled retention; that control is assessed by error diagnosability with seeded sensitive fields absent from collected logs; the incident instead requires time to detect and stop a simulated unauthorized bulk-write burst.

C:

Optimizing generation tokens cannot repair a slow connector that dominates the critical path; instrument per-stage timing and compare each segment against its allocated latency budget before changing model configuration; that control is assessed by stage-specific p95 deltas identifying injected bottlenecks; the incident instead requires time to detect and stop a simulated unauthorized bulk-write burst.

D:

Overall averages can hide concentrated failures without meaningful dimensional analysis; break down latency, errors, and tool success by permission-safe tenant and workload dimensions with cardinality controls; that control is assessed by detection time for an injected single-tenant degradation; the incident instead requires time to detect and stop a simulated unauthorized bulk-write burst.

Question 485

A circular escalation pattern consumes budget and ends without a usable result or human handoff. Which corrective change best addresses the root cause?

  1. Delegate only specialized subtasks that add measurable value
  2. Bound handoffs, retries, and recursion across agents
  3. Run independent specialists in parallel with a merge contract
  4. Use a coordinator to route distinct specialist tasks

Explanation

Correct Answer

B:

Enforce maximum depth, handoff count, timeouts, and explicit unresolved-case escalation in the orchestrator; stressing unresolved cases proves that the system can fail predictably and within budget; verify the repair using zero unbounded cycles under adversarial unresolved tasks while retaining a useful escalation record.

Incorrect Answers

A:

More agents by themselves do not provide additional knowledge, authority, or better outcomes; introduce a specialist only when its independent expertise, tool scope, or parallelism beats a simpler call on representative evaluations; that control is assessed by marginal quality improvement per added specialist against its incremental cost and latency; the incident instead requires zero unbounded cycles under adversarial unresolved tasks while retaining a useful escalation record.

C:

Parallel fan-out is unsafe when tasks mutate the same state or depend on each other's evolving outputs; parallel fan-out followed by deterministic aggregation can shorten wall-clock time if each branch has its own contract and errors are handled; that control is assessed by p95 end-to-end latency and deterministic merge completeness under one-branch failures; the incident instead requires zero unbounded cycles under adversarial unresolved tasks while retaining a useful escalation record.

D:

Specialist routing adds handoffs and can be wasteful for one small, homogeneous transformation; a coordinator can dispatch scoped subagents and merge their typed outputs while restricting each specialist's context and tools; that control is assessed by completed reports with correctly scoped evidence and no cross-specialty data leakage; the incident instead requires zero unbounded cycles under adversarial unresolved tasks while retaining a useful escalation record.

Question 486

A developer integration uses tokens for a private package registry and internal issue tracker. Which intervention is most appropriate for this use case?

  1. Use specialized subagents with bounded tools and instructions
  2. Use deterministic hooks to enforce required developer gates
  3. Version team-wide CLAUDE.md guidance with the repository
  4. Scope MCP connections by project and user identity
  5. Keep credentials out of prompts and versioned configuration

Explanation

Correct Answer

E:

Use approved secret storage, scoped environment access, and redaction while avoiding credentials in repositories, prompts, or logs; source and runtime scans target the actual paths by which developer secrets can leak; evaluate the design with secret-scanning results and blocked exfiltration on seeded repository credentials.

Incorrect Answers

A:

Give each delegated role explicit objectives, context limits, and tool permissions with clear return artifacts; delegation without role scoping merely multiplies the number of powerful agents; this alternative would measure subagent task completion with zero out-of-scope tool access; it does not establish secret-scanning results and blocked exfiltration on seeded repository credentials for the described use case.

B:

Configure supported hooks for deterministic checks at appropriate lifecycle points, with clear failure behavior and maintenance ownership; a written instruction alone is best-effort and does not guarantee enforcement of a critical command gate; this alternative would measure hook execution and blocked noncompliant operations under simulated bypass attempts; it does not establish secret-scanning results and blocked exfiltration on seeded repository credentials for the described use case.

C:

Put reviewed repository-specific guidance in a shared CLAUDE.md file with appropriate scope and code review; a documentation file guides behavior but cannot enforce operating-system permissions or replace CI tests; this alternative would measure consistency of generated changes with repository build and test conventions across fresh sessions; it does not establish secret-scanning results and blocked exfiltration on seeded repository credentials for the described use case.

D:

Choose appropriate configuration scope and per-user or service authorization for MCP servers, avoiding shared cross-project secrets; a working connection does not prove the assistant is restricted to the user's intended project resources; this alternative would measure access denial for cross-project MCP resources under user identity tests; it does not establish secret-scanning results and blocked exfiltration on seeded repository credentials for the described use case.

Question 487

A generalist agent sends sensitive legal exhibits to a financial summarizer that has no need to see them. Which change should the architect recommend first?

  1. Run independent specialists in parallel with a merge contract
  2. Version the handoff artifacts between agents
  3. Use a coordinator to route distinct specialist tasks
  4. Bound handoffs, retries, and recursion across agents
  5. Separate independent critique from generation

Explanation

Correct Answer

C:

A coordinator can dispatch scoped subagents and merge their typed outputs while restricting each specialist's context and tools; routing correctness must include scope enforcement, not just readable final reports; verify the repair using completed reports with correctly scoped evidence and no cross-specialty data leakage.

Incorrect Answers

A:

Parallel fan-out is unsafe when tasks mutate the same state or depend on each other's evolving outputs; parallel fan-out followed by deterministic aggregation can shorten wall-clock time if each branch has its own contract and errors are handled; that control is assessed by p95 end-to-end latency and deterministic merge completeness under one-branch failures; the incident instead requires completed reports with correctly scoped evidence and no cross-specialty data leakage.

B:

Artifact versioning governs exchange correctness, not whether the underlying market facts were researched accurately; immutable, versioned handoff artifacts and typed schemas prevent one agent from consuming ambiguous or mismatched intermediate state; that control is assessed by zero stale-artifact merges across concurrent revision and retry scenarios; the incident instead requires completed reports with correctly scoped evidence and no cross-specialty data leakage.

D:

Recursive collaboration is not inherently self-terminating and cannot be made safe only by asking agents to cooperate; enforce maximum depth, handoff count, timeouts, and explicit unresolved-case escalation in the orchestrator; that control is assessed by zero unbounded cycles under adversarial unresolved tasks while retaining a useful escalation record; the incident instead requires completed reports with correctly scoped evidence and no cross-specialty data leakage.

E:

A critic agent does not repair missing source documents or guarantee that all facts are verifiable; a distinct verifier with a rubric and evidence access can challenge unsupported assertions before an external document is released; that control is assessed by verified claim support rate after independent critique on seeded unsupported drafts; the incident instead requires completed reports with correctly scoped evidence and no cross-specialty data leakage.

Question 488

A claims portal places customer narratives in a separately delimited message while preserving higher-priority workflow rules. Attackers try role-spoofing text in the narrative field. Which outcome would verify the instruction boundary?

  1. Rate of user messages that fail to override defined task boundaries in regression tests
  2. Prompt-injection resistance on hostile retrieved snippets without loss of legitimate source use
  3. Unsupported-answer rate and appropriate abstention precision on no-answer cases
  4. Out-of-scope refusal and handoff accuracy on a policy-boundary test set

Explanation

Correct Answer

A:

Boundary-specific tests confirm that changing user content cannot rewrite the application contract; measure rate of user messages that fail to override defined task boundaries in regression tests at the release gate; separate stable system-level policy from user content and tool results, retaining consistent privilege boundaries across requests.

Incorrect Answers

B:

Adversarial retrieval tests exercise the trust boundary rather than only neutral documents; clearly separate lower-trust source material from application instructions and enforce permissions at the tool layer as well; this tests prompt-injection resistance on hostile retrieved snippets without loss of legitimate source use; the actual release condition is rate of user messages that fail to override defined task boundaries in regression tests.

C:

An abstention test verifies whether uncertainty is handled safely without refusing answerable questions; tell the assistant when to identify missing evidence, ask for clarification, or escalate, and reinforce this with evidence validation; this tests unsupported-answer rate and appropriate abstention precision on no-answer cases; the actual release condition is rate of user messages that fail to override defined task boundaries in regression tests.

D:

Boundary tests demonstrate task scoping rather than only fluent responses on ordinary requests; define the assistant's permitted tasks, out-of-scope handling, and escalation behavior in stable application-level instructions, backed by independent access enforcement; this tests out-of-scope refusal and handoff accuracy on a policy-boundary test set; the actual release condition is rate of user messages that fail to override defined task boundaries in regression tests.

Question 489

The assistant confidently quotes a repealed clause that remains in the vector store. Which intervention targets the defect rather than its symptoms?

  1. Evaluate retrieval quality independently of generation
  2. Version embeddings and reindex when representation changes
  3. Filter retrieval by access control before model exposure
  4. Preserve citation metadata through retrieval and synthesis
  5. Refresh the index when source content changes

Explanation

Correct Answer

E:

Build a monitored ingestion path for adds, updates, deletes, and effective dates, with freshness checks and removal of superseded chunks; update/delete tests prove the index tracks the authoritative corpus; verify the repair using publication-to-search freshness lag and absence of withdrawn clauses in results.

Incorrect Answers

A:

A stronger model cannot reliably cite evidence that retrieval never supplies; measure retrieval recall, ranking relevance, and evidence coverage on labeled query-document pairs before optimizing generation; that control is assessed by recall at k and evidence-coverage rate for known-answer queries; the incident instead requires publication-to-search freshness lag and absence of withdrawn clauses in results.

B:

Updating only the query encoder can corrupt retrieval ranking even if the documents are unchanged; record embedding model and preprocessing versions, re-embed consistently, and use controlled index migration; that control is assessed by retrieval recall before and after a complete embedding-index migration; the incident instead requires publication-to-search freshness lag and absence of withdrawn clauses in results.

C:

A model instruction to ignore confidential items is not a data-access boundary once the text is supplied; apply document permissions to retrieval candidates before material enters model context or logs; that control is assessed by unauthorized chunk exposure rate under staff permission matrices, targeting zero; the incident instead requires publication-to-search freshness lag and absence of withdrawn clauses in results.

D:

A similarity score is not a source identifier and cannot support a traceable citation; store source IDs, locations, dates, and stable links with chunks and propagate them to answer citation validation; that control is assessed by fraction of material claims linked to resolvable source locations; the incident instead requires publication-to-search freshness lag and absence of withdrawn clauses in results.

Question 490

An analyst assistant should read reconciliation results but its connector also permits payment creation. What should the solution architect recommend?

  1. Allowlist generated fields and destinations before external calls
  2. Treat retrieved instructions as untrusted data
  3. Sandbox untrusted code and file operations
  4. Enforce least privilege where tool actions execute
  5. Screen unsafe outputs in proportion to the use case

Explanation

Correct Answer

D:

Enforce role and scope in the backend execution service using credentials that cannot perform the forbidden action; direct permission tests verify security independent of model obedience; evaluate the design with zero payment writes when tested with the analytics identity and forged instructions.

Incorrect Answers

A:

Validate destinations, argument types, sensitive fields, and authorization before dispatch; reject values outside the approved contract; formatting the request as JSON does not make arbitrary field values safe to transmit; this alternative would measure zero unapproved recipients or fields accepted by the outbound service; it does not establish zero payment writes when tested with the analytics identity and forged instructions for the described use case.

B:

Keep source contents in a lower-trust evidence role and prevent embedded commands from crossing into tool authority; assuming retrieved text is authoritative because it came from a connector opens a prompt-injection path; this alternative would measure attack success rate on adversarial web pages and zero unauthorized egress calls; it does not establish zero payment writes when tested with the analytics identity and forged instructions for the described use case.

C:

Isolate execution with restricted filesystem, network, credentials, resources, and observable policy denials; an instruction saying 'do not read secrets' cannot contain arbitrary code on an unrestricted host; this alternative would measure forbidden file and network access attempts blocked in execution tests; it does not establish zero payment writes when tested with the analytics identity and forged instructions for the described use case.

E:

Evaluate output safety against a documented risk rubric and use appropriate escalation or refusal for high-risk claims; an input-only filter cannot detect every unsafe completion, especially when harm arises from the generated detail; this alternative would measure harmful-completion detection on labeled outputs with false-positive monitoring; it does not establish zero payment writes when tested with the analytics identity and forged instructions for the described use case.

Claude Certified Architect - Professional (CCAR-P) Practice Tests