Anthropic CCAR-P Exam Prep
Claude Certified Architect - Professional (Page 5 )

Updated On: 3-Oct-2026

MULTIPLE CHOICE
A Claude architect at a health services organization is defining evaluation metrics for a clinical-summary pipeline. The pipeline must remain within a per-query cost ceiling and must never surface patient data to unauthorized roles.
Which two metrics directly address these requirements? (Select two.)

  1. BLEU score computed against a human-annotated reference summary set
  2. Role-based access-control enforcement rate measured on a red-team dataset
  3. Throughput measured as successful requests processed per minute
  4. Per-query token cost measured against the defined cost ceiling
  5. Response latency at the 95th percentile across a one-week sample window

Answer(s): B,D

Explanation:

The evaluation metrics must map directly to the two stated requirements. Role-based access-control enforcement rate, tested against a red-team dataset, measures whether requests from unauthorized identities, roles, or access paths are consistently denied. It converts the privacy and authorization requirement into an observable security metric and exposes bypass conditions that ordinary functional tests may miss. Because the requirement says patient data must never reach unauthorized roles, the acceptance threshold should be effectively 100% enforcement across representative and adversarial cases.
Per-query token cost directly measures compliance with the financial constraint. The metric should include uncached input, cache reads and writes where applicable, output tokens, thinking tokens, and any other billable components attributed to the request. Results can then be compared with the defined ceiling across normal, boundary, and worst-case inputs.
Anthropic's evaluation guidance identifies privacy preservation and price as distinct success criteria and emphasizes that criteria must be specific, measurable, and relevant to the application. Define Success Criteria and Build Evaluations
BLEU may assess textual similarity but does not test authorization or cost. Throughput and percentile latency are valuable operational metrics, yet neither directly answers the two requirements in the scenario.
Study Guide references/topics: Multidimensional evaluation; privacy preservation; authorization testing; red-team datasets; token-cost measurement; requirement-to-metric traceability.



HOTSPOT (Drag and Drop is not supported)

You are evaluating retrieval-strategy claims used by a peer team.
For each claim, select yes if the statement is generally accurate. Otherwise, select no.
QUESTION IMAGE:

  1. See Explanation section for answer.

Answer(s): A

Explanation:

CORRECT AREA HIGHLIGHTED



MULTIPLE CHOICE
An architect is reviewing a set of architecture documentation packages before handing off a Claude-based pipeline to an implementation team.
Which two characteristics indicate that a documentation package is sufficient to support implementation without ongoing architect involvement? (Select two.)

  1. The document specifies integration contracts, configuration schemas, and expected input/output shapes for each component.
  2. The document includes a decision log that records the rationale for key architectural choices and the alternatives rejected.
  3. The document provides a high-level narrative description of the business problem without component-level detail.
  4. The document includes the architect's contact information for questions arising during implementation.
  5. The document lists all Claude models that were evaluated but does not specify which was selected or why.

Answer(s): A,B

Explanation:

Implementation-ready documentation must provide both executable specifications and preserved architectural reasoning. Option A supplies the contracts an implementation team needs to build components independently: configuration schemas, accepted inputs, produced outputs, validation requirements, and integration boundaries. These details prevent teams from inventing incompatible assumptions about data structures, tool behavior, error handling, or component ownership.
Option B complements the technical contracts with a decision log. Recording the selected design, underlying constraints, alternatives considered, and reasons for rejection enables implementers to distinguish deliberate architectural decisions from accidental omissions. It also prevents previously rejected approaches from being reintroduced without new evidence.
A high-level business narrative in Option C may explain purpose but cannot direct component-level implementation. Contact information in Option D provides an escalation route, but documentation is not sufficient if routine progress still depends on the architect's availability. Option E records activity rather than a decision; a model list without the selected model and selection rationale leaves critical cost, latency, capability, and evaluation assumptions unresolved.
A strong handoff package should permit implementation, testing, and support teams to proceed while escalating only genuinely new architectural questions.
Study Guide references/topics: Architecture documentation; interface contracts; configuration schemas; Architecture Decision Records; implementation handoff; decision traceability.



Your organization is building a document analysis platform that must process PDFs from multiple data sources, extract structured data, and route documents to different downstream systems based on content classification. The system receives 500-1000 documents daily with varying complexity. You need to design the architecture to handle this scale while maintaining cost efficiency.
Which architecture pattern best addresses this requirement?

  1. Batch processing with async job queues, using Claude's batch API for high-volume document processing, with a classification layer that routes output to appropriate systems
  2. Real-time streaming pipeline where each document immediately calls Claude's standard API, with in-memory buffers to manage throughput
  3. Synchronous request-response model where all documents are processed sequentially through a single Claude API endpoint
  4. Distributed microservice architecture where each document spawns a separate container with its own Claude instance

Answer(s): A

Explanation:

The batch processing pattern using Claude's batch API is the optimal solution for high-volume, non-real-time document processing. The batch API provides significant cost savings (50% reduction) for asynchronous workloads and is specifically designed for scenarios like this where 500-1000 daily documents don't require immediate responses. This approach enables efficient use of resources, scalability through job queuing systems, and cost-effective classification logic. Real-time streaming would be unnecessary for batch documents and wastes resources. Sequential processing would create bottlenecks. Spawning separate containers per document is operationally complex and expensive.



HOTSPOT (Drag and Drop is not supported)

You are auditing a procurement-assistant agent whose defined responsibility is to draft purchase requests for review.
For each tool currently configured on the agent, select yes if the tool should remain after a least-privilege audit. Otherwise, select no if it should be removed.
QUESTION IMAGE:

  1. See Explanation section for answer.

Answer(s): A

Explanation:

CORRECT AREA HIGHLIGHTED



Viewing page 5 of 30
Viewing questions 21 - 25 out of 125 questions


Post your Comments and Discuss Anthropic CCAR-P exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!