Distractor Patterns & Traps

What you'll learn: the recurring patterns CELPIP uses to write plausible-but-wrong answer choices, so you can eliminate them by pattern instead of by guessing.

Distractors are written on purpose

Wrong answer choices on CELPIP Listening aren't random — they're deliberately constructed to be attractive to a listener who understood the general gist of the recording but missed one specific detail. Recognizing the pattern behind a wrong answer is often faster than trying to recall the exact audio, because these patterns repeat across parts and across test versions.

The four recurring distractor patterns

1. Mentioned-but-rejected

The distractor states something that genuinely was said in the audio — but it was an option that got rejected, replaced, or ruled out, not the final answer. This is the single most common trap across Problem Solving and Discussion, where multiple options get raised before one is settled on.

2. Right category, wrong specific value

The distractor is the correct type of answer (a time, a name, a reason) but the wrong specific instance — often a value mentioned earlier in the recording before a correction. "2:00" when the corrected time was "2:30" is a classic version of this.

3. True statement, wrong question

The distractor is something the speaker did say, and it's accurate — but it doesn't actually answer the specific question being asked. This preys on listeners who recognize a familiar phrase from the audio and select it out of recognition rather than checking it against the actual question.

4. Overgeneralization

The distractor takes a specific, limited statement and stretches it into a broader claim the speaker never actually made — e.g., the speaker says a policy "might" cause delays "in some cases," and the distractor answer states it "will cause delays."

Worked example — elimination reasoning

Audio (paraphrased): "We originally planned to launch the app in March, but after the second round of testing turned up a few bugs, we pushed it to April. It could slip further if the next testing round finds anything major, but the team is fairly confident that won't happen."

Question: "When is the app now expected to launch?"

• (A) March — mentioned-but-rejected: this was the original plan, since replaced.
• (B) April — correct: this is the corrected, current expected date.
• (C) It has already launched — overgeneralization/unsupported: nothing in the audio states this has happened.
• (D) It will definitely slip further — overgeneralization: the audio says it could slip, and follows with the team being "fairly confident that won't happen" — the opposite emphasis.

Notice that (A), (C), and (D) can each be eliminated by naming the pattern, not just by "feeling" they're wrong — which is a faster, more reliable process under time pressure than re-recalling the whole recording.

Distractor-elimination checklist

• Before picking an answer, ask: was this mentioned, then changed or rejected, later in the audio?
• Check whether an answer is the right category but possibly an earlier, uncorrected value.
• Check whether an answer is a true statement from the audio that doesn't actually answer this question.
• Check whether an answer stretches a hedged statement ("might," "some," "could") into an absolute one.

Common mistakes

• Selecting an answer purely because it sounds familiar from the audio, without checking it against the question asked.
• Locking onto the first-mentioned value and not registering a later correction.
• Missing hedging words ("might," "some," "a few") that separate a correct, cautious answer from an overgeneralized distractor.
• Treating all four answer choices as equally worth full re-consideration instead of naming the pattern to eliminate three quickly.

Recap

CELPIP distractors follow four repeatable patterns — mentioned-but-rejected, right-category-wrong-value, true-but-off-question, and overgeneralization. Learning to name which pattern a wrong answer fits, rather than relying purely on memory of the audio, makes elimination faster and more reliable, especially on questions where your notes are incomplete.