Claude Certification Blog

JSON schemas on the Claude exams: one objective, and not the one you expect

Exactly one objective in the whole Claude programme names a JSON schema, and it is not on the exam most candidates would guess.

1 of 121 objectivesOn CCAR-F2.6% on CCDV-F

6 min read

Search all 121 objective titles published across the four Claude blueprints for the words schema, JSON or structured output and you get one hit. It is CCAR-F O21 — Enforce structured output using tool use and JSON schemas — on the architect foundations paper, inside a domain worth 20% of it. The developer exam, which most candidates assume owns this subject, names it as O18 Output Handling, published at 2.6%.

1objective names a schema
20%the domain holding it
2.6%the CCDV-F equivalent
0on CCAR-P

One objective in 121

Where the four blueprints put structured outputWHERE THE SUBJECT LIVESCCAR-FO21 enforce, 20% domainCCDV-FO18 Output Handling, 2.6%CCAO-FFormats, not schemasCCAR-PNot named at all
The word enforce appears once in the programme, on the architect foundations paper.

This is a scoping observation, not a claim that only one exam cares about output shape. All four papers ask about getting usable responses back. What differs is how explicitly each blueprint commits to the mechanism — and only one of them puts a schema in an objective title.

Where candidates expect it

On the developer track, reasonably enough. Schemas are a developer-facing concern, the CCDV-F blueprint has a whole domain called Prompt and Context Engineering, and the natural assumption is that the exam for people writing the integration is the exam that tests the contract.

The published weights say otherwise. Output Handling is 2.6% of CCDV-F — roughly one item — while CCAR-F Domain 4 is 20% and holds both O21 and the few-shot prompting objective beside it. Someone preparing for the developer paper who spends an evening on schema mechanics has prepared thoroughly for a different exam. The trade that pays on CCDV-F is Applications and Integration at 33.1%, which is a third of the paper on its own.

What each paper actually asks

ExamObjectiveHow the blueprint words it
CCAR-FO21Enforce structured output using tool use and JSON schemas
CCDV-FO18Output Handling
CCAO-FO10Select appropriate output formats, including structured formats for data
CCAR-PNo objective names schema, JSON or structured output

Read down the right-hand column and the difference is a verb. CCAR-F says enforce, which is a mechanism question: which layer makes the shape hold, and what happens when the model would rather not. CCAO-F says select, which is a fit question about matching a format to an audience. CCDV-F says nothing at all about what to do — a pattern that runs through its whole blueprint, as what the CCDV-F objectives don’t tell you sets out.

A schema promises shape, never truth

Whichever paper you are sitting, this is the distinction that decides items. A response can validate perfectly against a schema and still be a truncated answer or a confident invention. The shape is guaranteed; nothing about the contents is.

How much time this deserves

On CCAR-F, real time — it sits in a fifth of the paper, next to prompting objectives that share the same domain weight, and the mechanics are worth knowing properly. How tool use and structured output actually work is in Claude tool use and structured output, which covers both exams and goes into the round trip in detail.

On CCDV-F, twenty minutes, and spend it on the guarantee rather than the syntax: what a schema constrains, what it does not, and why checking why a generation stopped comes before parsing what it returned. That is the examinable core of a 2.6% skill and it transfers to the heavier domains besides. Sequencing all eight is in our Claude certification study guide, and the domain-by-domain weights across all four papers are in Claude certification domain weights.

Key takeaways

  • One objective in 121 names a JSON schema. CCAR-F O21, and it is the only one in the programme.
  • It is not on the developer paper. CCDV-F names the subject as Output Handling, published at 2.6%.
  • The difference is the verb. CCAR-F says enforce; CCAO-F says select; CCDV-F says nothing.
  • CCAR-P names none of the three terms. Not schema, not JSON, not structured output.
  • Weight your reading to your paper. A fifth of CCAR-F, about one item of CCDV-F.
  • Shape is not truth. A valid response can still be truncated or invented, and that distinction is examinable everywhere.

The same subject, weighted eight times differently

Assuming a topic sits where it feels like it should is one of the cheaper ways to lose an evening. The objectives, domains and published weights for all four exams are here, so you can check before you plan rather than after.

See the CCAR-F blueprint

Questions

Frequently asked

The follow-up questions people search next.

Which Claude exam covers JSON schemas?

CCAR-F, the architect foundations exam. Of the 121 objectives published across all four blueprints, exactly one names a JSON schema: O21, "Enforce structured output using tool use and JSON schemas", inside a domain worth 20% of that paper.

Does the developer exam test JSON schemas?

It tests the subject, but names it far more narrowly. CCDV-F calls it O18 "Output Handling", published at 2.6% — about one item on a 53-item paper — and its objective title contains no mention of schemas, JSON or enforcement.

Why does that difference matter for studying?

Because effort follows the word "enforce". On CCAR-F the blueprint asks you to make a shape hold, which is a mechanism question. On CCDV-F it asks about handling output, which is a judgment question about what a response guarantees. The same reading serves both badly if you assume the developer paper is the schema paper.

What does CCAO-F say about structured output?

Objective O10 asks you to select appropriate output formats and mentions structured formats for data, alongside artifacts and inline responses. It names a shape without naming any way to enforce one, which fits an exam about using Claude rather than building on it.

Is a schema a guarantee that the answer is right?

No, and that distinction is examinable in its own right. A schema constrains the shape of a response and says nothing about whether the contents are true, complete, or the result of a generation that finished.

Keep reading

Related posts

Not affiliated with, or endorsed by, Anthropic or Pearson VUE. Details are summarised from publicly published program information and can change — always confirm against the official exam guide before booking.

We use cookies and privacy-friendly analytics to understand usage and improve Cred Farmer. Essential features work either way. See our Cookie Policy.