CCDV-F Prompt and Context Engineering Practice Question
When should you use the 'system' field versus putting instructions in the 'user' field?
⚠ Common exam trap
Candidates often treat the system and user fields as interchangeable, failing to recognize that the model processes them with different levels of priority and foundational authority.
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
✓
Use the system field for instructions that should remain constant throughout the entire conversation.
The 'system' field is architecturally designed for global, persistent instructions that define the model's behavior, constraints, and identity throughout the session. The 'user' field is for specific, task-based requests. Mixing these up leads to poor instruction adherence, as the model differentiates between 'foundational rules' and 'conversational requests' based on these roles, ensuring a more robust and predictable experience.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Always put everything in the user field to keep the API call simple.
Why it's wrong here
While simple, putting everything in the user field is bad practice. The model treats system prompts with higher priority and as immutable, whereas user messages are treated as conversational data. This can make the model more susceptible to prompt injections and lead to inconsistent persona and instruction adherence.
- ✓
Use the system field for instructions that should remain constant throughout the entire conversation.
Why this is correct
The system prompt is the foundation of the model's behavior. By keeping constant instructions in the system field, you ensure that the model remains aligned with its core directives regardless of how the conversation progresses, providing a stable, reliable, and secure experience for the end user.
- ✗
Use the system field only for the first message, then switch to user.
Why it's wrong here
The system prompt is not a message in the sequence; it is a parameter of the API call that persists. You cannot 'switch' to user; they coexist. The system prompt should contain all high-level directives that apply globally, and should not be replaced or abandoned as the conversation continues.
- ✗
Use the system field to store user-specific information.
Why it's wrong here
The system prompt should contain general instructions, not user-specific data. Storing user data in the system prompt would mean you need to change the system prompt for every user, which is inefficient and does not leverage the prompt's purpose of defining global assistant behavior and safety constraints.
About these practice questions
One of 257 original CCDV-F practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.