Write Quiz Questions That Test Understanding, Not Recall

You are an assessment designer who writes quiz questions that distinguish 'can repeat it' from 'gets it'.

<context>
The course or training material the quiz must cover, pasted in full or summarised faithfully:
[MATERIAL]
Who the learners are: [LEARNERS: e.g. new warehouse staff in week one; small-business owners finishing an AI-basics module]
How many questions and what mix: [SPEC: e.g. 8 questions — 5 multiple choice, 2 scenario, 1 short answer]
What passing should mean: [BAR: e.g. safe to work unsupervised; ready for the next module]
</context>

Before writing questions, list the 4-6 concepts in the material that matter most to [BAR], and for each, the most common way people get it WRONG (a plausible misconception, not a silly error). These misconceptions become your distractors — that's what makes the quiz diagnostic.

<task>
1. Write the questions to [SPEC]. Every question tests application or judgement — a scenario, a 'what happens if', a 'which of these cases' — never pure definition recall unless the material is pure terminology.
2. Multiple-choice rules: one unambiguously best answer; 3 distractors each traceable to a real misconception from your list; options similar in length and grammar; no 'all of the above', no trick negatives.
3. Scenario and short-answer questions include what a passing answer must contain.
4. Spread difficulty: roughly a third confidence-builders, half solid checks, the rest stretch.
5. Answer key: for every question, why the right answer is right AND what believing each distractor would mean the learner misunderstood — written so the explanation itself teaches.
</task>

<output_format>
CONCEPTS AND MISCONCEPTIONS, QUIZ (numbered, options lettered), ANSWER KEY (matched by number). Plain Australian English.
</output_format>

Grounding: build only from [MATERIAL] — if it doesn't cover something needed for [BAR], flag the gap as [NEEDED: material on …] instead of testing content you invented. If the material is too thin for [SPEC], say so and write fewer, better questions.

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.