Computer Literacy and Banking Software
Questions here test practical familiarity with the tools a cash officer uses daily. Know spreadsheet fundamentals: cell references, absolute versus relative references, common functions such as SUM, AVERAGE, IF, VLOOKUP and COUNT, and how sorting and filtering differ. Know word-processing basics: styles, track changes, mail merge and PDF export. Understand email etiquette, attachments, and the risks of phishing and social engineering.
For banking software, understand core banking systems, teller terminals, transaction posting, reversal and authorisation workflows, and the audit trail that every system generates. Know why a transaction must be posted once and reversed, never deleted, and why maker-checker approval exists in system design.
Traps include confusing absolute and relative references, and questions that treat deleting a wrong entry as acceptable practice. In banking systems, records are corrected by reversal, preserving the audit trail.
Rule of thumb: in a spreadsheet, a dollar sign locks a reference; in a banking system, nothing is deleted, only reversed.
Worked example: A formula in cell B2 reads =A2*$C$1. Copied to B3, it becomes =A3*$C$1, because the relative reference shifts while the absolute reference stays locked.
Analytical Reasoning and Problem Solving
This domain tests structured thinking under time pressure. Expect series completion, analogies, coding-decoding, blood relations, direction sense, seating arrangement, syllogisms and logical deduction. The skills that matter are pattern recognition, careful translation of words into a diagram, and disciplined elimination of options.
For seating and arrangement puzzles, draw the arrangement and fix one anchor before placing others. For direction questions, sketch the path and remember that a left turn after facing south points east. For syllogisms, test the conclusion against a Venn diagram rather than intuition; a conclusion is valid only if it must be true in every possible diagram. For coding-decoding, check letter positions and shifts before assuming a word-level rule.
Traps include conclusions that are merely possible rather than certain, and questions with an extra condition that invalidates an earlier comfortable assumption. Re-read the constraints after forming a tentative answer.
Rule of thumb: if a conclusion can be false in even one valid arrangement, it is not a valid deduction.
Worked example: All clerks are officers. Some officers are auditors. Does it follow that some clerks are auditors? No. The auditors who are officers need not include any clerk, so the conclusion is only possible, not certain.