Guides / Failed CCAR-F
Failed CCAR-F? Here's what to do next
A failed attempt on Claude Certified Architect - Foundations is recoverable. You can retake after a 14-day wait, up to 4 attempts in any rolling 12 months, and the retake fee is $125. This guide turns the rules into a plan.
1. Know your retake window
The wait grows with each failed attempt, so it pays to make the next sitting count.
| If you have failed | You can retake after | Fee for that attempt |
|---|---|---|
| 1 time | 14 days | $125 |
| 2 times | 30 days | $125 |
| 3 times | 90 days | $125 |
| 4 attempts used | Until the oldest attempt is more than 12 months old | - |
Full exam fee each attempt, with your Partner Network tier discount applied if you have one. Retake rules from Anthropic's Partner Academy FAQ, last checked 2026-09-21. Enter your fail date in the retake calculator for your exact earliest date.
2. Plan the cost of the next attempt
Every attempt is $125 before any tier discount, so 4 attempts in a window is at most $500 in exam fees. Add your own study or training spend in the cost calculator to see the full picture before you rebook.
3. Find where you lost points
Before you rebook, work out what to change. Take the free CCAR-F diagnostic for a per-domain score ranked weakest-first, and check whether your Pearson VUE score report gives any breakdown by domain.
Where the points are
The blueprint tells you where a re-study hour buys the most. The three heaviest domains carry about 67% of the exam.
| Domain | Exam weight | Practice questions here |
|---|---|---|
| Agentic Architecture & Orchestration | 27% | 75 |
| Claude Code Configuration & Workflows | 20% | 61 |
| Prompt Engineering & Structured Output | 20% | 49 |
| Tool Design & MCP Integration | 18% | 52 |
| Context Management & Reliability | 15% | 52 |
Architect Foundations puts the most weight on agentic architecture and orchestration, then Claude Code configuration, prompt engineering and structured output, tool design and MCP integration, and context management. Loop control (stop_reason, not text parsing or iteration caps), orchestration patterns, tool schemas, and context-window discipline are where scenario questions turn on one precise detail.
Common wrong turns in the heaviest domains
These are exam traps from this site's own CCAR-F lessons, one from each of the heaviest domains first. If you picked one of these on the real exam, that lesson is your next stop.
- Using response.content[0].type == 'text' to determine loop completion Claude can return text alongside tool_use blocks in the same response. Text presence does not indicate completion. The stop_reason field is the authoritative signal. Review: 1.1 - Agentic Loops
- New team member not receiving Claude Code instructions despite working on the same repo and branch The instructions are in user-level config (~/.claude/CLAUDE.md) instead of project-level. User-level is not version-controlled or shared via git. Move to .claude/CLAUDE.md for team-wide application. Review: 3.1 - CLAUDE.md Hierarchy, Scoping, and Modular Organisation
- Choosing 'be conservative' or 'only report high-confidence findings' as valid prompt improvements Vague instructions do not improve precision. The model has no actionable interpretation of 'conservative.' Specific categorical criteria defining exactly what to flag and what to skip are the correct approach. Review: 4.1 - System Prompts with Explicit Criteria
- Blaming downstream subagents for coverage gaps when the coordinator's task decomposition was too narrow Subagents research what they are assigned. If the coordinator only assigns solar and wind as subtopics for renewable energy, no subagent can cover geothermal or tidal. Trace failures to their origin - the coordinator's decomposition. Review: 1.2 - Multi-Agent Orchestration
- Creating a flat Markdown file directly inside .claude/skills/ (e.g., .claude/skills/review.md) and expecting a /review command The two paths create the same commands but have different file structures. A skill is a directory containing a SKILL.md entrypoint (.claude/skills/review/SKILL.md); a flat .md file only creates a command under .claude/commands/ (.claude/commands/review.md). A loose file dropped straight into .claude/skills/ is not picked up. Review: 3.2 - Custom Slash Commands and Skills
- Choosing 'add more detailed instructions' when output formatting is inconsistent If detailed instructions already exist and output is still inconsistent, adding more instructions will not fix the problem. Few-shot examples demonstrating the exact desired format are more effective for consistency. Review: 4.2 - Few-Shot Prompting
4. Re-plan your study time
Set a new exam date on or after your eligible retake date, then let the study time calculator turn it into a daily target and a domain-by-domain split weighted by the blueprint. Then work the weakest domains with drill mode and timed mocks.