Skip to content

Claude Certified Architect - Foundations (CCAR-F) Flashcards

64 cards from this guide's fact sheet and notes. Click a question to reveal the answer.

To study with spaced repetition, download flashcards.csv and import it into Anki or Quizlet (comma separated, first row is the header). Back to the study guide.

Exam logistics

How long is the Claude Certified Architect - Foundations (CCAR-F) exam?

120 minutes

How many questions are on the Claude Certified Architect - Foundations (CCAR-F) exam?

60 multiple-choice and multiple-response, scenario-based

What is the passing score for Claude Certified Architect - Foundations (CCAR-F)?

720 / 1000

What does the Claude Certified Architect - Foundations (CCAR-F) exam cost?

$125 USD

How long is Claude Certified Architect - Foundations (CCAR-F) valid for?

12 months, free non-proctored on-time renewal

How is the Claude Certified Architect - Foundations (CCAR-F) exam delivered?

Pearson VUE (online proctored or test center)

Agentic architecture

Autonomy (agentic architecture)

Claude decides which tools to call and in what order

Iteration (agentic architecture)

Multiple rounds of tool calls and reasoning

Goal-directed behavior (agentic architecture)

Claude works toward completing a defined objective

Dynamic decision making (agentic architecture)

The path is not predetermined; it depends on intermediate results

Rate Limits (agentic architecture)

Production rate management

Claude code configuration

User settings (claude code configuration)

~/.claude/settings.json - Personal settings

Project settings (claude code configuration)

.claude/settings.json - Project-specific settings (checked into repo)

Enterprise settings (claude code configuration)

Managed centrally by administrators

Allowed tools (claude code configuration)

Tools that can run without asking for permission

Denied tools (claude code configuration)

Tools that are blocked entirely

Default behavior (claude code configuration)

Unspecified tools prompt for approval

PreToolUse (claude code configuration)

Runs before a tool is executed. Can block the tool execution.

PostToolUse (claude code configuration)

Runs after a tool completes. Can process or validate results.

Notification (claude code configuration)

Runs when Claude Code sends a notification

Pre-tool: Linting (claude code configuration)

Run linter before file writes to ensure code quality

Pre-tool: Validation (claude code configuration)

Check that proposed changes meet project standards

Pre-tool: Security scanning (claude code configuration)

Scan for secrets or vulnerabilities before committing

Post-tool: Formatting (claude code configuration)

Auto-format files after Claude writes them

Post-tool: Testing (claude code configuration)

Run relevant tests after code changes

Post-tool: Notifications (claude code configuration)

Alert the team when significant changes are made

stdio (claude code configuration)

For local MCP servers. Claude Code spawns the process and communicates via stdin/stdout.

Streamable HTTP / SSE (claude code configuration)

For remote MCP servers. Claude Code connects via HTTP.

Prompt engineering structured output

Clarity (prompt engineering structured output)

Claude clearly distinguishes between instructions, context, and data

Parsing (prompt engineering structured output)

You can ask Claude to wrap its output in XML tags for easy extraction

Organization (prompt engineering structured output)

Complex prompts become readable and maintainable

Referencing (prompt engineering structured output)

You can refer to tagged sections by name (e.g., "use the data in ")

Zero-shot (prompt engineering structured output)

Task is straightforward and Claude handles it well without examples

Few-shot (2-5) (prompt engineering structured output)

Format or behavior needs demonstration; common choice

Many-shot (10+) (prompt engineering structured output)

Highly specific or nuanced task requiring precise pattern matching

Temperature (prompt engineering structured output)

Controls randomness in output (0 to 1)

Top-p (prompt engineering structured output)

Alternative to temperature, controls diversity

Top-k (prompt engineering structured output)

Limits the number of tokens considered at each step

Tool design mcp integration

Standardization (tool design mcp integration)

One protocol for all tool integrations

Reusability (tool design mcp integration)

Build a server once, use it with any MCP client

Discovery (tool design mcp integration)

Clients can discover available tools, resources, and prompts

Security (tool design mcp integration)

Defined authorization and capability negotiation

Host (tool design mcp integration)

The AI application (e.g., Claude Desktop, Claude Code, your custom app)

Client (tool design mcp integration)

The MCP client within the host that manages server connections

Server (tool design mcp integration)

A service that exposes tools, resources, and prompts via MCP

Shared team server (tool design mcp integration)

Use streamable HTTP

Cloud-hosted service (tool design mcp integration)

Use streamable HTTP

Resources (tool design mcp integration)

Read-only data access. The model requests data by URI.

Tools (tool design mcp integration)

Executable functions with parameters. The model calls a function.

TypeScript (tool design mcp integration)

@modelcontextprotocol/sdk

Context reliability

Cost (context reliability)

Thinking tokens add to the total cost of each request

Latency (context reliability)

Extended thinking takes additional time before the response

Quality (context reliability)

Generally improves quality for complex tasks

Streaming (context reliability)

Thinking content is delivered as a single event, then response streams normally

Base delay (context reliability)

Start with 1-2 seconds

Exponential increase (context reliability)

Double the delay on each retry

Jitter (context reliability)

Add random variation to prevent thundering herd

Max delay (context reliability)

Cap at 30-60 seconds

Max retries (context reliability)

Typically 3-5 attempts

Requests per minute (RPM) (context reliability)

Maximum number of API requests per minute

Tokens per minute (TPM) (context reliability)

Maximum input + output tokens per minute

Tokens per day (TPD) (context reliability)

Maximum tokens per day (some tiers)

Exam tips prep strategy

Anthropic Academy (exam tips prep strategy)

Free official courses

Anthropic Documentation (exam tips prep strategy)

Primary reference