CCAR-F objective 4.1 · Domain 4 · 20% of the exam
System Prompts with Explicit Criteria
The recurring failure is a criterion the prompt never defines. Asking an agent to flag anything suspicious leaves it inventing a standard, and a slightly different one each run, so the fix is named categories with a stated rule each and a worked example anchoring the boundary. The other half is knowing when the prompt is the wrong instrument. Requirements phrased with never or without exception are guarantees, and a prompt raises the odds while leaving a tail; appending the text in code removes the model from the requirement. Length is examined too: a rule lost among thirty others is not fixed by adding a thirty-second.
7 questions · answers and explanations shown as you go · free, no sign-up
The rest of domain 4: Prompt Engineering and Structured Output
This domain is 20% of a scored form, about 13 of the 65 questions, spread across 6 objectives. Drill the whole domain or pick another objective below.
One objective is a narrow slice. A full-length timed mock is what tells you whether the whole thing holds together.
Sit a timed mock →