Weight: 17%. About 11 of the 63 exam questions.
This domain tests whether you can turn a business problem into a sound Claude architecture, and choose the simplest pattern that works.
| Objective | What it tests |
|---|---|
| 1.1 Business problem → solution | Framing the problem, finding where Claude adds value (and where it doesn't) |
| 1.2 End-to-end architecture | Input → processing → output → feedback loops, failure handling |
| 1.3 Architectural patterns | Augmented LLM, workflows (chaining, routing, parallelisation, orchestrator-workers, evaluator-optimiser), agents |
| 1.4 Multi-agent systems | When to split, orchestration, briefs, budgets, conflicts |
| 1.5 Decomposition | Map-reduce, hierarchical steps, verification boundaries, code vs model steps |
| 1.6 Business value pillars | Efficiency, transformation, productivity, cost, performance SLAs |
Mental model
- Start with the decision or outcome the business needs, not the technology.
- Use the simplest design that meets the requirement. Add agents, and then multiple agents, only when the task needs them.
- Deterministic rules belong in code; language and judgement belong with Claude.
Exam heuristics
- If the steps are known and fixed, choose a workflow. If the path depends on what's found, choose an agent, with bounds.
- If a scenario mentions audit or regulation, look for fixed, logged steps and human decisions at the right points.
- If the answer is "use the biggest model / more agents" without evidence, it's usually wrong.
- Value is always a measured change against a baseline.
Updated 2026-11-08