The 30-Day CCA-F Study Plan: Pass on Your First Attempt

This study plan assumes you can write code in Python or TypeScript, you've made at least a few Claude API calls, and you're committing real evenings and weekends for the next month. If any of those don't apply, see our longer 8-week CCA-F study guide instead.

The plan at a glance

Week 1: API and tool use

The goal this week is to build instinctive familiarity with the Messages API and the tool-call loop.

Days 1–2: Messages API end-to-end

• Read the official Messages API documentation
• Build a CLI tool that takes a question, sends it to Claude, prints the response
• Add streaming — handle Server-Sent Events properly
• Switch your model between Opus, Sonnet, and Haiku for the same query and note the differences

Days 3–5: Tool use

• Add a single tool to your CLI tool — start with something concrete like "search a small local document set"
• Implement the tool-call → tool-result loop manually (no SDK yet — you want to understand what the SDK does)
• Add a second tool that has a deliberate failure mode and observe how Claude reasons about errors

Days 6–7: Token economics + rate limits

• Read about input vs. output token pricing and the model-class differences
• Add basic retry-with-backoff logic to your tool calls
• Build a simple cost estimator that logs the token usage of each call

Week 2: MCP and Agent SDK

The two heaviest domains, packed into one intense week.

Days 8–10: MCP

• Read the official MCP specification at the conceptual level — Resources, Tools, Prompts
• Build a minimal MCP server in your preferred language
• Connect it to Claude Code via your local config and verify the tools appear
• Read about authorization patterns — what happens when an MCP server has access to sensitive data

Days 11–14: Claude Agent SDK

• Read the SDK primer for the conceptual model
• Rebuild your week-1 agent using the SDK instead of the raw Messages API loop
• Add a PreToolUse and PostToolUse hook that logs to a file
• Add allowedTools and verify the SDK refuses calls outside the list
• Build a small two-agent system: a parent agent that delegates to a subagent with a different system prompt

Week 3: Production patterns and Claude Code

Days 15–17: Production patterns

• Prompt caching — add cache markers to your week-2 agent. Estimate the cost savings on a typical workflow.
• Safety and policy — read Anthropic's policy framework. Add input validation hooks to your agent.
• Cost engineering — switch between model classes for different sub-tasks of your agent. Notice the cost delta.
• Evaluation — build a small eval set (10–20 examples) for your agent. Run it. Measure success rate.

Days 18–21: Claude Code

• Install Claude Code, configure permissions for your dev environment
• Build a custom slash command for a workflow you do regularly
• Build a custom skill that wraps a frequent task with clear triggers
• Wire an MCP server (your week-2 one) into Claude Code's config
• Try one PreToolUse hook in Claude Code's settings to see how the harness fires events

Week 4: Practice tests and gap filling

Days 22–25: First practice test + review

• Take a full practice test under exam conditions (120 minutes, no interruptions)
• Review every wrong answer — go back to the relevant documentation
• List your three weakest topics — those become days 23–24 priority
• Spend a full day on each weak topic with hands-on practice

Days 26–28: Second practice test + targeted fixes

• Take another practice test
• If your score improved by 10+ points, your prep is working
• If not, audit your study approach — usually the issue is too much reading, not enough building
• Spend the remaining days on hands-on coverage of your weakest domain

Days 29–30: Final practice test + light review

• One last practice test — aim for 80%+
• Light review of the full study guide on day 30
• Sleep well before exam day — fatigue costs more points than any single weak topic

Common ways this plan fails

• Reading too much, building too little. If by day 14 you haven't built an agent with the SDK, restart your plan with more hands-on time.
• Skipping the practice tests. Practice tests aren't optional — they're the only way to surface what you don't know.
• Over-investing in one domain. If you spend three weeks on Tool Use because it's interesting, you'll fail Production Patterns. Stick to the weighted allocations.
• Cramming in week 4. Week 4 is for testing and gap-filling. New material learned in the last week rarely sticks in time for exam day.

Related reading

• Complete CCA-F study guide — the longer 8-week version
• Claude Agent SDK primer — the deepest single-domain dive
• 10 free CCA-F sample questions — gauge your readiness in 20 minutes

The bottom line

Thirty days works if you're disciplined about building and ruthless about practice tests. Front-load hands-on work, back-load testing, and don't fall into the trap of reading documentation instead of writing code. Most candidates who pass CCA-F in 30 days credit the practice-test discipline, not the reading.