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

Question 510

Spend spikes as basic questions consume the same reasoning budget as the rare complex exceptions. Which intervention targets the defect rather than its symptoms?

  1. Choose model and architecture tiers by case impact
  2. Adopt a control group to establish incremental business impact
  3. Track cost per accepted business outcome
  4. Design a degraded mode that protects the value proposition

Explanation

Correct Answer

A:

Route by validated task complexity and consequence, using stronger reasoning or human review where evidence justifies the incremental spend; segmented evaluation reveals whether additional reasoning spend is targeted at cases that benefit; verify the repair using quality and total cost segmented by request risk tier under a fixed accuracy floor.

Incorrect Answers

B:

Before-after counts without a credible comparison group may misattribute unrelated changes to the model; use matched baselines, controlled rollout, or appropriate difference-in-differences analysis to isolate contribution under plausible confounders; that control is assessed by incremental resolution lift compared with a comparable non-assisted cohort; the incident instead requires quality and total cost segmented by request risk tier under a fixed accuracy floor.

C:

Raw token prices do not capture productivity or failure-driven rework; combine inference, retrieval, tools, review, and rework costs into cost per accepted deliverable; that control is assessed by total operational cost divided by approved documents meeting the quality rubric; the incident instead requires quality and total cost segmented by request risk tier under a fixed accuracy floor.

D:

High answer accuracy in normal mode says little about process continuity during dependency failures; separate critical deterministic operations from AI enhancement and provide explicit fallback and manual paths when model service is unavailable; that control is assessed by successful completion of critical workflows during injected model outages; the incident instead requires quality and total cost segmented by request risk tier under a fixed accuracy floor.

Question 511

An emergency-planning assistant proposes resource allocations that may be disputed by local experts. What is the most defensible next step?

  1. Test accessibility of generated explanations and interfaces
  2. Design an override path proportionate to consequences
  3. Expose evidence and decision boundaries to affected users
  4. Measure errors across relevant user subgroups

Explanation

Correct Answer

B:

Preserve an authorized override and recovery route scaled to decision consequences, with feedback recorded for evaluation; pre-commit override drills test real controllability rather than retrospective documentation; evaluate the design with successful intervention before seeded high-impact incorrect actions are committed.

Incorrect Answers

A:

Include accessibility requirements, assistive-technology testing, and inclusive content rubrics in evaluation and design; factual accuracy alone does not make the interface usable to everyone; this alternative would measure task completion by users of tested assistive technologies on representative flows; it does not establish successful intervention before seeded high-impact incorrect actions are committed for the described use case.

C:

Distinguish evidence, uncertainty, and advisory status with accessible citations and a path to authoritative decisions; a polished explanation without provenance may create false confidence in unsupported reasoning; this alternative would measure user comprehension of advisory status and source-citation validity; it does not establish successful intervention before seeded high-impact incorrect actions are committed for the described use case.

D:

Evaluate suitable subgroup error rates and access outcomes, with privacy-aware sampling and appropriate fairness review; overall accuracy cannot establish comparable treatment for every affected population; this alternative would measure quality and escalation parity across predeclared language segments; it does not establish successful intervention before seeded high-impact incorrect actions are committed for the described use case.

Question 512

Leadership assumes full automation is safe because no failure was disclosed during the demonstration. Which change should the architect recommend first?

  1. Record alternatives and rationale in an architecture decision record
  2. Present executive decisions through outcomes, cost, and risk
  3. Demonstrate known limitations alongside successful workflows
  4. Compare options on a shared multi-dimensional scorecard

Explanation

Correct Answer

C:

Use representative happy-path and failure-path demonstrations with explicit fallback, uncertainty, and human ownership; understanding checks reveal whether decision-makers grasp operational limits; verify the repair using stakeholder identification of boundaries and fallback responsibilities after the demo.

Incorrect Answers

A:

A final diagram alone often omits rejected alternatives and the reasoning behind the choice; use an ADR recording context, considered options, decision, trade-offs, implications, and conditions for revisiting it; that control is assessed by reconstructability of key design decisions after a simulated staff handoff; the incident instead requires stakeholder identification of boundaries and fallback responsibilities after the demo.

B:

A detailed API design is valuable to implementers but not sufficient for a funding decision; summarize business value, alternatives, cost envelope, measured evidence, and requested decisions in concise nontechnical terms; that control is assessed by sponsor comprehension of expected outcomes, decision options, and risk ownership; the incident instead requires stakeholder identification of boundaries and fallback responsibilities after the demo.

D:

Isolated benchmark rankings cannot settle a decision with several business constraints; present the same quality, latency, cost, risk, and maintainability measures for each candidate under agreed weighting; that control is assessed by stakeholder-approved selection using common scored evidence and disclosed trade-offs; the incident instead requires stakeholder identification of boundaries and fallback responsibilities after the demo.

Question 513

A claim-resolution assistant is corrected by specialists but only the final approval status is recorded. Which option addresses the immediate design need?

  1. Escalate binding legal interpretations to qualified reviewers
  2. Capture reviewer overrides as structured improvement signals
  3. Mandate stronger approval paths for exceptional high-impact actions
  4. Require named authorization before moving money

Explanation

Correct Answer

B:

Record correction reasons, provenance, and case labels under retention rules to support evaluation and process redesign; structured override trends reveal whether feedback improves the system over time; evaluate the design with recurrence rate of categorized, previously corrected error types.

Incorrect Answers

A:

Define escalation thresholds and route consequential interpretations to qualified legal or compliance owners with source context; a high model confidence estimate cannot replace delegated legal decision authority; this alternative would measure correct escalation of ambiguous legal cases with reviewer attribution; it does not establish recurrence rate of categorized, previously corrected error types for the described use case.

C:

Apply risk-tiered approvals, including dual control or independent sign-off where policy demands, to exceptionally consequential mutations; a uniform low-friction approval does not reflect differing blast radius and operational risk; this alternative would measure critical-action dual-approval compliance and zero bypasses during staged tests; it does not establish recurrence rate of categorized, previously corrected error types for the described use case.

D:

Separate recommendation from execution and require an authenticated human approval bound to the exact amount, payee, and transaction; general user authentication does not confer approval for a specific financial transfer; this alternative would measure zero disbursements without an auditable transaction-specific approver; it does not establish recurrence rate of categorized, previously corrected error types for the described use case.

Question 514

A service owner believes the AI will resolve all disputes while engineering plans only to draft recommended replies. Which intervention is most appropriate for this use case?

  1. Map the owner and authority of every required data source
  2. Validate risky assumptions through narrow experiments
  3. Record nonfunctional requirements as measurable thresholds
  4. Obtain sign-off on explicit acceptance criteria and exclusions
  5. Capture external dependencies and acceptance risks explicitly

Explanation

Correct Answer

D:

Document in-scope outcomes, exclusions, metrics, responsibilities, and go-live gates for accountable approval; an explicit agreement limits scope drift and creates a common release standard; evaluate the design with signed acceptance criteria mapped to demonstrable tests and named owners.

Incorrect Answers

A:

Create a source inventory with accountable owners, sensitivity, update rate, and approval dependencies before committing to the design; a list of desired features cannot grant access or establish source truthfulness; this alternative would measure percentage of required sources with approved owners, legal uses, and integration paths; it does not establish signed acceptance criteria mapped to demonstrable tests and named owners for the described use case.

B:

Identify high-risk assumptions and design small feasibility spikes with explicit success and stop criteria; detailed architecture diagrams do not prove uncertain input quality or model capability; this alternative would measure resolution rate of prioritized unknowns through measured prototypes; it does not establish signed acceptance criteria mapped to demonstrable tests and named owners for the described use case.

C:

Specify capacity, tail latency, availability, privacy, and recovery objectives with measurement windows and ownership; functional task lists do not tell designers what constitutes acceptable production operation; this alternative would measure agreed p95, availability, and load thresholds exercised in an acceptance environment; it does not establish signed acceptance criteria mapped to demonstrable tests and named owners for the described use case.

E:

Maintain a dependency register covering third-party SLAs, quotas, outage paths, and contractual conditions with mitigation owners; an AI model benchmark cannot predict every upstream system's production behavior; this alternative would measure verified readiness of high-impact external dependencies against test quotas and outage cases; it does not establish signed acceptance criteria mapped to demonstrable tests and named owners for the described use case.

Question 515

A confidential production failure must be reproduced without copying customer transcripts into an open test environment. Which result would establish that sanitized fixtures preserve the bug while protecting sensitive values?

  1. Correct root-cause attribution under injected search timeouts
  2. Time to restore normal operation using an approved previous release
  3. Correct identification of enforced deny source without allowing prohibited commands
  4. Bug reproduction on sanitized fixtures with no sensitive token disclosure
  5. Recurrence rate of the diagnosed failure and completion of preventive actions
  6. Reproduction rate of sampled incidents from stored sanitized diagnostic metadata

Explanation

Correct Answer

D:

Safe replay demonstrates that privacy and diagnostic value can coexist; measure bug reproduction on sanitized fixtures with no sensitive token disclosure at the release gate; build redacted, access-controlled replay fixtures preserving relevant syntax and error conditions without unnecessary secrets or personal data.

Incorrect Answers

A:

Controlled fault injection tests whether the team diagnoses the failing layer; classify tool errors separately from model responses, validate return codes, and probe the failing integration before changing prompts; this tests correct root-cause attribution under injected search timeouts; the actual release condition is bug reproduction on sanitized fixtures with no sensitive token disclosure.

B:

A rollback drill verifies that recovery does not depend on the original developer being online; maintain versioned releases and documented rollback steps for hooks, prompts, model routes, and connector configuration; this tests time to restore normal operation using an approved previous release; the actual release condition is bug reproduction on sanitized fixtures with no sensitive token disclosure.

C:

Precedence tests prevent insecure workarounds that bypass governance intent; review organization, project, and local permission layers in the documented precedence order before weakening security controls; this tests correct identification of enforced deny source without allowing prohibited commands; the actual release condition is bug reproduction on sanitized fixtures with no sensitive token disclosure.

E:

Follow-up measures show whether operational learning survives the immediate repair; run blameless root-cause analysis, link corrective actions to owners, and add regression or operational safeguards before closing the incident; this tests recurrence rate of the diagnosed failure and completion of preventive actions; the actual release condition is bug reproduction on sanitized fixtures with no sensitive token disclosure.

F:

Reproducibility is a prerequisite for a trustworthy fix; collect privacy-safe traces, request IDs, environment details, and exact configuration revisions to establish a reproducible failure case; this tests reproduction rate of sampled incidents from stored sanitized diagnostic metadata; the actual release condition is bug reproduction on sanitized fixtures with no sensitive token disclosure.

Question 516

A compliance search index includes multiple editions of the same regulation. Reviewers ask questions on either side of an effective-date change. Which evidence proves that retrieved citations are version-correct?

  1. Citation correctness by effective-date version in temporal regression questions
  2. Current-state citation accuracy across log-update sequences
  3. Correct recovery of approvals and pending actions after forced session reset
  4. Answer support and retrieved-token volume on a sampled policy-question set

Explanation

Correct Answer

A:

Metadata-aware checks distinguish legitimate historic references from current-policy answers; measure citation correctness by effective-date version in temporal regression questions at the release gate; supply source identity, version, effective date, and retrieval relevance alongside each chunk so the model can attribute evidence correctly.

Incorrect Answers

B:

Freshness-aware tests expose whether stale tool observations override newer facts; prune or summarize superseded tool data, preserve timestamps and current authoritative observations, and fetch details only when needed; this tests current-state citation accuracy across log-update sequences; the actual release condition is citation correctness by effective-date version in temporal regression questions.

C:

Durable-state testing proves behavior survives context eviction; store approvals and workflow state in an authoritative durable system; treat chat history as context, not a transaction ledger; this tests correct recovery of approvals and pending actions after forced session reset; the actual release condition is citation correctness by effective-date version in temporal regression questions.

D:

Relevance per token measures whether context compression preserves the needed evidence; apply query-driven retrieval and evidence selection before prompting Claude, retaining citations and permission filters; this tests answer support and retrieved-token volume on a sampled policy-question set; the actual release condition is citation correctness by effective-date version in temporal regression questions.

Question 517

A warehouse-assistance system has a limited pilot before broad operational rollout. Testers introduce traffic spikes, malformed inputs, and edge-case orders. Which outcome would demonstrate readiness against defined thresholds?

  1. Resolution of high-severity architecture risks before implementation approval
  2. Cycle time from detected drift to validated improvement without safety regression
  3. Pilot gate pass rate with defined performance and safety thresholds
  4. Closure of high-risk feasibility questions before design approval

Explanation

Correct Answer

C:

A controlled pilot turns rollout into a measurable decision; measure pilot gate pass rate with defined performance and safety thresholds at the release gate; define pilot size, critical acceptance metrics, escalation paths, and scale-up criteria before broad deployment.

Incorrect Answers

A:

Early controls reduce late redesign and exposure; incorporate threat modeling, authorization, data processing, and human oversight into architecture acceptance before implementation hardens; this tests resolution of high-severity architecture risks before implementation approval; the actual release condition is pilot gate pass rate with defined performance and safety thresholds.

B:

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 pilot gate pass rate with defined performance and safety thresholds.

D:

Stage gates prevent costly commitment to untested assumptions; require validated problem scope, value hypothesis, data authority, and feasibility evidence before full design commitment; this tests closure of high-risk feasibility questions before design approval; the actual release condition is pilot gate pass rate with defined performance and safety thresholds.

Question 518

A software organization has placed its codebase conventions and validation commands in shared, versioned Claude Code guidance. Which result across fresh developer sessions would establish that assistance follows the repository standard?

  1. Subagent task completion with zero out-of-scope tool access
  2. Hook execution and blocked noncompliant operations under simulated bypass attempts
  3. Consistency of generated changes with repository build and test conventions across fresh sessions
  4. Secret-scanning results and blocked exfiltration on seeded repository credentials

Explanation

Correct Answer

C:

Reproducible onboarding shows whether team guidance is discoverable and current; measure consistency of generated changes with repository build and test conventions across fresh sessions at the release gate; put reviewed repository-specific guidance in a shared CLAUDE.md file with appropriate scope and code review.

Incorrect Answers

A:

Role-isolation tests prove that decomposition also restricts authority; give each delegated role explicit objectives, context limits, and tool permissions with clear return artifacts; this tests subagent task completion with zero out-of-scope tool access; the actual release condition is consistency of generated changes with repository build and test conventions across fresh sessions.

B:

Gate testing verifies that a real program, not a conversational promise, enforces the rule; configure supported hooks for deterministic checks at appropriate lifecycle points, with clear failure behavior and maintenance ownership; this tests hook execution and blocked noncompliant operations under simulated bypass attempts; the actual release condition is consistency of generated changes with repository build and test conventions across fresh sessions.

D:

Source and runtime scans target the actual paths by which developer secrets can leak; use approved secret storage, scoped environment access, and redaction while avoiding credentials in repositories, prompts, or logs; this tests secret-scanning results and blocked exfiltration on seeded repository credentials; the actual release condition is consistency of generated changes with repository build and test conventions across fresh sessions.

Question 519

A repeated legal phrasing problem cannot be traced to the release that introduced it. Which corrective change best addresses the root cause?

  1. Associate human corrections with exact release versions
  2. Detect distribution and quality drift in ongoing samples
  3. Track safety policy events across product updates
  4. Alert on unexpected token and cost anomalies

Explanation

Correct Answer

A:

Log consented feedback alongside prompt revision, model route, source version, and case context for reproducible analysis; version-linked labels enable targeted, testable corrections; verify the repair using reproduction of sampled reviewer defects against their original configuration.

Incorrect Answers

B:

A static validation set cannot reflect every change in real input distribution over time; periodically sample representative production outputs for labeling, segment analysis, and drift signals without retaining unnecessary personal data; that control is assessed by quality delta between recent audited production samples and the launch baseline; the incident instead requires reproduction of sampled reviewer defects against their original configuration.

C:

A falling count of harmful completions can coexist with an unusable overrestrictive assistant; monitor both harmful-output violations and false-positive blocks by version and user segment; that control is assessed by safety precision/recall and legitimate-task completion before and after the change; the incident instead requires reproduction of sampled reviewer defects against their original configuration.

D:

Request-volume alerts alone miss a sudden rise in tokens per individual workflow; monitor input/output tokens, cache reads, per-stage costs, and cost-per-task anomalies with accountable ownership; that control is assessed by detection lag for injected per-request token inflation; the incident instead requires reproduction of sampled reviewer defects against their original configuration.

Question 520

A backend team asks Claude to implement a billing calculation with several edge cases and regulatory rounding rules. Which choice most directly satisfies the documented goal?

  1. Use test-first acceptance cases for generated changes
  2. Run reproducible CI checks on AI-assisted code changes
  3. Package reusable engineering instructions as governed Skills
  4. Break large refactors into independently reviewable changes

Explanation

Correct Answer

A:

Define executable tests and expected behavior before relying on AI-generated implementation, then review failures and iterate; test-first evidence anchors generated code in independently defined behavior; evaluate the design with passing unit and property tests including specified rounding boundaries.

Incorrect Answers

B:

Execute standardized linting, type checks, tests, and security scanning in versioned CI environments before merges; local success can be environment-dependent and should not be the only release assurance; this alternative would measure cI pass reproducibility on clean builds with locked dependencies; it does not establish passing unit and property tests including specified rounding boundaries for the described use case.

C:

Maintain task-scoped reusable Skills or playbooks with versioning, ownership, and documented prerequisites; shared instructions improve consistency but do not replace enforced approval or automated tests; this alternative would measure checklist completeness across independent sessions using the reviewed Skill version; it does not establish passing unit and property tests including specified rounding boundaries for the described use case.

D:

Use small scoped changes, compatibility checkpoints, and separate pull requests tied to specific tests; one massive patch can reduce initial coordination but increases regression and rollback risk; this alternative would measure review time and defect localization per incremental change set; it does not establish passing unit and property tests including specified rounding boundaries for the described use case.

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