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

Question 150

A generic subagent receives deployment tools while doing read-only documentation analysis. Which corrective change best addresses the root cause?

  1. Keep credentials out of prompts and versioned configuration
  2. Scope MCP connections by project and user identity
  3. Use specialized subagents with bounded tools and instructions
  4. Use deterministic hooks to enforce required developer gates

Explanation

Correct Answer

C:

Give each delegated role explicit objectives, context limits, and tool permissions with clear return artifacts; role-isolation tests prove that decomposition also restricts authority; verify the repair using subagent task completion with zero out-of-scope tool access.

Incorrect Answers

A:

Masking output after committing a secret cannot undo credential exposure or grant least privilege; use approved secret storage, scoped environment access, and redaction while avoiding credentials in repositories, prompts, or logs; that control is assessed by secret-scanning results and blocked exfiltration on seeded repository credentials; the incident instead requires subagent task completion with zero out-of-scope tool access.

B:

A working connection does not prove the assistant is restricted to the user's intended project resources; choose appropriate configuration scope and per-user or service authorization for MCP servers, avoiding shared cross-project secrets; that control is assessed by access denial for cross-project MCP resources under user identity tests; the incident instead requires subagent task completion with zero out-of-scope tool access.

D:

A written instruction alone is best-effort and does not guarantee enforcement of a critical command gate; configure supported hooks for deterministic checks at appropriate lifecycle points, with clear failure behavior and maintenance ownership; that control is assessed by hook execution and blocked noncompliant operations under simulated bypass attempts; the incident instead requires subagent task completion with zero out-of-scope tool access.

Question 151

Architecture review happens after deployment, revealing no documented legal basis or evaluation of employee privacy impact. Which corrective change best addresses the root cause?

  1. Assess privacy risks and lawful processing grounds early
  2. Apply accountable access, deletion, and retention processes
  3. Map data residency commitments to actual processing paths
  4. Check HIPAA business associate and safeguard requirements
  5. Minimize personal data and specify retention purpose

Explanation

Correct Answer

A:

Involve privacy counsel to assess applicable lawful bases, transparency, rights, and whether a data-protection impact assessment is required before release; compliance readiness must be demonstrated upstream of irreversible data processing; verify the repair using completion of required privacy assessment and recorded resolution of high risks before go-live.

Incorrect Answers

B:

Deleting the original row does not automatically erase embeddings, caches, or observability copies; map data copies, implement lifecycle deletion where required, and retain audit evidence of the authorized request and its completion; that control is assessed by deletion-request completion across all inventoried repositories within policy deadlines; the incident instead requires completion of required privacy assessment and recorded resolution of high risks before go-live.

C:

Locating the primary database domestically does not ensure every supporting service processes data there; trace storage, inference, retrieval, logs, backups, and subprocessors against contractual and legal location requirements; that control is assessed by verified geographic processing paths for all sensitive request components; the incident instead requires completion of required privacy assessment and recorded resolution of high risks before go-live.

D:

A provider security claim alone does not prove that the purchased deployment is contractually suitable for PHI; confirm the specific service and contract support relevant HIPAA obligations, including any required business associate agreement and safeguards; that control is assessed by approved contracting, access controls, and PHI data-flow verification for the selected service path; the incident instead requires completion of required privacy assessment and recorded resolution of high risks before go-live.

E:

Broad encryption does not justify collecting more personal data than the task needs; limit processing to necessary authorized fields, define a lawful purpose and retention controls, and document relevant privacy obligations; that control is assessed by sensitive-field inclusion rate in prompts and retention-policy compliance; the incident instead requires completion of required privacy assessment and recorded resolution of high risks before go-live.

Question 152

A catalog assistant suggests minor nonbinding product descriptions at very high volume. Which option addresses the immediate design need?

  1. Use risk-based sampling for low-impact decisions
  2. Escalate binding legal interpretations to qualified reviewers
  3. Capture reviewer overrides as structured improvement signals
  4. Give reviewers only necessary sensitive information

Explanation

Correct Answer

A:

Combine automated checks with representative human sampling and exception-based review scaled to risk; sampling effectiveness must balance residual errors and human capacity; evaluate the design with defect-detection rate and reviewer workload under a risk-tiered sampling policy.

Incorrect Answers

B:

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 defect-detection rate and reviewer workload under a risk-tiered sampling policy for the described use case.

C:

Record correction reasons, provenance, and case labels under retention rules to support evaluation and process redesign; counting approval clicks alone does not describe why humans disagreed with the AI; this alternative would measure recurrence rate of categorized, previously corrected error types; it does not establish defect-detection rate and reviewer workload under a risk-tiered sampling policy for the described use case.

D:

Minimize, redact, and scope information in review interfaces according to purpose and authorized reviewer role; human oversight is not permission to expand access to unrelated personal information; this alternative would measure unauthorized field exposure and successful review accuracy after data minimization; it does not establish defect-detection rate and reviewer workload under a risk-tiered sampling policy for the described use case.

Question 153

An architecture review must replay a historical assistant response from before several model, prompt, and connector upgrades. Which result would prove that the release manifest is sufficient for reproduction?

  1. Reproducibility of a sampled historical answer using its full manifest
  2. Successful completion of standard support drills by staff who did not build the system
  3. Successful containment time in a simulated stale-index incident
  4. Completeness of sensitive-data flow paths identified during security review

Explanation

Correct Answer

A:

Versioned provenance enables defensible debugging and rollback; measure reproducibility of a sampled historical answer using its full manifest at the release gate; maintain a release manifest linking model configuration, prompt, tool contracts, data versions, and evaluation results.

Incorrect Answers

B:

Independent operator readiness is stronger evidence than architect-led demonstrations; provide system overview, access setup, troubleshooting flowcharts, monitoring thresholds, and named support responsibilities; this tests successful completion of standard support drills by staff who did not build the system; the actual release condition is reproducibility of a sampled historical answer using its full manifest.

C:

A runbook is effective when a different on-call engineer can perform the recovery; maintain runbooks for detection, containment, safe fallback, rollback, and communication with named incident roles; this tests successful containment time in a simulated stale-index incident; the actual release condition is reproducibility of a sampled historical answer using its full manifest.

D:

Architecture diagrams are useful when they expose where protection and authority change; a current diagram should show data classes, flows, processing boundaries, identities, trust zones, and side effects; this tests completeness of sensitive-data flow paths identified during security review; the actual release condition is reproducibility of a sampled historical answer using its full manifest.

Question 154

A malicious attachment impersonates a developer instruction and attempts to redirect a tool call. Which change should the architect recommend first?

  1. Cap agent steps and resource expenditure
  2. Threat-model prompt injection across lower-trust inputs
  3. Counter automation bias with visible uncertainty and review
  4. Constrain outbound channels to prevent data exfiltration

Explanation

Correct Answer

B:

Model external content as untrusted input, test role spoofing and instruction attempts, and enforce downstream permissions regardless of the prompt; a realistic attack corpus exercises both model behavior and execution controls; verify the repair using unauthorized tool-action success rate over injected emails and documents.

Incorrect Answers

A:

Asking the model to 'be efficient' does not guarantee bounded autonomous execution; set per-task step, token, cost, and elapsed-time budgets with a clear abort and escalation state; that control is assessed by maximum resource usage and orderly termination on deliberately unsolvable tasks; the incident instead requires unauthorized tool-action success rate over injected emails and documents.

C:

A nominal human checkpoint is weak when the interface encourages blind confirmation; design review interfaces that expose citations, uncertainty, and targeted challenge checks rather than only an approval button; that control is assessed by reviewer error interception on seeded incorrect recommendations; the incident instead requires unauthorized tool-action success rate over injected emails and documents.

D:

Redaction of the final chat answer does not prevent a tool from transmitting data elsewhere; restrict egress destinations, data classes, and tool arguments at the network and application layers, with audit trails; that control is assessed by blocked unauthorized destinations and absence of confidential fields in egress logs; the incident instead requires unauthorized tool-action success rate over injected emails and documents.

Question 155

An insurance policy assistant is evaluated on both supported coverage questions and cases where the available documents provide no answer. Which analysis would reveal whether it abstains appropriately without sacrificing useful service?

  1. p95 time from user submission to fully validated answer under load
  2. Critical-class precision and recall on independently verified tax-code cases
  3. Fully loaded cost per correctly completed document
  4. Correct-answer rate at each supported coverage threshold including no-answer cases

Explanation

Correct Answer

D:

Coverage-risk curves expose the tradeoff between reliability and unnecessary handoffs; measure correct-answer rate at each supported coverage threshold including no-answer cases at the release gate; measure selective risk: error rate on answered items alongside abstention precision, coverage, and escalation cost.

Incorrect Answers

A:

Measuring the completed workflow captures actual end-user waiting, including downstream services; report p95 or p99 end-to-end latency over representative traffic rather than relying only on averages or raw model runtime; this tests p95 time from user submission to fully validated answer under load; the actual release condition is correct-answer rate at each supported coverage threshold including no-answer cases.

B:

Label-based metrics catch mistakes that surface-level satisfaction may conceal; measure the business decision against a labeled reference, with metrics weighted for costly errors and explicit acceptance thresholds; this tests critical-class precision and recall on independently verified tax-code cases; the actual release condition is correct-answer rate at each supported coverage threshold including no-answer cases.

C:

This metric includes rework rather than rewarding low-quality cheap drafts; relate full inference and review costs to accepted outcomes that meet the task rubric, not to requests attempted; this tests fully loaded cost per correctly completed document; the actual release condition is correct-answer rate at each supported coverage threshold including no-answer cases.

Question 156

A field-service pilot receives unfamiliar machine symptoms and must adapt its diagnostic path as new fault codes appear. Which observed result would justify allowing bounded exploratory tool calls?

  1. Rate of recommendations backed by all required completed stage checks
  2. Resolution of unseen diagnostic branches within a specified tool-call and time budget
  3. Completed valid classifications per batch window and cost per accepted record
  4. Disputed-case resolution with every refund still passing the identity and approval gates
  5. Correct citations to currently effective policy versions across update tests

Explanation

Correct Answer

B:

The agent must demonstrate flexible discovery without escaping its operational guardrails; measure resolution of unseen diagnostic branches within a specified tool-call and time budget at the release gate; bounded agentic planning chooses follow-up tools from observed evidence while enforcing time, budget, and tool permissions.

Incorrect Answers

A:

Stage-completion evidence verifies that mandatory controls were not left to agent discretion; explicit state transitions preserve required order, testing points, and deterministic branch conditions; Claude can supply judgment inside selected stages; this tests rate of recommendations backed by all required completed stage checks; the actual release condition is resolution of unseen diagnostic branches within a specified tool-call and time budget.

C:

Throughput and unit economics measure the benefit that a user-facing latency metric would miss; batch-oriented orchestration handles throughput, retries, and cost planning while preserving consistent model instructions for a noninteractive workload; this tests completed valid classifications per batch window and cost per accepted record; the actual release condition is resolution of unseen diagnostic branches within a specified tool-call and time budget.

D:

This tests flexible investigation and deterministic control at the same time; place bounded exploratory reasoning inside one stage of a deterministic state machine; enforce approval and write permissions outside the agent; this tests disputed-case resolution with every refund still passing the identity and approval gates; the actual release condition is resolution of unseen diagnostic branches within a specified tool-call and time budget.

E:

Version-aware citation checks show whether answers rely on authoritative current evidence; retrieval from a versioned, access-filtered source grounds answers in current documents and can expose the authoritative citation; this tests correct citations to currently effective policy versions across update tests; the actual release condition is resolution of unseen diagnostic branches within a specified tool-call and time budget.

Question 157

An all-tenant dashboard conceals sustained failure for a low-volume customer. Which corrective change best addresses the root cause?

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

Explanation

Correct Answer

A:

Break down latency, errors, and tool success by permission-safe tenant and workload dimensions with cardinality controls; segmented monitoring finds localized issues that global summary statistics miss; verify the repair using detection time for an injected single-tenant degradation.

Incorrect Answers

B:

General chat satisfaction metrics are too delayed and indirect to detect dangerous mutation spikes; monitor write volume, denials, unusual resource patterns, and action-specific thresholds with fast containment routing; that control is assessed by time to detect and stop a simulated unauthorized bulk-write burst; the incident instead requires detection time for an injected single-tenant degradation.

C:

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 detection time for an injected single-tenant degradation.

D:

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 detection time for an injected single-tenant degradation.

Question 158

On-call engineers know the architecture but lack the commands and authority to stop affected answers safely. What is the most direct remediation?

  1. Prepare operator onboarding and support handoff materials
  2. Version prompts, model routes, tools, and evaluation artifacts together
  3. Specify tool schemas, errors, and authorization contracts
  4. Document decisions with assumptions and reversal triggers
  5. Publish an incident runbook with containment and rollback steps

Explanation

Correct Answer

E:

Maintain runbooks for detection, containment, safe fallback, rollback, and communication with named incident roles; a runbook is effective when a different on-call engineer can perform the recovery; verify the repair using successful containment time in a simulated stale-index incident.

Incorrect Answers

A:

Source code alone rarely communicates the operational decisions and permission steps operators need; provide system overview, access setup, troubleshooting flowcharts, monitoring thresholds, and named support responsibilities; that control is assessed by successful completion of standard support drills by staff who did not build the system; the incident instead requires successful containment time in a simulated stale-index incident.

B:

Recording only the model name omits other behavior-changing dependencies; maintain a release manifest linking model configuration, prompt, tool contracts, data versions, and evaluation results; that control is assessed by reproducibility of a sampled historical answer using its full manifest; the incident instead requires successful containment time in a simulated stale-index incident.

C:

API examples without failure and permission semantics leave dangerous integration ambiguity; define typed inputs, outputs, error semantics, idempotency, required scopes, and audit obligations for tool boundaries; that control is assessed by consumer contract pass rate under timeouts, invalid arguments, and permission denials; the incident instead requires successful containment time in a simulated stale-index incident.

D:

Configuration exports show what exists but rarely why it was chosen; record architectural context, alternatives, decision rationale, constraints, and explicit conditions for revisiting choices; that control is assessed by ability to identify affected decisions after simulated policy and workload changes; the incident instead requires successful containment time in a simulated stale-index incident.

Question 159

A logistics sponsor asks to automate ten departments simultaneously before any operational acceptance criteria have been tested. Which strategy should be prioritized for this requirement?

  1. Translate vague accuracy demands into task-specific criteria
  2. Map available data and its permitted uses before solution selection
  3. Pilot one bounded workflow with acceptance gates
  4. Measure the current manual task before choosing automation

Explanation

Correct Answer

C:

A narrow pilot validates one representative flow and pre-agreed quality, latency, and escalation thresholds before scaling to other workflows; a bounded deployment can prove business fitness before a large enterprise-wide dependency is created; evaluate the design with passing the acceptance gate on a representative pilot cohort including difficult exceptions.

Incorrect Answers

A:

Convert vague requests into observable task outcomes, rubric-based quality dimensions, and failure thresholds that stakeholders can agree to test; a clear success rubric evaluates outcomes but cannot on its own implement retrieval access controls; this alternative would measure agreement between domain reviewers on a rubric and pass rate against a labeled acceptance set; it does not establish passing the acceptance gate on a representative pilot cohort including difficult exceptions for the described use case.

B:

Data-readiness and usage-rights mapping identifies legitimate inputs, owners, quality gaps, and prohibited transfers before committing to an implementation; a data inventory does not alone identify target SLOs or decide whether an orchestration loop is necessary; this alternative would measure percentage of required fields with validated owners, quality checks, and approved processing purposes; it does not establish passing the acceptance gate on a representative pilot cohort including difficult exceptions for the described use case.

D:

A baseline separates real business improvement from attractive demos; use completed cases, reviewer effort, errors, and exception handling as measurable comparators; process measurement establishes value, not the identity, data-permission, or runtime architecture of a Claude application; this alternative would measure change in verified minutes and rework per adjudicated claim versus the documented baseline; it does not establish passing the acceptance gate on a representative pilot cohort including difficult exceptions for the described use case.

Question 160

A project chooses one deployment platform based on data-residency and latency assumptions. What is the most defensible next step?

  1. Document decisions with assumptions and reversal triggers
  2. Publish an incident runbook with containment and rollback steps
  3. Prepare operator onboarding and support handoff materials
  4. Specify tool schemas, errors, and authorization contracts

Explanation

Correct Answer

A:

Record architectural context, alternatives, decision rationale, constraints, and explicit conditions for revisiting choices; assumption-aware ADRs support controlled adaptation rather than accidental drift; evaluate the design with ability to identify affected decisions after simulated policy and workload changes.

Incorrect Answers

B:

Maintain runbooks for detection, containment, safe fallback, rollback, and communication with named incident roles; a high-level diagram alone is not an executable incident response procedure; this alternative would measure successful containment time in a simulated stale-index incident; it does not establish ability to identify affected decisions after simulated policy and workload changes for the described use case.

C:

Provide system overview, access setup, troubleshooting flowcharts, monitoring thresholds, and named support responsibilities; source code alone rarely communicates the operational decisions and permission steps operators need; this alternative would measure successful completion of standard support drills by staff who did not build the system; it does not establish ability to identify affected decisions after simulated policy and workload changes for the described use case.

D:

Define typed inputs, outputs, error semantics, idempotency, required scopes, and audit obligations for tool boundaries; aPI examples without failure and permission semantics leave dangerous integration ambiguity; this alternative would measure consumer contract pass rate under timeouts, invalid arguments, and permission denials; it does not establish ability to identify affected decisions after simulated policy and workload changes for the described use case.

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