Welcome back. You have already built two foundations for mock improvement: first, separating what went wrong (concept, interpretation, calculation, carelessness, or decision); then scheduling targeted reattempts so the repair persists. This lesson focuses on the decision error that can silently cost several marks even when the underlying concepts are known: spending too long on the wrong question, guessing an MCQ without enough evidence, or leaving a low-risk question untouched.
The aim is not to “attempt more questions.” It is to allocate your 180 minutes to the questions with the best combination of confidence, expected marks, and time cost. By the end, you should be able to label a question attempt now, defer, or skip, and explain the choice rather than making it emotionally in the moment.
The exam decision is an allocation problem
Every question competes for a limited resource: your attention and time. A difficult 2-mark MCQ is not automatically worth four minutes merely because it carries two marks. If that same four minutes could secure a known 1-mark question and allow you to check a NAT calculation, the expensive MCQ may be the worse choice.
A useful mental model is:
Attempt now when you have a credible solution path and a favourable return for the time.
Defer when you know the method but need more time or calmer attention.
Skip when you have no executable path, the MCQ risk is unjustified, or the likely time cost is too high.
“Skip” does not mean “I am weak at this subject.” It means this question is currently a poor investment. That distinction matters especially in COA, CN, TOC, and Compiler Design, where a familiar-looking question can consume time before you discover that you do not actually have a method.
The first 30–45 seconds of reading should therefore answer three things:
- What is being asked? Identify the output: a value, complexity class, valid option set, schedule property, cache field, subnet, and so on.
- Can I state a first executable step? “Use Dijkstra” is not a first step; “check whether all edge weights are non-negative, then initialize distances” is.
- What will this probably cost? A direct fact recall may take under a minute. A recurrence expansion, B+ tree cost calculation, or pipeline trace may take several minutes.
If you cannot name the first step after properly reading the question, your confidence is low even if the topic name feels familiar.
Know the scoring rules before using strategy
The official GATE pattern makes the question type central to your decision. MCQs have negative marking; MSQs and NATs do not. The final 2027 information bulletin should always be your authority, but this official pattern gives the relevant structure to practice now.
Read the official GATE page to anchor your decision rules in the actual marking scheme rather than in general test-taking advice.
In the “QUESTION PAPER PATTERN” table, first locate the rows for “Type of Questions,” “Marking Scheme,” and “Negative Marking.” Then read the official penalty rules. Focus on the different consequences of an incorrect MCQ versus an incorrect MSQ or NAT response.

The practical implications are:
| Question type | If correct | If wrong | Decision implication |
|---|---|---|---|
| 1-mark MCQ | Do not make unsupported guesses | ||
| 2-mark MCQ | Require a credible method, elimination, or strong verification | ||
| MSQ | Full marks only | No penalty, but no partial credit; every selected and unselected option matters | |
| NAT | Full marks | No penalty, but a random numerical entry is rarely useful; time still matters |
The absence of negative marking does not mean that an MSQ or NAT should be solved immediately. A seven-minute NAT with no clear method can still crowd out easier marks. It means only that a wrong final entry does not reduce your raw score.
MCQs: confidence must exceed the penalty risk
For an MCQ worth marks, let be your real probability of getting it right. This probability must include the whole process: identifying the correct concept, executing the calculation, interpreting the options, and selecting the intended answer.
Its expected score is:
The expected score is positive only when:
For a usual four-option MCQ, a completely random guess has , hence an expected score of zero. It also adds variance: in a particular paper, it may become a deduction. For someone trying to move from below 40 marks to a top-IIT competitive range, “zero on average” is not a good reason to introduce avoidable negative marks.
What elimination really gives you
If you can genuinely rule out one option and the remaining three seem equally plausible, then is approximately . The expected score becomes positive:
For a 1-mark MCQ, that is roughly marks; for a 2-mark MCQ, roughly marks. Eliminating two options gives a much stronger position, with near .
But this is only a risk calculation, not an instruction to attempt immediately. You must still ask: How much time did the elimination take, and what known questions remain?
Consider two 2-mark questions in the middle of a mock:
- Question A: A COA MCQ. You eliminate one option, but your cache-field calculation remains unclear. You estimate four more minutes to finish.
- Question B: A DBMS NAT. You know you need attribute closure, can write the first step, and expect two minutes of work.
Even though Question A now has a slightly positive expected value from elimination, Question B is the better immediate investment. Mark A for review and secure B.
A safer MCQ rule
Use this hierarchy:
| Your state after the initial read | Decision |
|---|---|
| Exact method is clear, first step is ready, and the work is short | Attempt now |
| Method is clear but calculation, tracing, or verification will take time | Defer |
| You can eliminate options but have no full method | Usually defer; decide later based on time remaining |
| No method and no justified elimination | Skip |
| You are choosing an option because it “looks familiar” | Skip |
The important word is justified. For example, in a CN MCQ, rejecting an option because its subnet mask cannot support the stated host count is justified. Rejecting an option because “it seems too large” is not.
MSQs and NATs: no penalty does not remove opportunity cost
MSQs and NATs change the risk of being wrong, but they do not eliminate the cost of spending time.
MSQ: treat “all correct options” as the target
An MSQ gives no partial marks. If three options are correct and you select only two, your score is still zero. Therefore, do not use the familiar MCQ habit of finding one attractive answer and stopping.
For an MSQ, use this mini-check:
- Test each option against the rule or definition.
- Ask whether the question has a hidden condition such as “always,” “only if,” “minimum,” or “all possible.”
- Check both sides of the choice: why selected options are valid and why unselected options are invalid.
If you are unsure about one option during the first pass, defer it. In the final minutes, an uncertain MSQ cannot produce negative marks, but it should never displace checking a likely-correct MCQ or a nearly finished calculation.
NAT: preserve it for a method-based attempt
NATs are often excellent second-pass targets because there is no option distraction and no negative marking. But “no penalty” is not the same as “random input is valuable.” The numerical range may be broad, making a blind entry almost certain to earn zero.
Attempt a NAT now when:
- you know the governing formula or procedure;
- you can estimate the answer’s sign, scale, or allowable range;
- the computation is short enough for the current pass.
Defer it when the method is known but long. Skip active work on it when the method is absent. If time remains at the end, a reasoned estimate is harmless; before that, do not sacrifice high-confidence marks for it.
For example, a NAT asking for effective memory access time is a good attempt if you can immediately write the weighted-average structure. If you cannot recall whether a TLB lookup overlaps memory access in the stated model, defer it rather than inventing assumptions under pressure.
A three-part decision routine for the live paper
A multi-pass paper strategy prevents one stubborn question from controlling the entire exam. Watch this brief explanation for the core logic: sweep the paper, secure straightforward questions, then return to marked questions that need calculation.
How to Attempt the Question Paper? | The Perfect Strategy
Watch “How to Attempt the Question Paper? | The Perfect Strategy” by Torq4712 for a practical explanation of separating quick, high-confidence questions from known-but-slower questions.
In the explanation of the first phase, watch the rapid sweep. Notice that the objective is not merely to read every question: it is to solve genuinely easy items while gaining visibility over the whole paper. Then watch the deferred set, focusing on why questions with a known method but nontrivial calculation belong in a later pass.
Do not copy someone else’s timing exactly. Your mock data should eventually determine your timings. As a starting template for a 180-minute GATE paper, use the following structure.
| Phase | Approximate time | Primary action |
|---|---|---|
| Pass 1: secure marks | 35–45 minutes | Scan the paper; attempt only high-confidence, short questions; mark deferred items |
| Pass 2: convert known methods | 75–85 minutes | Solve questions where the method is known but calculation or tracing is needed |
| Pass 3: selective returns | 30–40 minutes | Choose the best remaining questions based on likely marks, risk, and time |
| Final check | 15–20 minutes | Review marked answers, calculations, units, option selection, and question interpretation |
This structure has a strategic purpose: it protects you from an early six-minute trap.
A strong operational rule is to make a small label beside each question number on the rough sheet:
| Label | Meaning | Example |
|---|---|---|
| A | Attempt now | Direct GA ratio, familiar linked-list trace, direct Boolean simplification |
| D | Defer with a reason | “D-C”: method known, lengthy calculation; “D-E”: partial MCQ elimination |
| S | Stop investing time | No method, no useful elimination, or an unfamiliar multi-topic construction |
The reason beside D is important. “D-C” tells you the issue is calculation. “D-M” might mean a method needs recalling. When you return, you will not spend another minute rereading the question just to remember why you left it.
Use a first-step test, not a feeling of familiarity
The most dangerous internal sentence during GATE is: “I have studied this; I should be able to do it.” That feeling can lead to a five-minute struggle with no actual progress.
Replace it with a first-step test.
Example 1: COA cache mapping MCQ
A question gives cache size, block size, associativity, and an address.
- Attempt now if you can immediately determine the number of sets and write how offset, index, and tag bits are obtained.
- Defer if you know the formulas but need careful arithmetic and the first pass is still underway.
- Skip if you cannot distinguish cache lines from sets or do not know what changes under set associativity.
This connects directly to your earlier cache-mapping review unit: “I have seen cache questions” is not enough. You need a retrievable procedure.
Example 2: DBMS functional-dependency MCQ
A question asks whether is a candidate key.
- Attempt now if you can begin and know that you must also test minimality.
- Defer if the closure is likely long but you know exactly what to do.
- Skip if you cannot recall how closure proceeds or confuse superkeys with candidate keys.
Example 3: CN fragmentation NAT
- Attempt now if you can identify the payload limit from the MTU, account for header size, and remember fragment offsets are measured in 8-byte units.
- Defer if the setup is clear but the arithmetic has multiple fragments.
- Skip active work for now if you cannot identify the relevant fields or are guessing the offset rule.
The pattern is consistent across subjects: confidence is demonstrated by an executable next action, not by recognizing vocabulary.
Add a stop-loss rule for time-consuming questions
Many decision errors are not caused by an incorrect first choice. They happen because the learner fails to stop after deferring should have happened.
Before a mock, set provisional limits such as:
- If a 1-mark question has not produced a clear method after about a minute of real work, mark it for review.
- If a 2-mark question has not progressed beyond setup after roughly two minutes, reassess: do you have a real path, or only hope?
- If a calculation becomes messy, pause and ask whether you can state the next operation and a final sanity check.
These are not rigid universal limits. A direct 2-mark graph question can be quicker than a tricky 1-mark C output question. The point is to interrupt unproductive persistence.
A useful distinction is:
- Productive difficulty: each line of work narrows the solution; you can explain why the next step follows.
- Unproductive struggle: you reread, try unrelated formulas, restart repeatedly, or choose options by intuition.
Productive difficulty may deserve a defer-and-return. Unproductive struggle deserves a skip.
Turn this into measurable mock behavior
For your next three timed mocks, do not judge the strategy only by the final score. Track these four numbers:
| Measure | What it reveals |
|---|---|
| Accuracy on questions attempted in Pass 1 | Whether “attempt now” truly means high confidence |
| Accuracy on deferred questions | Whether you are correctly identifying known-but-slower problems |
| Minutes spent on skipped or ultimately wrong questions | Your time-leakage problem |
| Negative marks from MCQs | Whether elimination and confidence rules are working |
After each mock, mark a decision error precisely:
- Should have deferred: knew the method, but spent too long during the first pass.
- Should have skipped: no method or valid elimination, yet attempted an MCQ.
- Should have attempted: had a method and low risk, but left marks unused.
- Returned at the wrong time: chose a low-value hard question while easier deferred questions remained.
This record fits directly into the error-log and spaced-reattempt system from the previous lesson. You are not only repairing subject concepts; you are training a repeatable execution policy.
Key takeaways
Your question-selection rule is not “always attempt” or “never guess.” It is a structured comparison of:
- Confidence: Can you state the exact first step and identify the requested output?
- Time cost: Can you solve it efficiently now, or should it wait for a later pass?
- Marking risk: Is it an MCQ with a penalty, or an MSQ/NAT with no negative marking but still a time cost?
For MCQs, random guessing has zero expected value under the usual four-option, one-third-penalty structure; it is not a sound way to build a reliable score. One eliminated option can make the expected value positive, but it still may not be the best immediate use of time. For MSQs, verify the entire option set; for NATs, use the lack of penalty intelligently without donating excessive time to an unknown method.
In the next lesson, you will apply the same disciplined approach to General Aptitude questions involving percentages, ratios, averages, and mixtures—topics that can become high-confidence Pass 1 marks with the right setup.
Can't find a good explanation? Sign up and we'll make it for you
Sign up