- In short
- Matching technique to task applies the technique-selection heuristic to concrete tasks. A well-specified, low-ambiguity classification into a small fixed set of categories is typically zero-shot. Extracting structured fields from inputs with highly variable layout benefits from few-shot examples that demonstrate the target structure. A judgment that depends on multiple interacting conditions benefits from chain-of-thought so the reasoning path is made explicit and checkable. A short, simple summarization is usually zero-shot.
From heuristic to concrete tasks
The technique-selection heuristic is only useful if you can apply it to a real task in front of you. The Claude Certified Architect - Professional (CCAR-P) exam tests this at the apply level by handing you concrete tasks and asking which technique fits each. The skill is diagnosing where the difficulty of a task actually lives, in the format, in the judgment, or in the reasoning path, and choosing the technique that targets that specific difficulty, consistent with the lightest-that-works rule from technique selection by task complexity.
Four task shapes recur, and each has a natural technique. Learning the mapping, and the reasoning behind it, is what lets you answer these questions quickly and defend the choice.
- Matching technique to scenario-based tasks
- Applying the technique-selection heuristic to concrete task shapes. Fixed-category, low-ambiguity classification is typically zero-shot. Structured extraction from highly variable layouts benefits from few-shot examples demonstrating the target structure. A judgment with multiple interacting conditions benefits from chain-of-thought to make the reasoning path explicit. A short, simple summarization is usually zero-shot.
The four canonical mappings
Fixed-category classification is zero-shot. A well-specified, low-ambiguity classification into a small fixed set of standard categories, such as routing a ticket into billing, technical, returns, account, or general, is work the model handles reliably from instructions alone. The categories can be described in words, so examples add cost without adding capability.
Variable-layout extraction is few-shot. Extracting structured fields, such as date, vendor, and amount, from inputs whose layout and formatting vary widely benefits from examples that demonstrate the target structure. Here the difficulty is that the output shape is hard to describe across so many input formats, and a few worked examples show it directly, which is exactly what few-shot is for. Balance those examples across the layouts the system will see, per bias introduced by prompt construction.
Multi-condition reasoning is chain-of-thought. A judgment that depends on several interacting conditions, such as whether a contract clause creates a liability under conditions that interact, benefits from chain-of-thought so the reasoning path is made explicit and checkable. The difficulty is the reasoning itself, not the output format, so the technique that targets reasoning is the right one.
Short summarization is zero-shot. Condensing a short passage into a couple of sentences is a simple, well-specified task the model handles reliably without scaffolding.
What the exam trips candidates on
The two traps are mismatches between the technique and where the difficulty lives. The first is applying chain-of-thought to a short, simple summarization task where zero-shot already produces a reliable, concise result. A scenario will over-scaffold an easy task; the credited reading uses zero-shot. The second is choosing few-shot for a multi-condition reasoning task when the harder problem is the reasoning path itself, not the output format. A scenario will address a reasoning problem with format examples; the credited reading recognises that the difficulty is the reasoning and reaches for chain-of-thought.
Worked example
A team faces four tasks: (1) classify support tickets into five fixed categories, (2) extract date, vendor, and amount from receipts with wildly varying layouts, (3) decide whether a contract clause creates liability under three interacting conditions, and (4) summarize a 400-word product description into two sentences. Which technique fits each, and why?
The move is to locate each task's difficulty and match the technique to it.
Task 1 is a well-specified classification into a small fixed set. The categories are describable in words and the model handles them reliably, so the difficulty is essentially nil beyond stating the categories. Zero-shot fits; adding examples or reasoning would be the recurring tax the heuristic warns against.
Task 2's difficulty is the output structure across highly variable layouts. Instructions struggle to describe the target shape for every receipt format, but a few examples demonstrate it directly. Few-shot fits, with examples balanced across the layout variety the system will actually encounter.
Task 3's difficulty is the reasoning path: a liability judgment depends on three conditions that interact, so getting the answer right means getting the reasoning right. This is where chain-of-thought earns its place, making the path explicit and checkable. Choosing few-shot here would be the second trap, addressing a reasoning problem with format examples when the format was never the hard part.
Task 4 is a short, simple summarization the model handles concisely on its own. Zero-shot fits, and applying chain-of-thought would be the first trap, scaffolding an easy task for no gain.
The pattern across all four is the same: diagnose where the difficulty lives, then choose the technique that targets it, staying as light as the task allows.
Common misreadings to avoid
Misconception
Chain-of-thought makes a short summarization more reliable.
What's actually true
Misconception
A multi-condition reasoning task is best handled with a few good examples.
What's actually true
How this shows up on the exam
Apply-level questions present one or more concrete tasks and ask which technique fits. The reliable answer diagnoses where each task's difficulty lives and matches the technique: zero-shot for fixed-category classification and short summarization, few-shot for variable-layout structured extraction, and chain-of-thought for multi-condition reasoning.
This knowledge point operationalises technique selection by task complexity using the prompt technique taxonomy, and it depends on bias introduced by prompt construction when the chosen technique is few-shot and the examples must be balanced.
Which technique best fits deciding whether a contract clause creates liability under three conditions that interact with each other?
People also ask
Which prompt technique fits a classification task?
Which technique fits extraction from varied layouts?
When does a task need chain-of-thought?
Watch and learn
Official Anthropic Academy lessons first, then hand-picked walkthroughs. Videos load only when you press play.
No videos curated for this concept yet
We are still curating the best official and community videos for this topic.
Official prep for this domain
Anthropic's own free prep module for this part of the syllabus, on the official prep course. Free with an Anthropic Academy sign-in.
References & primary sources
Master this concept with Archie
Practice it inside an adaptive study session. Archie, your Socratic AI tutor, tracks your mastery with Bayesian Knowledge Tracing and schedules the perfect next review.