この試験を受けるべき方
Claudeを本番環境で実際に扱った経験のあるソリューションアーキテクトが対象です
「この試験を受けるべき方」はCoddyKit上の無料Claude Architectレッスンです。 これはレッスン4/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはClaude Architect学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Claude Architectコースには全4レッスンが含まれています。
このレッスンの一部はまだ翻訳されておらず、英語で表示されています。
Who Is This Exam For?
The Claude Certified Architect exam is built for one audience: solution architects who already ship Claude in production. Every question is a real-world design decision.
The Core Requirement: 6+ Months
The clearest readiness signal: at least 6 months of hands-on production Claude experience. You've made real trade-offs — which tools to expose, how to stop a loop, when to escalate.
What 'Production Experience' Looks Like
You're a strong candidate if you've built a real agentic loop: send the full history, check stop_reason, run tools on tool_use, repeat until end_turn — and know why you never stop on the word 'done'.
import anthropic
client = anthropic.Anthropic()
messages = [{"role": "user", "content": "Refund order #4821"}]
while True:
resp = client.messages.create(
model="claude-sonnet-4-5",
max_tokens=1024,
tools=tools,
messages=messages, # FULL history every turn
)
if resp.stop_reason == "end_turn":
break # terminate on stop_reason, never on text
if resp.stop_reason == "tool_use":
messages.append({"role": "assistant", "content": resp.content})
messages.append({"role": "user", "content": run_tools(resp)})The Five Domains You'll Be Tested On
The exam covers five domains, weighted by real-world impact: D1 Agents 27%, D2 Tools/MCP 18%, D3 Claude Code 20%, D4 Prompting 20%, D5 Context 15%. Can you speak to all five from real projects?
You Think in Multi-Agent Systems
D1 is the heaviest at 27%. Strong candidates design hub-and-spoke multi-agent systems and know the key rule: subagents don't inherit the coordinator's history, so pass all context explicitly.
coordinator = AgentDefinition(
name="coordinator",
description="Decomposes the task and delegates to subagents",
system_prompt="Break the request into independent subtasks...",
allowed_tools=["Task"], # must include Task to spawn subagents
)
researcher = AgentDefinition(
name="researcher",
description="Researches ONE topic from the prompt it is given",
system_prompt="You receive full context in your prompt; you inherit none.",
allowed_tools=["WebSearch", "Read"], # least privilege
)You Know When to Use Hooks vs Prompts
You know hooks vs prompts: prompts are ~90% reliable guidance; hooks are 100% deterministic enforcement. When failure has financial, legal, or safety stakes, you reach for a hook.
# PostToolUse hook: deterministic policy gate
def on_refund_tool(tool_input):
if tool_input["amount"] > 500:
return {"block": True, "reason": "Refunds over $500 require a human."}
return {"block": False}You Live in Claude Code Daily
Domain 3 assumes real Claude Code fluency: the CLAUDE.md hierarchy (project files shared via VCS, user-level personal) and scoped .claude/rules/ that load only for matching files.
---
paths:
- "src/payments/**"
---
# Payments rules (loaded only when editing payment files)
- All money values are integer cents, never floats.
- Every refund path must call the PostToolUse policy hook.You Automate Claude in CI/CD
Wired Claude Code into CI/CD? You fit the profile: -p for non-interactive runs, --output-format json for parseable results, and review in an isolated session, not the one that wrote the code.
claude -p "Review the staged diff for correctness bugs only" \
--output-format json \
> review.json
# Isolated review session, not the generation session.
# Re-runs include prior results and report only new/unfixed issues.You Design Tools and Structured Output
Domains 2 and 4 reward treating tool descriptions as the selection mechanism, not names, and keeping 4-5 tools per agent. For structured output, force JSON Schema; never mark an absent field required.
resp = client.messages.create(
model="claude-sonnet-4-5",
max_tokens=1024,
tools=[extract_invoice_tool],
tool_choice={"type": "any"}, # must call a tool -> structured output
messages=messages,
)
# Schema: only 'invoice_id' is required; 'discount' may be absent -> optional.You Care About Context and Reliability
Domain 5 is staying correct over long sessions: progressive summarization makes numbers vague, so keep transactional facts verbatim. Escalate on real triggers, never on sentiment or self-rated scores.
case_facts = {
"order_id": "4821",
"amount_usd": 540.00,
"order_date": "2026-05-31",
} # kept verbatim, OUTSIDE the rolling summary
summary = summarize(history) # safe for prose, NOT for these numbersHow to Read Your Score
The format signals the audience: scenario-based MCQ, scaled 100 to 1000, pass 720, 4 of 8 scenarios, no guessing penalty. Experienced builders consistently outperform pure memorizers.
Quick Check: Are You the Right Candidate?
An engineer asks whether they should sit the Claude Certified Architect exam now. Based on the official audience, which profile is the best fit?
Recap: Who Should Take This Exam
Recap: audience is architects with 6+ months production Claude experience; scaled MCQ, pass 720; domains D1 27% to D5 15%. The mindset: stop on stop_reason, enforce with hooks, review in isolation.
よくある質問
「この試験を受けるべき方」レッスンは無料ですか?
はい。「この試験を受けるべき方」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し(組み込みコードエディタと24時間対応のAIチューター)、Claude Architectコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Claude Architectコースには全4レッスンが含まれています。
「この試験を受けるべき方」で何を学びますか?
Claudeを本番環境で実際に扱った経験のあるソリューションアーキテクトが対象です ブラウザで直接実行するハンズオンコードでClaude Architectを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。
Claude Architectを始めるのに経験は必要ですか?
事前経験は必要ありません。CoddyKitのClaude Architectは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン4/4です。
「この試験を受けるべき方」レッスンにはどのくらい時間がかかりますか?
ほとんどのCoddyKitレッスンは約5~10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。
このClaude Architectレッスンでコードを書いて実行できますか?
はい。すべてのClaude Architectレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。