Anthropic CCAR-P Exam Questions

Federated authorship allows each domain team to maintain the procedural knowledge it understands while preserving organization-wide trust through a central publication gate. Team authors can update coding standards, review practices, and postmortem procedures without waiting for a single platform group to write every change. Central reviewers can validate ownership, security, tool permissions, duplication, versioning, testing evidence, and compliance before publication. Per-developer or fully decentralized publication creates inconsistent and potentially unsafe Skills. Fully centralized authorship becomes a scalability bottleneck and separates content maintenance from domain expertise. Anthropic describes Skills as packages of instructions, scripts, and resources and warns that repository Skills may grant broad tool access, making formal review essential. Claude Code Skills

The required sequence must reduce repeated computation without changing the information or model capability used to generate projections. Prompt caching the static 6,000-token policy preamble directly addresses the largest cost contributor while preserving the complete instruction set. Anthropic states that cache reads cost substantially less than uncached input tokens, making repeated, stable prompt prefixes an ideal caching target. Prompt Caching

Caching frequently reused historical-sales chunks applies the same principle to the retrieval layer. When identical, version-controlled chunks are repeatedly fetched and supplied to the model, caching their retrieval or reusable representation eliminates redundant work while maintaining the same evidence available to the projection process. The cache must use appropriate invalidation or source-version keys so updated sales data cannot be replaced by stale content.

Options A and B modify the information supplied to Claude. Fewer sales chunks could remove relevant historical evidence, while truncating policy instructions could alter constraints or projection behavior. Option D introduces a model-capability change and therefore cannot guarantee unchanged accuracy without a comparative evaluation. Those interventions may be considered later, but only after representative regression testing establishes equivalence.

Study Guide references/topics: Cost profiling; prompt caching; retrieval caching; cache invalidation; accuracy-preserving optimization; model and context trade-offs.

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

Credentials must never be supplied as prompt content. Prompts can be retained in traces, debugging output, caches, or logs, and model output may inadvertently expose included secrets. Credentials should instead be resolved server-side through an approved secret store or delegated authentication mechanism. Option C is also a serious gap because post-response RBAC occurs after unauthorized data has already entered model context. Authorization must be enforced before retrieval and prompt construction. Options A, D, and E describe appropriate controls: least-privilege service identities, per-user scoped OAuth, and encrypted transport. Anthropic's prompt-leak guidance recommends excluding unnecessary sensitive information, while Claude Code security relies on permission-based enforcement rather than natural-language instructions alone. Reduce prompt leak

A constrained retrieval-augmented generation architecture best satisfies the grounding, citation, latency, cost, and audit requirements. The system first indexes the approved internal policy corpus. At request time, it retrieves a small set of relevant passages, supplies those passages to Claude with stable source identifiers, and requires the answer to cite the supporting material. Anthropic's search-result content blocks are specifically designed for this pattern: they allow custom RAG systems to provide source-attributed internal content and enable Claude to render citations against those results.

The retrieval boundary is critical. Only approved and version-controlled policy sources should be searchable, with document identifiers, effective dates, access controls, retrieval scores, and cited passages retained for audit reconstruction. This produces substantially more predictable evidence than unconstrained web research.

A planner-researcher-writer system introduces unnecessary model calls, orchestration complexity, cost, latency, and behavioral variance for routine policy lookup. Open-web browsing violates the authoritative-source requirement and increases prompt-injection and provenance risk. Concatenating the complete corpus into every prompt wastes tokens, increases latency, and can reduce retrieval precision as the corpus expands.

Study Guide references/topics: Search-result blocks for cited RAG; Claude citations; authoritative-corpus retrieval; source attribution; auditable context engineering.

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

The workflow must first identify where human judgment is necessary. Option E applies risk-based oversight by examining each decision's impact and reversibility. High-impact, irreversible, externally binding, privacy-sensitive, or legally consequential actions require stronger review than low-risk draft generation or easily reversible recommendations.

After locating those control points, Option A defines how work reaches reviewers. The sampling strategy should specify whether review is universal, random, risk-triggered, confidence-based, or stratified. Escalation criteria should cover policy violations, uncertain outputs, conflicting evidence, sensitive data, failed validation, and cases exceeding the reviewer's authority.

Anthropic recommends human confirmation for decisions with meaningful real-world consequences and actions requiring affirmative consent. Computer Use Security Considerations

Option B necessarily follows the pilot because findings must exist before design iteration. Reviewer onboarding and operational documentation in Options C and D are important readiness activities, but they follow the core design decisions being tested by this item: where oversight is required and how cases are sampled and escalated.

The completed pilot plan should subsequently include trained reviewers, documented procedures, queue capacity, SLAs, audit evidence, and measured inter-reviewer agreement.

Study Guide references/topics: Human-in-the-loop design; impact and reversibility; oversight points; sampling; escalation criteria; consequential decisions.

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