- In short
- Matching scenarios to diagnosis and fix means applying the four-pattern framework and the diagnostic sequence together to a concrete description of underperforming output, in order to select the correct root cause and the remedy that follows from it. A summary that keeps missing undefined key points is under-specification, fixed by naming criteria. Format loss deep in a long chat is context overload, fixed by restarting from a summary or persisting the format. Shallow analysis on a speed-tier model is a wrong-model-tier problem, fixed by switching tiers, not adding prompt detail. Output that was fine last month and is now off, with an unchanged prompt, is stale configuration.
Turning the framework into a decision
Naming the four causes and knowing the diagnostic sequence are necessary, but the exam ultimately tests whether you can apply them to a concrete situation and land on the right fix. This is an apply-level knowledge point on the Claude Certified Associate - Foundations (CCAO-F) exam: given a described failure, produce the correct diagnosis and the remedy that follows from it. The two prior skills, reading symptom timing and the diagnostic sequence, are the tools; this is using them together under pressure.
The discipline is keeping diagnosis and fix aligned. Each cause has a matching remedy, and the wrong remedy for a correctly named cause fails just as surely as the right remedy for the wrong cause. A great deal of the exam's difficulty lives in the seam between "I know what is wrong" and "I know what to do about it," because the tempting fixes cross the wires: adding prompt detail to a model-tier problem, or restarting a session for an under-specified prompt.
- Matching diagnosis to fix
- The apply-level skill of taking a concrete description of underperforming output, using symptom timing and the diagnostic sequence to name the root cause, and then selecting the remedy that specifically addresses that cause rather than a plausible-looking but mismatched fix.
The four canonical scenario-to-fix mappings
Four canonical pairings anchor this skill. First: a summary that keeps missing the points that matter, because the prompt never defined what "key" means, is under-specification. The fix is naming the criteria for importance in the prompt, not restarting or upgrading anything. The output was never right because the prompt never carried the standard by which points count as key.
Second: output that follows a format at first and stops partway through a long conversation is context overload. The fix is restarting from a summary, or persisting the format as a standing instruction so it survives regardless of session length. Third: a request for thorough analysis that stays shallow despite added detail, when a fast model tier was chosen, is a wrong-model-tier problem. The fix is switching to a more capable tier, because the depth the task needs is a capability the speed tier does not supply. Fourth: output that was fine last month and is now off, with an unchanged prompt, is stale configuration, fixed by maintaining whatever standing instruction, knowledge source, or Skill has drifted.
What the CCAO-F exam trips candidates on
The first trap is trying to fix a wrong-model-tier problem by adding more and more prompt detail. When analysis stays shallow, the instinct is to keep enriching the prompt, but if the shallowness comes from a speed-oriented tier, no volume of detail creates depth the tier cannot produce. The exam sets up scenarios where the candidate has already "added detail" and it did not help, which is itself the signal that the cause is the tier, not the prompt.
The second trap is restarting the session for an under-specification failure. Because restarting is a familiar, satisfying reset, candidates reach for it when the real fix is naming the missing criteria in the current prompt. A restart clears context overload; it does nothing for a prompt that never specified what mattered. The pattern to internalise is that restart and summary belong to overload, prompt criteria belong to under-specification, tier switching belongs to model-tier depth, and maintenance belongs to stale configuration, and crossing those wires is the error.
Worked example
Two requests fail. In the first, a fresh chat asks Claude to 'summarise the key risks' of a report, but the summary keeps surfacing minor points and missing the ones the user cares about. In the second, a request for a thorough vendor analysis keeps returning shallow output even after the user pasted in more background; a lightweight, fast model tier is selected. Diagnose and fix each.
The first failure appears on early responses in a fresh chat and centres on the word "key." The user never defined which risks count as key, financial exposure, regulatory, operational, so Claude applied its own judgement of importance, which did not match the user's. This is under-specification. The fix is not a restart and not a stronger model; it is naming the criteria in the prompt: "prioritise risks with financial exposure over a threshold and any regulatory-compliance risks." Once the standard for "key" is explicit, the summary can hit the intended points.
The second failure is diagnostic in a different way. The user already added more background, which is the under-specification fix, and it did not help, that failed remedy is a clue. Shallow analysis that resists added detail, on a fast, lightweight model tier, is a wrong-model-tier problem. The depth the task needs is a capability of a more capable tier, not something more prompt content can conjure from a speed tier. The fix is switching to a model tier built for deeper reasoning. Piling on still more detail would repeat the move that already failed.
Together the two show the core skill: the same surface complaint, "the output is not good enough," resolves to two different causes and two different fixes, and choosing correctly depends on reading the details rather than reaching for a favourite remedy.
Common misreadings to avoid
Misconception
If analysis is too shallow, keep adding detail and context to the prompt until it deepens.
What's actually true
Misconception
Restarting the session is a safe general fix for most underperforming outputs.
What's actually true
How this shows up on the exam
Domain 7 apply-level questions give you a scenario and four options that each pair a diagnosis with a fix. The wrong options usually pair a plausible diagnosis with a mismatched fix, or name a fix that belongs to a different cause. The reliable method is to diagnose first, using timing and the sequence, then reject any option whose remedy does not match the cause you named.
This knowledge point draws on reading symptom timing and the cheapest-fix-first diagnostic sequence, and it depends on the finer distinction in wrong feature versus wrong model. It unlocks the hardest case in this task statement, recognizing a genuine task-fit mismatch, where none of the four fixes applies and the task itself must be reshaped. Master the matching and the evaluate-level judgement becomes reachable.
A user asks for a thorough competitive analysis on a fast, lightweight model tier. The output stays shallow even after the user adds more context and background. What is the diagnosis and fix?
People also ask
How do I choose the right fix for a bad Claude output?
What fixes under-specification versus context overload?
When should I switch model tiers instead of editing the prompt?
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.