The CCAR-F Claude Certified Architect - Foundations exam asks candidates to make informed choices about real-world Claude solutions. That means preparation should be more than reading a list of terms. You need to practice connecting architecture, tools, workflows, prompts, and context to the requirements in a scenario.
CCAR-F practice questions with explanations can help you build that habit. They give you a problem to solve, answer options to assess, and a chance to review the reasoning behind the result. Used well, they can help you identify weak areas before exam day and make your study time more focused.
The Claude Certified Architect - Foundations certification validates foundational knowledge for implementing production-grade applications with Claude. The core technologies named in the outline are Claude Code, the Claude Agent SDK, the Claude API, and Model Context Protocol, or MCP.
The exam has 60 multiple-choice and multiple-response items. It uses four scenarios drawn from a bank of six, with a 120-minute time limit. The passing score is a scaled score of 720 on a scale of 100 to 1,000.
The five exam domains are:
| Domain | Weight |
|---|---|
| Agentic Architecture & Orchestration | 27% |
| Claude Code Configuration & Workflows | 20% |
| Prompt Engineering & Structured Output | 20% |
| Tool Design & MCP Integration | 18% |
| Context Management & Reliability | 15% |
Because the exam is scenario-based, a question may involve more than one domain. A tool integration decision can also affect context. A Claude Code workflow can influence how a team works with agentic applications. Practice should reflect these connections.
Answering a practice question is only the first step. The explanation is where you check your reasoning.
If you choose the correct answer, read the explanation anyway. It may confirm that you arrived at the answer for the right reason. If you choose an incorrect answer, use the explanation to identify the domain and decision you misunderstood. Then return to that topic before moving on.
A simple review note can be useful. After each question, record:
These notes become a targeted review list. They are more useful than rereading every topic with the same amount of attention.
Agentic Architecture & Orchestration is the largest CCAR-F domain at 27%. The expected experience includes building agentic applications with the Claude Agent SDK, multi-agent orchestration, subagent delegation, tool integration, and lifecycle hooks.
When you work through a practice scenario in this area, start by identifying the architectural goal. Is the scenario about coordinating agents, delegating work to a subagent, integrating a tool, or handling part of the application lifecycle? Then compare each answer option to that goal.
Do not rely on an option sounding technically advanced. The best answer is the one that matches the requirements in the question. Practice questions help you get used to separating a useful feature from the right design choice for a specific case.
Tool Design & MCP Integration accounts for 18% of the outline. Candidates should be able to design MCP tool and resource interfaces for backend system integration.
Practice questions can help you ask better design questions. What does the application need from the backend system? Is the scenario asking for a tool, a resource, or a particular interface decision? What information should be available to the application?
When reviewing an explanation, focus on the relationship between the interface and the stated requirement. That approach is more reliable than memorizing a list of terms without context.
CCAR-F includes Claude Code Configuration & Workflows, which represents 20% of the exam. This area covers CLAUDE.md files, Agent Skills, MCP server integrations, and plan mode for team workflows.
While practicing, imagine the people in the scenario as a team with a repeatable process. What needs to be configured? How does a shared instruction file affect the workflow? Where would a skill or MCP server integration fit? How could plan mode support the team's approach to a task?
This method turns configuration details into decisions with a purpose. It also makes the domain easier to recall when questions are written as scenarios instead of direct definitions.
Prompt Engineering & Structured Output also makes up 20% of the CCAR-F outline. The listed experience includes JSON schemas, few-shot examples, and extraction patterns.
For every prompt-related practice question, begin with the output requirement. If the application needs structured output, what should that output look like? Then consider which prompt technique makes the expected result clear. JSON schemas, examples, and extraction patterns each support structured output in different ways depending on the task.
After reading an explanation, summarize the answer in one sentence that starts with the requirement, not the technology. For example, write "The output needs a defined structure," before you write about the approach used to support it. This keeps your reasoning tied to the scenario.
Context Management & Reliability is 15% of the outline. It should not become the final topic you review once and then forget. Context connects with architecture, tools, and prompt design.
Add one question to every practice review: what information does the system need in context to produce a reliable result? This question helps you see how context management affects the whole solution rather than one isolated exam domain.
Use a repeatable routine when working through CCAR-F practice questions:
Multiple-response questions deserve extra care. Select only the number of answers requested, and test every choice against the facts in the scenario. An option can be useful in general and still not be one of the best answers for that question.
Start with Agentic Architecture & Orchestration because it has the highest weighting at 27%. Continue reviewing all five domains throughout your study plan, especially the two 20% domains: Claude Code Configuration & Workflows and Prompt Engineering & Structured Output.
No. The exam structure includes scenarios, so questions can require you to connect several parts of a solution. Practice by identifying the architecture, tool, workflow, prompt, and context details that matter in each scenario.
Use the explanation to verify your reasoning, not only to find the correct option. Write down the requirement that mattered and the domain you need to revisit. This turns each missed question into a focused study task.
Passing CCAR-F requires a working understanding of how Claude technologies fit together in a production application. Practice questions with explanations can help you strengthen that understanding when you review the reasoning behind every answer.
CertQuestionsBank publishes study content for certification candidates. Use this CCAR-F practice guide to organize your review, track the topics that need more attention, and prepare for the exam with a scenario-focused mindset.
About Us · User Accounts and Benefits · Privacy Policy · Management Center · FAQs
© 2026 MolecularCloud