PNB LBO common mistakes
PNB LBO · Understand the traps and how to avoid them.
Spending equal time on every General Awareness question instead of answering banking/economy items quickly and leaving obscure static-GK items for last, causing the section to overrun and eat into Quantitative Aptitude time.
Candidates treat GA as a knowledge test rather than a speed test and second-guess answers on static GK (dates, capitals, awards) they either know instantly or not at all; the section has a large question count relative to the time typically allotted, so hesitation compounds.
What to do instead
Do two passes: first pass answer only banking/economy/financial-awareness items you know within about 10 seconds each; second pass return to static GK and mark any item you cannot resolve in 15 seconds. Practise with a 15-minute timer for a full GA set so the pacing becomes automatic.
Reading the entire English Language passage in detail before looking at the questions, then re-reading it for every question.
School habit of 'read once, understand fully' carries over; candidates fear missing context, but on a timed section the passage is read two or three times in effect, and inference/vocabulary questions rarely need the whole text.
What to do instead
Skim the passage in 60-90 seconds for structure (topic, tone, paragraph purpose), then answer questions by locating the relevant sentence. For vocabulary-in-context questions, read the surrounding two lines only. Target roughly 45-60 seconds per question and practise with a stopwatch per passage.
Solving Quantitative Aptitude questions with full written calculation instead of using approximation, percentage-to-fraction conversion, or elimination from the options.
Candidates prepare by solving textbook problems completely on paper, so the exam becomes a calculation endurance test; they never build a repertoire of shortcuts or estimate-first habits, and data-interpretation sets with large numbers become time sinks.
What to do instead
Drill a fixed shortcut set: fraction-percentage equivalents (1/8 = 12.5%, 1/16 = 6.25%), squares to 30, and the option-elimination habit of estimating the answer's magnitude before computing. For DI, read the question first, then extract only the two or three figures needed.
Attempting puzzles and seating-arrangement sets in the order they appear, sinking 8-10 minutes into one unsolvable arrangement while easy inequality and direction-sense questions remain untouched.
Puzzles look solvable 'with one more clue', and candidates lack a rule for abandoning a set; the reasoning section mixes high-yield quick items with low-yield time traps, and without a triage rule the traps win.
What to do instead
Set a hard cap of 4-5 minutes per puzzle. If two clues still conflict or the arrangement has not taken shape, mark it and move on. First sweep all single-line items (inequalities, syllogisms, blood relations, direction sense, alphanumeric series), then return to puzzles with remaining time.
Guessing randomly on Computer Aptitude items and skipping the section entirely because it 'is not real reasoning'.
Many candidates come from a banking-exam background where computer knowledge is a small add-on, so they under-prepare; but in this exam computer aptitude is fused with reasoning, and questions on number systems, logic gates, binary/hex conversion, and basic hardware/software terms are highly predictable and quick to answer.
What to do instead
Build a one-page revision sheet covering binary/decimal/hex conversion, logic gates (AND, OR, NOT, XOR, NAND truth tables), basic shortcuts (Ctrl+C, Ctrl+V, Alt+Tab, F5), memory units, and common networking terms. Practise 20 conversion and gate questions daily until each takes under 30 seconds.
Leaving General Awareness preparation to the final week and relying only on last-minute current-affairs compilations.
GA feels low-effort because it is 'just reading', so it gets deferred; but the section rewards steady accumulation of banking awareness (RBI functions, monetary policy tools, types of accounts, NBFCs, payment systems such as UPI and NEFT/RTGS) that cannot be crammed reliably.
What to do instead
Schedule 20-25 minutes daily from day one: one page of banking/economy concepts plus a monthly current-affairs digest. Maintain a single running notes file organised by theme (RBI, banking terms, schemes, appointments) and revise it weekly rather than rereading fresh material.
Treating English Language as pure grammar and skipping para-jumbles, cloze tests, and error-spotting practice because 'reading feels enough'.
Fluent readers assume comprehension ability transfers to exam formats, but para-jumbles and cloze tests reward structural cues (connectors, pronoun reference, chronology) that must be practised explicitly; without practice, candidates rely on gut feel and lose accuracy on exactly these high-frequency types.
What to do instead
Practise each question type in isolation: for para-jumbles, identify the opening sentence (no pronoun or connector dependency) and mandatory pairs; for cloze, predict the word before looking at options. Do 10 para-jumbles and 2 cloze passages per week and review every wrong answer for the cue you missed.
Ignoring the sectional time structure and attempting all four sections in a single continuous block without planned cut-offs.
Candidates simulate full papers only occasionally and never rehearse section switches; in the real exam the transition between a calculation-heavy section and a reading-heavy one causes a momentum drop, and unplanned overruns in one section cascade into the next.
What to do instead
Run at least four full-length mocks under real sectional timing before the exam. After each, record time spent per section against the plan and adjust. Rehearse a 30-second reset ritual at each section boundary: stop, note the clock, and start the next section with its easiest question type.
Marking answers on the sheet only at the end of each section or at the very end of the exam.
Candidates who solve on the question paper and plan to transfer later run out of time or misalign the numbering; the risk is highest in Quantitative Aptitude and Reasoning where rough work covers the page and answer keys are easy to shift by one.
What to do instead
Transfer each answer immediately after solving it, and verify the question number against the sheet every ten questions. In mocks, practise the same rhythm so the extra seconds per question are already priced into your timing.
Reviewing mock tests by reading the solutions and nodding along, without re-solving the missed questions from scratch or logging the error type.
Recognition feels like mastery; reading a solution creates familiarity that does not survive exam pressure, and without classifying errors (concept gap, calculation slip, misread question, time pressure) candidates repeat the same pattern.
What to do instead
Keep an error log with four columns: question, error type, correct method in one line, and a re-test date. Re-solve every wrong question cold within 48 hours and again after a week. Track the error-type counts weekly; if 'misread question' dominates, add an underlining habit when reading stems.