CAT 2026 QA Sectional Live | Question Selection, Solving & the 40-Minute Strategy, Decoded

In CAT QA, scoring well depends more on which questions you choose to attempt than on how fast you solve them. Unlike LRDI, don't burn the first few minutes reading everything — read one question at a time, decide inside 15–20 seconds whether it's yours to take right now, and move on the instant it isn't. Most high scorers build their score in a fast first round of 12–13 "must-solve" questions, then come back for a handful of trickier ones with whatever time is left.

That framework was tested live — a complete CAT-level QA sectional, solved on camera, in real time, under the 40-minute clock. Not a pre-recorded walkthrough with the hard parts edited out. The actual scanning, the actual mid-solve u-turns, the actual moment of abandoning a question because it wasn't opening up.

Key Takeaways

1. QA (Quantitative Ability) rewards question selection over raw solving speed — 22 questions, 22 different concepts, no two alike.
2. Unlike LRDI, don't read the whole section upfront — QA is decide-as-you-go: read a question, judge it in seconds, act.
3. Cap most questions at 2–2.5 minutes; treat 3 minutes as a hard ceiling.
4. Build a first round of 12–13 "must-solve" questions you can recognise and execute fast — target 9–10 correct out of those.
5. Save the lengthy, calculative, or unfamiliar-looking ones for a second round — attempt 2–3 of them, with at most one wrong.
6. Most QA marks lost aren't concept failures — they're time-management failures: getting attached to one question and starving two others that were actually solvable.

A Typical QA Section, Question by Question

CAT QA doesn't repeat five set-types the way LRDI does — it's roughly 22 standalone questions spanning algebra, arithmetic, geometry, number systems, and modern math, each testing something different. That spread is exactly why blanket strategies ("always attempt geometry first") don't work. What matters is a fast, honest read on each individual question as it comes:

The point isn't to memorise these categories — it's to train the 15-second judgment call itself. That call only sharpens with volume: the more full sectionals you attempt under a clock, the faster and more accurate this read becomes.

Why Question Selection Matters More Than Solving Speed

The single costliest habit in QA isn't a silly mistake on a solved question — it's spending real time on a question that was never going to open up, at the expense of one or two that would have.

Every minute sunk into a question you eventually abandon is a minute not spent on a question you could have closed out. And closing out even one or two extra questions in that recovered time is often worth several percentile points. That trade is invisible in the moment — it only shows up when you compare your actual score to what was sitting right there, solvable, while you were stuck elsewhere.

This is also where QA strategy diverges sharply from LRDI. In LRDI, spending 3–5 minutes scanning every set before solving anything is the right call — a set only reveals itself over its full length. In QA, the same upfront-scanning habit is a trap: you'd be spending 3–5 minutes reading when you could already have solved one or two of those questions outright. QA rewards deciding in the moment, question by question, not scanning the whole section first.

How Do You Select QA Questions? A Framework

Read. Decide fast. Timebox. Bank or bail. Run this loop on every question, in order, without pausing to scan ahead:

1. Read one question at a time — no upfront scanning of the whole section. Give yourself roughly 15–20 seconds to judge whether the approach is clear.
2. If it clicks, solve it — with a real time cap. Most questions should take 2 to 2.5 minutes; treat 3 minutes as the outer limit for anything in the first round.
3. If it doesn't click in those first seconds, skip immediately and move on. Don't reread it hoping it'll make more sense — that's dead time.
4. Build your first round out of the questions that click fast. Aim for 12–13 of these across the section, solved at high accuracy.
5. Return in a second round for the longer or less-obvious ones, now with a clearer sense of how much time is actually left. Attempt only as many as the clock allows.

Inside any single question, the same stubbornness rule from LRDI applies: if you're a couple of minutes in and it's not resolving, that's the signal to stop — not push harder.

What Actually Happened in 40 Minutes

Here's the honest part, because a strategy is only useful if you also see it fail a little.

Solving live — narrating every decision, re-explaining a step that was solved mentally, switching between the question and the working area — takes noticeably longer than solving silently. Several questions that should have been comfortable first-round solves ended up eating far more time than they should have simply because of the added friction of explaining while solving, and one question got abandoned mid-way after getting stuck on a step that, in hindsight, had an easier route through a small set of factor combinations.

The takeaway isn't that explaining costs time, though it does. It's that the real cost in QA almost never comes from the questions you get wrong — it comes from the time misallocated to questions that were never going to pay off, time that could have gone to ones that would have.

What Mistakes Cost the Most Marks in QA?

A few failure patterns show up again and again in live solving, regardless of the specific questions involved:

1. Not recognising a shortcut that saves real time. Quadratics that factorise by inspection, squares of numbers ending in 5, expressions that reduce cleanly to a power of 10 — these aren't optional tricks, they're basics that directly control how many questions you get through.
2. Getting stuck and not letting go. A question that "should" work with one more try is exactly the kind that eats a minute and a half for zero return. The instinct to keep pushing is precisely what a hard time cap exists to override.
3. Spending recovered time on the wrong thing. Questions you abandon should free up time for other solvable questions — not get revisited immediately out of frustration. Time saved from a skip only helps if it's redirected, not re-spent on the same question.

None of these are pure concept failures. They're execution and time-allocation failures — the kind that only show up under a real clock, which is why full sectional attempts under time pressure matter more than untimed question-by-question practice.

What This Means for Your Prep

Don't treat every question as worth solving by default. A 15–20 second read-and-decide habit protects you from questions that look approachable and turn into 4-minute sinkholes.

Know your weak topics before the exam, not during it. After enough full sectionals, a clear pattern emerges — the topic types that consistently take too long or don't resolve for you. Once you know them, skip them on sight in the actual exam rather than re-discovering the struggle live.

Drill the basic shortcuts until they're automatic. Instant factorisation, quick squaring, converting expressions to powers of 10 — these aren't separate from strategy, they're what makes the 2–2.5 minute cap realistic in the first place.

Practice with a shrinking timer. Start with a 3-minute cap per question in regular practice, and reduce it by about 15 seconds every few mocks until you're comfortably working within roughly 1 minute 45 seconds. Consistency across sessions is what makes the gain stick — a single fast session followed by a week off doesn't move the needle.

Log every mock, not just the score. After each attempt, go question by question: for the ones you got right, compare your method against the solution to see if a faster route existed; for the ones wrong or unattempted, pin down exactly what went wrong — a concept gap, a misread, or simply running out of time. Revisit that log regularly.

We've broken the full question-selection and time-boxing framework down further, with complete QA preparation, here: CAT Quant — CAThlete 2026 →

Key Numbers to Remember

Frequently Asked Questions

How long is the CAT QA section? CAT QA runs for 40 minutes and typically contains around 22 standalone questions across algebra, arithmetic, geometry, number systems, and modern math.

Should I read the whole QA section before solving, like in LRDI? No. QA questions are independent of each other, so scanning the whole section upfront wastes time you could spend solving. Read one question at a time, decide within 15–20 seconds if it's approachable, and act immediately.

How many QA questions should I attempt in the actual exam? Build a first round of around 12–13 questions you can recognise and solve quickly, aiming for high accuracy there. Use whatever time remains for a smaller second round of 2–3 longer or trickier questions.

What should I do if I get stuck on a question mid-exam? Cap it at 2 to 2.5 minutes — 3 at the very outside. If it isn't resolving, skip it and move to the next question. The time you free up is only useful if you spend it on something solvable, not by returning to the same question out of stubbornness.

Should I attempt every topic in QA? No. Full sectional practice will reveal your consistently weak topic types. Once you know them, skip those on sight in the real exam rather than spending time discovering the struggle live.

Why do QA scores not improve even with regular practice? Most QA plateaus come from time misallocation, not knowledge gaps — time lost to a question that was never opening up, at the cost of ones that would have. Practising full sectionals under a real clock (not just isolated questions) surfaces this pattern in a way question-by-question practice can't.

GRADSKOOL CAT QA — CAThlete 2026 Complete QA preparation, including the question-selection and time-boxing framework used in this session. Explore the Course →

Written by

Kavya K

GRADSKOOL