CAT Practice Questions: 4 Signs You're Rushing Them

Strategy

There's a myth in CAT prep that finishing a set of CAT practice questions early is proof you've mastered them. A student closes fifteen Time, Speed and Distance questions in eleven minutes flat, fastest in her mock group. Then the answer key lands: six wrong. Not the concept. She never once checked the units before locking an answer.

Speed feels like strength because it looks like fluency from the outside, and both produce the same stopwatch reading. Only one holds up against an answer key. What follows finds the topics where speed and accuracy point in opposite directions, names the one rushed step causing the damage, and fixes it without losing the speed you already built.

What a Fast But Inaccurate CAT Topic Actually Looks Like

Every topic sits somewhere between two numbers: how long you take, and how often you're right. This piece stays inside exactly one pattern: fast and wrong. Slow and wrong is a different problem with a different fix, and fast and right needs no fixing at all. Not every one of your CAT practice questions deserves equal attention, and this is the pattern to prioritise first.

A slow topic feels hard while you're solving it, so you already suspect something's off before the answer key confirms it. A speed trap topic feels solved instead, and the problem only shows up in marks you don't check until well after the mock is over. That gap between how a topic feels and how it actually scores is the whole reason this pattern hides for so long.

• Fast and wrong: the speed trap this piece is about.
• Slow and wrong: a genuine knowledge gap, a different audit entirely.
• Fast and right: no action needed, protect the pace you've built.
• Slow and right: accurate but inefficient, its own separate fix.
• The audit below only ever targets the first quadrant.

The Two Numbers That Reveal a Speed Trap

Two numbers are enough to flag a topic, both straight off a mock. Neither alone tells you much; it's the combination that matters. A speed trap shows up when the first number sits below your overall average and the second sits meaningfully below it: genuinely fast and genuinely wrong, on the same topic, at once.

• Average time per question, for that specific topic, not the section average.
• Accuracy for that same topic: correct answers divided by attempted questions.

Reading Your Mock Analysis Log

Most students already have this data, spread across a mock report and a practice log. The audit needs it pulled into one place, topic by topic, instead of relying on memory, which is exactly what fails on a topic that felt fine while you were solving it.

Why Your Fastest Topics Quietly Turn Into Your Weakest

A topic becomes fast for a reason, rarely mastery in the way you'd assume. Repetition builds pattern recognition long before it builds full correctness. Your hand starts writing a familiar formula before your eyes finish reading the numbers, right up to the moment a question quietly changes one condition and your hand keeps writing the old formula anyway.

Autopilot Pattern Matching

Autopilot is pattern recognition once it stops asking questions. You match the type, retrieve the method, execute it, and move on, without checking whether this question actually fits the pattern applied. Most speed trap errors aren't calculation mistakes. They're pattern mismatches: the right method, applied quickly, to a question that quietly broke one assumption.

• A percentage question asking for the original value, not the increase, while your hand writes the increase formula.
• A quadratic whose second root fails the original constraint, kept anyway by a fast solver.
• A DILR clue that reverses a direction stated earlier, missed because the grid was already half filled.
• A VARC choice that repeats the passage's words without repeating its actual claim.
• An arrangement clue applied to the wrong seat or slot once fatigue sets in.

Confidence That Outpaces Verification

The second half of the mechanism is emotional, not mechanical. A topic that has gone well earns your trust, and trust removes the impulse to double check. You verify the topics that scare you, not the ones you've already decided you're good at, which is backwards: a fast topic needs a checkpoint more, because speed is what hides the error in real time.

The 4-Step Speed Trap Audit

Fixing a speed trap topic doesn't mean slowing down everywhere and hoping accuracy improves on its own, because the rushed step was never scattered across the topic, it was hiding in one specific place. The 4-Step Speed Trap Audit finds that place first, then fixes only that, so your pace barely moves while accuracy actually does.

Step 1: Flag the Topic Inside Your CAT Practice Questions Log

Open your last two or three mocks and your recent practice history side by side. For every topic attempted at least eight to ten times, note two numbers: average time per question, and accuracy. Most students skip this step, not because it's hard, but because it feels slower than moving to the next mock. It takes fifteen minutes and it's the one part of this audit that can't be shortcut.

Topic	Avg. Time per Question	Accuracy	Verdict
Time, Speed and Distance	58 sec	58%	Speed trap
Percentages	62 sec	91%	Genuinely strong
Number System	112 sec	54%	Slow and wrong, different fix
Venn Diagrams	65 sec	60%	Speed trap

Watch for a topic whose time sits near your fastest topics, while its accuracy sits near your weakest ones. That combination, not either number on its own, is what marks a speed trap. A topic that's merely fast and merely average on accuracy isn't the target here.

Step 2: Isolate the Exact Step You're Rushing

Once flagged, stop practicing the topic at speed. Pull five wrong questions and rework each slowly, writing out every step instead of doing two in your head. Somewhere in that rework you'll hit the line where your fast attempt diverged from the correct one, almost always the same line, question after question.

The Rushed Step in Quant

In Quant, the rushed step is usually a two-second check skipped because the formula feels automatic: not converting units before plugging into a speed formula, not checking whether a quadratic's second root satisfies the original constraints, not re-reading whether a percentage question wants the increase or the new value. None are knowledge gaps, just a fast hand outrunning a careful eye. If Time, Speed and Distance practice questions are a speed trap for you, rework ten watching for the unit-conversion step alone.

The Rushed Step in DILR and VARC

DILR speed traps hide in the setup, not the solving: you draw the grid fast, lock an interpretation, and never check it against the next clue. A wrong Venn Diagram question is rarely a Venn Diagram problem at its core; it's a five-second re-read that got skipped. In VARC, it's usually eliminating a choice on tone alone. Rework a few wrong Reading Comprehension questions and the same shortcut tends to repeat.

Step 3: Install a Forced Verification Checkpoint

A checkpoint only works if it targets the specific rushed step you found. A vague reminder to slow down gets ignored under pressure for the same reason the original step did. A specific, five-second action, tied to the exact place the error happens, survives real mock pressure.

• Quant: circle the unit or the exact ask before writing the first line of working.
• DILR: re-read the constraint list once the grid is half filled, before locking any cell in.
• VARC: underline the exact sentence a choice claims to support, before selecting it.
• Across all three: say the answer's rough magnitude out loud before marking it.

Step 4: Run Deliberate Slowdown Drills

The checkpoint needs to become automatic before it can survive a timed set. For the next few sessions, give yourself twenty to thirty percent more time per question than usual, and spend the extra seconds on the checkpoint, not on the parts you already handle well.

• Pick eight to ten fresh questions from the flagged topic, not the ones already reworked.
• Add the checkpoint deliberately, even when it feels slow at first.
• Track accuracy for that set specifically, separate from your overall practice accuracy.
• Repeat for two to three sessions before letting the topic back into a full mock.
• Keep the log running so the next flagged topic gets caught just as fast.

When to Stop Slowing Down and Speed Back Up

Slowdown drills are a temporary correction, not a new pace. Staying deliberately slow after the checkpoint becomes automatic costs you time for no accuracy gain. The signal to speed back up is accuracy, measured the same way you measured it when you first flagged the topic.

• Three consecutive sets at 90 percent or higher, not one good set and a lucky guess.
• The checkpoint feels quick, not effortful, the way an old habit feels next to a new one.
• Accuracy holds even when you deliberately reintroduce time pressure in the final set.

Build the Speed Trap Audit into your CAT preparation weekly plan the same way you'd schedule any revision block, deliberately, not as an afterthought once a mock forces the issue again. A fixed topic can quietly relapse if never revisited, especially in the final weeks.