CCDV-F Claude API Mechanics Practice Question
A developer is preparing a Messages API request and wants to give Claude a persistent persona: "You are a concise legal assistant. Never give advice outside contract review." Where should this instruction be placed so it applies to the whole conversation?
⚠ Common exam trap
The trap here is putting standing instructions into a user message or metadata field instead of the dedicated system parameter.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
In the system parameter, as the top-level system prompt for the request.
The system parameter is purpose-built for top-level instructions that define Claude's role, tone, and boundaries for the whole request. Placing the legal-assistant persona there gives it consistent influence over all turns and separates standing guidance from conversational content. Other fields either carry no model-visible text or serve unrelated control functions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
In the system parameter, as the top-level system prompt for the request.
Why this is correct
The system parameter is the designated top-level field for global instructions that shape Claude's role, tone, and constraints across the entire exchange. Placing the persona there ensures it frames every user and assistant turn without being treated as a user message. This is the intended location for standing behavioral guidance.
- ✗
As the first user message in the messages array, prefixed with "System:".
Why it's wrong here
The messages array accepts only user and assistant roles; a literal "System:" prefix does not create a system role and is just prose. While the text may influence output, it lacks the elevated framing of the system parameter and can be overridden as the conversation grows. The dedicated system field is the correct placement.
- ✗
Inside a metadata object attached to the request body.
Why it's wrong here
A metadata field is used for tagging requests for tracking or abuse monitoring and is not rendered into the model's context. Instructions placed there are never seen by Claude and have no effect on behavior. The persona must go into content-bearing fields such as system, not metadata.
- ✗
In the stop_sequences parameter so Claude stops when it deviates from the persona.
Why it's wrong here
stop_sequences lists strings that halt generation when produced; it cannot encode instructions or enforce behavior. Using it for a persona is a category error and would cause the model to stop on literal matches instead of acting as a legal assistant. Persona text belongs in the system parameter.
About these practice questions
Courseiva writes every CCDV-F question from scratch — 257 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Anthropic exam blueprint
This CCDV-F practice question is part of Courseiva's free Anthropic certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CCDV-F exam.