Claude Certification Blog
The CCDV-F objectives name the topic and withhold the verb
Ninety-six of the 121 objectives in the programme begin with an imperative verb. All 25 that do not are on the developer exam, and it has no verb-led objective at all.
The CCDV-F objectives are the only ones in the Claude programme written without a verb. Of the 121 objectives published across the four blueprints, 96 begin with an imperative — Create, Design, Diagnose, Evaluate — and all 25 that do not are CCDV-F’s, which are noun phrases without exception: Agent Architecture, Claude API Mechanics, Output Handling. The developer blueprint names the subject and withholds the action.
Ninety-six of 121 start with a verb
The first words on the other three read like a syllabus of actions. CCAO-F opens objectives with Create, Iterate, Adapt, Evaluate, Differentiate and Follow. CCAR-F with Design, Orchestrate, Enforce, Distribute and Preserve. CCAR-P with Translate, Analyze, Diagnose, Ensure and Support. CCDV-F opens with Agent, Claude, Software, Systems, Output, Cost and Identity.
The same subject, written twice
The clearest way to see the difference is to find a topic both styles cover and read them side by side. Every row below is the same subject on two different papers:
| Subject | On CCDV-F | Elsewhere in the programme |
|---|---|---|
| Prompting | Prompt Engineering | Iterate prompts to improve output quality |
| Context | Context Engineering | Manage conversation context to preserve critical information |
| Cost | Cost and Token Management | Optimize token usage, latency, and cost-performance trade-offs |
| Debugging | Debugging and Error Handling | Support debugging and operational issue resolution |
Read the right-hand column and you know what an item will make you do. Read the left and you know only that the subject is in scope. That is not a small difference when the whole purpose of an objective list is to tell a candidate what to prepare.
What a verb buys you
A verb names the cognitive level. Evaluate an output and design an output format are the same subject and different questions: one asks you to judge something in front of you, the other to produce something that does not exist yet, and they reward different reasoning under time pressure. Diagnose is different again — it presupposes something has already gone wrong.
So on three of the four papers the blueprint hands you the shape of the question for free, and a verb-led objective list converts directly into a revision checklist: you can rehearse the action, not just read about the topic. How that shape shows up in the stem itself is in how to read a Claude exam question.
What CCDV-F gives you instead
Here is the part that makes this a trade rather than a defect. CCDV-F is the only track in the programme that publishes a weight for every single skill — 25 of them, from Claude Application Design at 8.6% down to Claude Hooks at 1.0%. The other three publish weights at domain level only.
Which is genuinely useful in the opposite direction. On CCAO-F you can read that an objective asks you to iterate on prompts, and you cannot tell whether it carries four items or none, because six objectives share one domain weight. On CCDV-F you know before you start that hooks are worth about half an item and application design four or five — the consequences of which are in security and safety on CCDV-F and prompt and context engineering. The cross-exam picture of weights is in Claude certification domain weights.
Neither style is the complete one
A verb without a weight tells you what to rehearse and not how long to spend. A weight without a verb tells you how long to spend and not what to rehearse. Whichever paper you are sitting, the missing half is the thing you have to supply yourself — and knowing which half is missing is most of the work.
Studying a blueprint with no verbs
Supply the verb from two places. The first is the domain the objective sits in: Output Handling inside Prompt and Context Engineering is plainly about producing and checking a response, not about admiring one. The second, and better, is the rest of the programme — the other three blueprints name most of the same topics with the verbs attached, and that is the closest thing to an official gloss on what the developer track expects you to be able to do.
Then let the weights do the scheduling, which is the half CCDV-F actually does hand you. Size each session by the published skill weight rather than by how interesting the topic reads, and the blueprint’s silence about verbs costs you very little. The sequencing for all eight domains is in our Claude certification study guide, and the day-by-day version is in the two-week plan for CCDV-F.
Key takeaways
- 96 of 121 objectives are verb-led. All 25 exceptions are CCDV-F’s, and it has none at all.
- 2.9 words against 8.9, 8.1 and 7.3. The developer objectives are labels; the others are action statements.
- A verb names the cognitive level. Evaluate, design and diagnose are three different questions about one subject.
- CCDV-F trades verbs for weights. It is the only track publishing all 25 skill weights, down to 1.0%.
- Neither blueprint is complete. One withholds how much, the other withholds what to do.
- Borrow the missing verb. The other three papers name the same topics with the action attached.
A blueprint that tells you the size but not the shape
Reading an objective list is the cheapest preparation there is, and it is worth knowing which half of the question each list answers before you build a plan on it. The weights, domains and objectives for all four exams are published here.
See the CCDV-F blueprintQuestions
Frequently asked
The follow-up questions people search next.
Why do the CCDV-F objectives look so much shorter than the others?
Because they are noun phrases rather than action statements. CCDV-F’s 25 objectives average 2.9 words — "Output Handling", "Claude Hooks", "LLM Fundamentals" — while CCAO-F averages 8.9, CCAR-F 8.1 and CCAR-P 7.3, and every one of those is verb-led.
How many Claude exam objectives start with a verb?
Ninety-six of the 121 published across the four blueprints. All 25 that do not are CCDV-F’s, and CCDV-F has no verb-led objective at all — the split between the developer track and the other three is total, not a tendency.
Does that make CCDV-F harder to study for?
Harder to plan by objective, easier to plan by weight. A verb tells you the cognitive level an item will demand; a noun does not. But CCDV-F is the only track that publishes a weight for every skill, so you can size the work exactly even though the blueprint will not tell you what shape it takes.
What should I do with an objective like "Output Handling"?
Supply the missing verb yourself, from the domain around it and from how the programme phrases the same subject elsewhere. The other three blueprints name the same topics with verbs attached, which is the closest thing to an official gloss on what CCDV-F expects.
Is one style better than the other?
They trade. Verb-led objectives convert straight into a revision checklist but come with domain-level weights only, so you cannot tell which of six objectives in a domain carries the marks. CCDV-F inverts it: you know Claude Hooks is 1.0% and Claude Application Design is 8.6%, and neither tells you what you will be asked to do.
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.