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

Question 80

Average latency looks healthy even though a long tail violates the customer-facing promise. What is the most direct remediation?

  1. Use a control group to establish incremental business impact
  2. Track cost per accepted business outcome
  3. Translate response-time expectations into a percentile SLO
  4. Choose model and architecture tiers by case impact

Explanation

Correct Answer

C:

Define a p95 or p99 target against real end-to-end requests, including retrieval and tools, rather than reporting an average model time; tail measurement detects the bad experiences that averages can obscure; verify the repair using end-to-end p95 latency and error rate against the agreed service objective.

Incorrect Answers

A:

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 end-to-end p95 latency and error rate against the agreed service objective.

B:

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 end-to-end p95 latency and error rate against the agreed service objective.

D:

A uniformly premium model can raise cost without proportionate value on simple, low-risk tasks; route by validated task complexity and consequence, using stronger reasoning or human review where evidence justifies the incremental spend; that control is assessed by quality and total cost segmented by request risk tier under a fixed accuracy floor; the incident instead requires end-to-end p95 latency and error rate against the agreed service objective.

Question 81

Two support reviewers disagree because one rewards elegant phrasing and the other values successful issue resolution. How should the team make their acceptance judgment reproducible?

  1. Prioritize a repetitive step with bounded exceptions
  2. Pilot one bounded workflow with acceptance gates
  3. Map available data and its permitted uses before solution selection
  4. Translate vague accuracy demands into task-specific criteria

Explanation

Correct Answer

D:

Convert vague requests into observable task outcomes, rubric-based quality dimensions, and failure thresholds that stakeholders can agree to test; consistent scoring makes a go-live decision defensible rather than impressionistic; verify the repair using agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set.

Incorrect Answers

A:

Prioritization improves initial return and feasibility; it does not directly supply output-validation code or tenant isolation; select a high-frequency, well-described task with measurable work reduction and explicit escalation for ambiguous records; that control is assessed by accepted cases per reviewer-hour with exception share tracked separately; the incident instead requires agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set.

B:

A pilot bounds deployment exposure; it does not substitute for an authorization model or document freshness; a narrow pilot validates one representative flow and pre-agreed quality, latency, and escalation thresholds before scaling to other workflows; that control is assessed by passing the acceptance gate on a representative pilot cohort including difficult exceptions; the incident instead requires agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set.

C:

A data inventory does not alone identify target SLOs or decide whether an orchestration loop is necessary; data-readiness and usage-rights mapping identifies legitimate inputs, owners, quality gaps, and prohibited transfers before committing to an implementation; that control is assessed by percentage of required fields with validated owners, quality checks, and approved processing purposes; the incident instead requires agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set.

Question 82

The same one-click reviewer action is used for ordinary lookups and high-risk network isolation. Which corrective change best addresses the root cause?

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

Explanation

Correct Answer

A:

Apply risk-tiered approvals, including dual control or independent sign-off where policy demands, to exceptionally consequential mutations; approval testing must target the cases where one mistake affects many users; verify the repair using critical-action dual-approval compliance and zero bypasses during staged tests.

Incorrect Answers

B:

Universal manual review may be disproportionate when actions are reversible and errors are easily detected; combine automated checks with representative human sampling and exception-based review scaled to risk; that control is assessed by defect-detection rate and reviewer workload under a risk-tiered sampling policy; the incident instead requires critical-action dual-approval compliance and zero bypasses during staged tests.

C:

General user authentication does not confer approval for a specific financial transfer; separate recommendation from execution and require an authenticated human approval bound to the exact amount, payee, and transaction; that control is assessed by zero disbursements without an auditable transaction-specific approver; the incident instead requires critical-action dual-approval compliance and zero bypasses during staged tests.

D:

A high model confidence estimate cannot replace delegated legal decision authority; define escalation thresholds and route consequential interpretations to qualified legal or compliance owners with source context; that control is assessed by correct escalation of ambiguous legal cases with reviewer attribution; the incident instead requires critical-action dual-approval compliance and zero bypasses during staged tests.

E:

Counting approval clicks alone does not describe why humans disagreed with the AI; record correction reasons, provenance, and case labels under retention rules to support evaluation and process redesign; that control is assessed by recurrence rate of categorized, previously corrected error types; the incident instead requires critical-action dual-approval compliance and zero bypasses during staged tests.

Question 83

A supplier-risk assistant relies on an external ERP endpoint with unknown throttling and downtime commitments. Separately, a document-understanding project assumes difficult scanned images will be accurate enough without testing them. Which TWO discovery practices should precede a full solution commitment? Choose TWO.

  1. Map the owner and authority of every required data source
  2. Validate risky assumptions through narrow experiments
  3. Capture external dependencies and acceptance risks explicitly
  4. Record nonfunctional requirements as measurable thresholds
  5. Interview each role that owns a distinct outcome or risk

Explanation

Correct Answers

B:

Identify high-risk assumptions and design small feasibility spikes with explicit success and stop criteria; evidence-based discovery reduces commitment to unverified technical assumptions; its corresponding workstream should be validated by resolution rate of prioritized unknowns through measured prototypes.

C:

Maintain a dependency register covering third-party SLAs, quotas, outage paths, and contractual conditions with mitigation owners; dependency validation closes gaps between prototype success and operational feasibility; its corresponding workstream should be validated by verified readiness of high-impact external dependencies against test quotas and outage cases.

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; its natural acceptance measure is percentage of required sources with approved owners, legal uses, and integration paths, which does not satisfy the separate workstreams being assessed.

D:

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; its natural acceptance measure is agreed p95, availability, and load thresholds exercised in an acceptance environment, which does not satisfy the separate workstreams being assessed.

E:

Use role-based discovery to capture goals, current workflows, authority boundaries, and failure impacts from relevant stakeholders; a sponsor's high-level vision does not fully describe operational controls or edge cases; its natural acceptance measure is coverage of approved requirements traced to affected stakeholder groups, which does not satisfy the separate workstreams being assessed.

Question 84

A service increases inference spend for routine customer questions without improving the verified outcome. Which cost-quality intervention should it test first?

  1. Reuse expensive stable prefixes through prompt caching
  2. Route straightforward requests to a validated economical model
  3. Reduce context using retrieval and relevance filtering
  4. Parallelize independent retrieval calls on the critical path

Explanation

Correct Answer

B:

Evaluate a smaller model on straightforward request strata and escalate only where measurable capability is needed; stratified monitoring confirms economic gains do not displace expensive errors onto users; verify the repair using accepted resolution rate and cost per case across routed difficulty levels.

Incorrect Answers

A:

Selecting a smaller model alone may reduce price but does not address wasted recomputation of invariant content; keep a stable eligible prompt prefix and measure cache-read tokens to reduce repeated processing; that control is assessed by cache-read rate, p95 latency, and cost per accepted answer under repeated queries; the incident instead requires accepted resolution rate and cost per case across routed difficulty levels.

C:

Token truncation at arbitrary character positions can remove governing exceptions and worsen accuracy; retrieve relevant excerpts and retain enough surrounding evidence for interpretation rather than indiscriminately filling the context window; that control is assessed by supported-answer rate per input token on labeled audit questions; the incident instead requires accepted resolution rate and cost per case across routed difficulty levels.

D:

Parallelism adds little if operations depend on each other or contend for the same rate-limited service; parallel retrieval with per-call budgets reduces wall time while preserving authorization and complete aggregation; that control is assessed by p95 response time with all three source checks present under load; the incident instead requires accepted resolution rate and cost per case across routed difficulty levels.

Question 85

A quarter later nobody knows why one pattern was chosen or which assumptions justified it. Which corrective change best addresses the root cause?

  1. Record alternatives and rationale in an architecture decision record
  2. Compare options on a shared multi-dimensional scorecard
  3. Demonstrate known limitations alongside successful workflows
  4. Maintain a risk register with controls and accountable owners

Explanation

Correct Answer

A:

Use an ADR recording context, considered options, decision, trade-offs, implications, and conditions for revisiting it; decision records preserve rationale beyond a particular architect's memory; verify the repair using reconstructability of key design decisions after a simulated staff handoff.

Incorrect Answers

B:

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 reconstructability of key design decisions after a simulated staff handoff.

C:

A demo focused solely on best cases can mask residual risks and create unrealistic expectations; use representative happy-path and failure-path demonstrations with explicit fallback, uncertainty, and human ownership; that control is assessed by stakeholder identification of boundaries and fallback responsibilities after the demo; the incident instead requires reconstructability of key design decisions after a simulated staff handoff.

D:

A high-level statement that AI has risks does not create an actionable governance plan; record probability and impact where appropriate, control owners, evidence, residual risk, and required approvals; that control is assessed by completion and ownership of high-severity mitigations before the release gate; the incident instead requires reconstructability of key design decisions after a simulated staff handoff.

Question 86

Three service teams publish changes to a shared Claude behavior standard at different times. Which release result would demonstrate that versioned guidance now prevents silent divergence?

  1. Prefix reuse ratio when request metadata changes across calls
  2. Net cost per accepted request across realistic interarrival times
  3. Cross-application prompt-version alignment and regression pass rate
  4. Cache-read input tokens and end-to-end latency over repeated requests

Explanation

Correct Answer

C:

A shared module succeeds when consuming workflows inherit the same reviewed rule set; measure cross-application prompt-version alignment and regression pass rate at the release gate; maintain a versioned reusable prompt module with explicit parameters and regression tests across consumers.

Incorrect Answers

A:

Controlled request pairs reveal avoidable cache invalidation; move changing metadata after the stable prefix so cache keys remain reusable across otherwise similar requests; this tests prefix reuse ratio when request metadata changes across calls; the actual release condition is cross-application prompt-version alignment and regression pass rate.

B:

Reuse-adjusted economics tests whether the caching decision pays off under actual traffic; assess eligible caching windows, traffic frequency, and write/read economics against real reuse intervals before selecting a cache policy; this tests net cost per accepted request across realistic interarrival times; the actual release condition is cross-application prompt-version alignment and regression pass rate.

D:

Cache-hit telemetry verifies the optimization rather than relying on estimated token savings; put reusable instructions and reference material in a consistent prefix and use supported prompt-cache controls while placing variable requests afterward; this tests cache-read input tokens and end-to-end latency over repeated requests; the actual release condition is cross-application prompt-version alignment and regression pass rate.

Question 87

Preloading every manual causes truncation of the recent code context and still yields irrelevant parameter examples. How should the design be corrected?

  1. Use searchable tool discovery for large catalogs
  2. Preserve stable prefixes while dynamically discovering tools
  3. Fetch detailed schemas only for shortlisted actions
  4. Retrieve detailed reference material only when requested
  5. Keep orchestrator intent and policy separate from tool inventories

Explanation

Correct Answer

D:

Discover resource summaries first and fetch the specific authoritative documentation section at the point of need; targeted documentation fetches should improve focus without losing necessary details; verify the repair using correct endpoint contract use with lower documentation-token overhead.

Incorrect Answers

A:

Up-front registration of every schema does not improve a request that needs only one domain-specific operation; expose a lean search or discovery interface and load relevant detailed tools only after intent is established; that control is assessed by tool-choice accuracy and context-token savings on varied employee requests; the incident instead requires correct endpoint contract use with lower documentation-token overhead.

B:

Progressive discovery can lose its token advantage if dynamic tool definitions repeatedly destroy cache reuse; isolate stable instructions from changing discovery payloads and measure cache behavior when tool inventories vary; that control is assessed by cache-read tokens and total context cost while changing selected tool subsets; the incident instead requires correct endpoint contract use with lower documentation-token overhead.

C:

Schema-on-demand still needs strict parameter validation at execution time; keep concise discovery metadata initially and retrieve the precise argument schema when a tool becomes actionable; that control is assessed by schema-token consumption and invalid-argument rate after staged loading; the incident instead requires correct endpoint contract use with lower documentation-token overhead.

E:

Tool search does not supply missing user intent or approval; it is only a mechanism for selecting capabilities; separate goal interpretation and policy decisions from a downstream staged capability-discovery step; that control is assessed by intent-classification accuracy before any tool disclosure or call; the incident instead requires correct endpoint contract use with lower documentation-token overhead.

Question 88

Two support-review teams disagree about whether a polite answer that leaves an account problem unresolved should pass. Before expanding the pilot, which evidence would establish a consistent, outcome-oriented quality standard?

  1. Accepted cases per reviewer-hour with exception share tracked separately
  2. Share of binding decisions showing the required named approver and rationale
  3. Percentage of required fields with validated owners, quality checks, and approved processing purposes
  4. Agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set

Explanation

Correct Answer

D:

Consistent scoring makes a go-live decision defensible rather than impressionistic; measure agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set at the release gate; convert vague requests into observable task outcomes, rubric-based quality dimensions, and failure thresholds that stakeholders can agree to test.

Incorrect Answers

A:

Counting both throughput and escalations prevents a fast happy path from hiding a costly exception queue; select a high-frequency, well-described task with measurable work reduction and explicit escalation for ambiguous records; this tests accepted cases per reviewer-hour with exception share tracked separately; the actual release condition is agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set.

B:

An auditable decision trail demonstrates that AI outputs remained advisory where policy requires it; explicit decision-rights boundaries distinguish advisory generation from actions requiring a credentialed human or deterministic policy engine; this tests share of binding decisions showing the required named approver and rationale; the actual release condition is agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set.

C:

Measured coverage of eligible sources exposes blockers that a high demo score conceals; data-readiness and usage-rights mapping identifies legitimate inputs, owners, quality gaps, and prohibited transfers before committing to an implementation; this tests percentage of required fields with validated owners, quality checks, and approved processing purposes; the actual release condition is agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set.

Question 89

Calls execute serially and their combined latency dominates generation time. Which change should the architect recommend first?

  1. Parallelize independent retrieval calls on the critical path
  2. Tune cost using the rate of acceptable outcomes
  3. Route straightforward requests to a validated economical model
  4. Schedule non-urgent work through bounded batch processing

Explanation

Correct Answer

A:

Parallel retrieval with per-call budgets reduces wall time while preserving authorization and complete aggregation; the acceptance signal guards against a fast but incomplete response; verify the repair using p95 response time with all three source checks present under load.

Incorrect Answers

B:

Minimizing token counts without measuring quality can make a workflow more expensive in practice; optimize total cost per successful output with floor constraints on completeness, safety, and latency; that control is assessed by all-in cost per accepted summary at a fixed mandatory-section completion rate; the incident instead requires p95 response time with all three source checks present under load.

C:

Using the cheapest model universally could impair complex or safety-critical cases; evaluate a smaller model on straightforward request strata and escalate only where measurable capability is needed; that control is assessed by accepted resolution rate and cost per case across routed difficulty levels; the incident instead requires p95 response time with all three source checks present under load.

D:

Batch pipelines are inappropriate where a person needs a subsecond answer for an active decision; use suitable batch orchestration and queue control to trade immediate response time for predictable throughput and expense; that control is assessed by cost and successful throughput per nightly processing window; the incident instead requires p95 response time with all three source checks present under load.

Question 90

Applicants using an automated scholarship screening service can challenge suspected factual errors. Which measured outcome would demonstrate that review and correction are accessible and accountable?

  1. Task completion by users of tested assistive technologies on representative flows
  2. Time to resolve substantiated challenges and proportion of cases with documented review
  3. Quality and escalation parity across predeclared language segments
  4. Successful intervention before seeded high-impact incorrect actions are committed

Explanation

Correct Answer

B:

Remedy effectiveness measures whether affected people can obtain meaningful reconsideration; measure time to resolve substantiated challenges and proportion of cases with documented review at the release gate; provide a contest and correction process with accountable human ownership for significant impacts.

Incorrect Answers

A:

Direct accessibility testing measures practical use rather than formal content correctness only; include accessibility requirements, assistive-technology testing, and inclusive content rubrics in evaluation and design; this tests task completion by users of tested assistive technologies on representative flows; the actual release condition is time to resolve substantiated challenges and proportion of cases with documented review.

C:

Group-specific evaluation reveals concentrated harm masked by pooled scores; evaluate suitable subgroup error rates and access outcomes, with privacy-aware sampling and appropriate fairness review; this tests quality and escalation parity across predeclared language segments; the actual release condition is time to resolve substantiated challenges and proportion of cases with documented review.

D:

Pre-commit override drills test real controllability rather than retrospective documentation; preserve an authorized override and recovery route scaled to decision consequences, with feedback recorded for evaluation; this tests successful intervention before seeded high-impact incorrect actions are committed; the actual release condition is time to resolve substantiated challenges and proportion of cases with documented review.

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