Free Anthropic CCAR-P Practice Exam with Questions & Answers

Least privilege means granting the exact capabilities required for the defined responsibility—no more and no less. Option B permits the assistant to read the approved knowledge base and write only to the draft queue. Enforcing the allow-list at the orchestration layer creates a deterministic authorization boundary outside the model’s prompt and reasoning.

The rule should also be role-specific so different users or operational roles receive only the tools and data scopes they require. The knowledge-base tool should remain read-only, while the draft-queue tool should be restricted to draft creation rather than external sending, approval, or production publication.

Option A exposes every globally readable tool, creating unnecessary access to unrelated information. Option C relies on voluntary model behavior instead of enforceable authorization. A mistaken tool selection or successful prompt injection could therefore invoke an inappropriate capability. Option D minimizes permissions by eliminating the assistant’s required functionality and is not a viable least-privilege implementation.

Anthropic’s permission guidance distinguishes allow, ask, and deny rules and confirms that these controls are enforced by Claude Code rather than by model instructions. Configure Permissions

Study Guide references/topics: Least privilege; per-role authorization; orchestration-layer enforcement; capability scoping; read/write separation; tool allow-lists.

===============

Project scope is designed for repository-specific configuration shared through version control, including MCP server definitions, project permissions, hooks, and team instructions. This gives every contributor a consistent baseline while keeping changes reviewable. Managed configuration is appropriate for mandatory security and compliance controls because administrators can deploy it centrally and prevent lower scopes from overriding it. Local scope is machine-specific and unsuitable for organization-wide enforcement. User scope follows one engineer across projects, so it cannot guarantee that an entire team receives identical MCP definitions. Personal editor preferences belong in user or local configuration, not project scope, unless the team has explicitly standardized them. Anthropic’s settings hierarchy distinguishes managed, project, local, and user responsibilities. Claude Code settings

Prompt caching reduces repeated input processing when a stable system prefix is reused, directly lowering input cost and processing latency. Model routing provides the second optimization: routine cases can use a faster, lower-cost model, while difficult cases retain access to the more capable model. The routing policy must be validated against representative evaluations to confirm that quality remains within the required threshold. Increasing max_tokens can increase output cost and generation time. Retrieving the complete corpus and adding examples to every request both enlarge the input, worsening latency and token consumption. Anthropic identifies prompt caching as a cost-and-latency optimization and recommends selecting a model according to the workload’s quality, speed, and economic requirements. Prompt caching ; reducing latency

The pilot must test a deliberately designed workflow, not technology added without role boundaries. Option B identifies where Claude provides measurable value and where approval, accountability, or consequential decisions must remain human responsibilities. Option E establishes the technical environment required for consistent pilot execution: repository-shared MCP servers, scoped permissions, specialized subagents, and persistent project instructions. Iteration in Option D necessarily follows observed pilot findings. Formal approval from every manager is unnecessarily broad unless required by organizational governance. Complete runbooks and final handoff documentation mature after the workflow has been validated, although essential pilot procedures must exist. Anthropic documents project-level instructions, permissions, MCP servers, and subagents as complementary mechanisms for team workflows. Claude Code extension overview

The assistant is making recommendations without considering information that specialists regard as material. That is a direct input-scope and requirements gap, not merely a presentation issue. The 89 percent acceptance metric is also incomplete because initial acceptance does not reveal whether recommendations remain correct after users apply the omitted criteria. Production readiness requires outcome-focused evaluation, including final recommendation agreement, override reasons, financial impact, supplier risk, and performance across representative procurement scenarios. Options B and E raise possible concerns, but the scenario supplies no evidence that response rate or pilot duration is the demonstrated deficiency. Option A incorrectly treats a single proxy metric as sufficient. Anthropic recommends multidimensional, task-specific success criteria aligned with the actual user outcome. Define success criteria and evaluations

Option B targets two major contributors to per-turn latency: retrieved-context size and repeated prompt processing. Reducing retrieval to an empirically validated top- k limits the tokens Claude must process while preserving the passages that historically provide sufficient answer coverage. Caching the stable system-prompt prefix avoids repeatedly processing identical instructions.

Anthropic’s latency guidance recommends choosing an appropriate model and reducing unnecessary input and output tokens. Its prompt-caching documentation explains that caching reusable prompt prefixes can reduce both repeated processing cost and latency. Reducing Latency , Prompt Caching

The retrieval depth must be selected through evaluation rather than arbitrary truncation. The team should compare answer quality, retrieval recall, latency, and failure rates across candidate values and retain escalation logic for complex queries requiring deeper retrieval.

Option A removes an applicable latency optimization. Option C maximizes context consumption regardless of demonstrated benefit. Option D deliberately selects the slowest model class even though routine-turn quality already meets requirements.

Study Guide references/topics: Latency optimization; top- k retrieval; prompt caching; token reduction; quality–latency evaluation; adaptive retrieval.

===============

Lifecycle continuity depends on preserving validated knowledge and feeding operational learning back into subsequent phases. Carrying the evaluation framework and reference set forward, as stated in Option B, creates a stable baseline across prompt changes, model migrations, retrieval adjustments, and architectural revisions. Rebuilding the evaluation system each time would undermine longitudinal comparison because changes in the test framework could be mistaken for changes in solution performance.

Option D establishes the second essential continuity mechanism: lessons from discovery, design, implementation, deployment, and production monitoring become explicit inputs to the next phase. This closes the feedback loop and prevents recurring defects, invalid assumptions, and operational findings from being lost at organizational handoffs.

Option A is overly mechanical. Stakeholders should receive communications relevant to their responsibilities and decision rights, not indiscriminate notifications at every transition. Option C confuses comprehensive archival with lifecycle continuity; retention must follow business, regulatory, security, and records-management requirements rather than an unconditional “archive everything” policy. Option E is directly contrary to iterative architecture. Decisions should be documented and governed, but material evidence or changed requirements must be allowed to reopen them.

Study Guide references/topics: Lifecycle phases; evaluation continuity; reference datasets; feedback loops; lessons learned; decision records; iterative architecture governance.

===============

Responsible deployment requires users to receive an accurate representation of the system with which they are interacting. Option C provides that transparency while also establishing a practical escalation path. Disclosure should be proportionate to the material role AI plays, expressed in language appropriate to the audience, and aligned with organizational policy and applicable regulatory obligations.

A documented human-contact route is important when the assistant cannot resolve an issue, produces a disputed result, encounters a high-impact exception, or handles a matter requiring human authority. Anthropic’s Responsible Scaling Policy recognizes escalation to human reviewers as an appropriate safeguard for edge cases and situations requiring human judgment. Responsible Scaling Policy

Options A and D intentionally conceal material AI involvement from affected users, weakening informed decision-making, auditability, and trust. Option B is also unsuitable because transparency does not require revealing proprietary prompts, confidential controls, or internal security mechanisms; however, it does require an honest explanation of AI involvement and the system’s operational role.

The correct design combines disclosure, understandable limitations, human escalation, and records demonstrating that the organization’s transparency requirements are consistently applied.

Study Guide references/topics: AI transparency; informed user interaction; human escalation; responsible deployment; disclosure policy; operational accountability.

===============

Risk-stratified sampling concentrates limited reviewer capacity where error consequences and uncertainty are greatest. All low-confidence and high-impact cases should receive mandatory review, while random sampling of routine high-confidence outputs provides an unbiased signal for drift, unexpected failure modes, and overconfident errors. Complaint-only monitoring discovers defects after harm occurs. Reviewing only high-confidence cases systematically ignores the most dangerous outputs. Universal review provides maximum coverage but contradicts the stated throughput constraint and may create queues that undermine service objectives. The sampling policy should define confidence calibration, impact categories, escalation thresholds, review SLAs, and periodic adjustment based on observed error rates. Reviewer decisions should feed the evaluation dataset so monitoring quality improves over time.

Approval-rate parity measures whether groups receive positive recommendations at similar rates. It does not establish whether false approvals, false denials, sensitivity, specificity, or calibration are comparable across those groups. A system can therefore satisfy aggregate approval parity while imposing materially different error burdens on protected populations. The evaluation must include subgroup confusion matrices, false-positive and false-negative rates, calibration, intersectional analysis, and confidence intervals.

The 94 percent agreement rate measures fidelity to human underwriter decisions, not fairness. Human decisions are not automatically unbiased ground truth. If historical underwriting practices contain structural, procedural, or measurement bias, a model that reproduces those decisions accurately can reproduce the same bias. The reference labels must therefore be independently assessed for legitimacy, consistency, and potential discriminatory effects.

Nothing in the scenario establishes that protected groups were omitted, so D is unsupported. Similarly, sample size may require examination, but the scenario provides no statistical information proving that sample size is the principal deficiency. The evidence already contains two identifiable conceptual gaps regardless of sample size.

Study Guide references/topics: [Defining multidimensional evaluation criteria](https://docs.anthropic.com/en/docs/build-with-claude/develop-tests); fairness measurement; subgroup error analysis; label and benchmark bias; human-baseline limitations; governance evidence.

===============