RBSE SS Voc IT and ITeS common mistakes
RBSE SS Voc IT and ITeS · Understand the traps and how to avoid them.
Treating RAM and ROM as interchangeable in questions about which memory loses its contents when power is switched off, or describing secondary storage (hard disk, pen drive) as volatile main memory.
Candidates memorise the words 'primary memory' and 'secondary memory' as labels without attaching the volatile/non-volatile property to each, and textbook diagrams of the memory hierarchy are often recalled as pictures rather than as facts about data retention.
What to do instead
Build a two-column table (volatile / non-volatile) and place RAM, ROM, cache, hard disk, SSD, pen drive and DVD into it from memory, then check. For every hardware question, ask 'what happens on power-off?' before answering. Practise explaining in one sentence why a computer needs both RAM and a hard disk.
Confusing input, output and storage devices, for example classifying a touchscreen only as input, a pen drive as an input device, or a plotter as an input device.
Devices are learned as a list to be recited rather than by the direction in which data flows, and hybrid devices such as touchscreens and modems are taught late or not at all, so the simple one-way model breaks down.
What to do instead
For each device, state the data direction aloud: 'sensor to computer = input', 'computer to paper = output', 'kept for later = storage'. Keep a short list of hybrids (touchscreen, modem, touchpad-with-display) and note that they are both. Sort a mixed list of fifteen devices into three columns under timed conditions.
In spreadsheet questions, writing a formula that hard-codes values instead of using cell references, or copying a formula with relative references and expecting the same cells to be used in every row.
Candidates practise by typing numbers directly (for example =25*4) because it produces the right visible answer, and they have not internalised that a spreadsheet's purpose is recalculation when source data changes. The dollar sign in absolute references is memorised as syntax without understanding what it locks.
What to do instead
Adopt the rule that a formula should contain only references and operators, never typed source numbers. Practise writing =B2*C2 and filling down, then change B2 and confirm the result updates. Test relative versus absolute by copying =A1, =$A$1, =$A1 and =A$1 one column right and one row down, and record which part of the reference changed each time.
Confusing the functions of word-processing features: using Find when Replace is needed, describing Track Changes as a way to compare two documents, or claiming that pressing Enter creates a new page rather than a new paragraph.
The ribbon presents many similar-looking commands side by side, and candidates who have only used a word processor casually map exam vocabulary onto the few buttons they have personally clicked, filling gaps with plausible guesses.
What to do instead
For each feature, write a one-line 'problem it solves' note (Find locates text; Replace locates and substitutes; Page Break forces content to a new page; Section Break allows different page setup). Then perform each operation once in a real document and describe what changed on screen. Answer feature questions by first naming the user's goal, then the command.
Answering internet questions with a vague description of what a browser or search engine does, without distinguishing a browser from a search engine, a URL from an IP address, or the World Wide Web from the internet itself.
Everyday language blurs these terms ('I go on the internet with Google'), and candidates reuse that casual phrasing in an exam that is testing precise technical definitions.
What to do instead
Write four crisp definitions in your own words and one counter-example for each: the internet is the network of networks; the web is a service running on it; a browser is client software that requests and renders pages; a search engine is a website that indexes other pages. Also label the parts of a sample URL (protocol, domain, path) and state what DNS does.
Writing SQL or describing database operations that ignore the role of the primary key, or confusing primary key, foreign key, candidate key and unique key when asked to identify them in a table description.
Keys are taught as definitions to memorise rather than as constraints that enforce behaviour, so candidates cannot decide which column qualifies. They also overlook that a primary key cannot be null and must be unique, which is the discriminating detail in most questions.
What to do instead
For a given table, test each column against three questions: is it unique, is it never null, and does it identify one row? Only then label it. Practise writing CREATE TABLE statements with PRIMARY KEY and FOREIGN KEY clauses so the constraint is expressed in syntax, and explain in one sentence what a foreign key guarantees about referential integrity.
Describing an algorithm in prose without stating the input, the step sequence and the stopping condition, or writing pseudocode whose loop never terminates or whose variables are used before being initialised.
Candidates focus on producing the 'right answer' for one sample input and never learn to specify a general procedure, and they have not traced their own code line by line to see the missing update or exit condition.
What to do instead
Use a fixed three-part template for every algorithm answer: inputs, numbered steps, output. Then dry-run it on paper with a small sample, writing the value of each variable after every step. For any loop, explicitly state what changes each iteration and the condition that ends it. Trace a deliberately broken loop to see the infinite case.
In IT-enabled services questions, describing BPO, KPO, data entry and transcription as the same activity, or failing to match a process (inbound voice, outbound voice, chat, back-office) to the correct service category and its typical performance measures.
The sector vocabulary is new to most candidates and the terms overlap in ordinary speech; without a mental map of front-office versus back-office and voice versus non-voice, answers default to a generic 'handling customers' description.
What to do instead
Draw a two-by-two grid of voice/non-voice against front-office/back-office and place each service in a cell with one example and one metric (for example inbound voice: calls handled, average handling time, first-call resolution; transcription: accuracy percentage, turnaround time). Learn one distinguishing feature per term, especially BPO versus KPO (judgement-intensive work).
Answering occupational safety and health questions with general good intentions rather than named hazards and controls, for example ignoring ergonomic risks, electrical safety, or the correct response to a fire or a suspected repetitive strain injury.
Safety content is often skimmed as 'common sense', so candidates never learn the specific vocabulary of hazard identification, risk assessment and the hierarchy of controls, and cannot match a control to a hazard type.
What to do instead
Learn the hierarchy of controls (elimination, substitution, engineering controls, administrative controls, PPE) and, for each of the main IT/ITeS hazards (ergonomic, electrical, fire, noise, psychological stress), state one control at each level where possible. Practise the workstation setup checklist and the emergency sequence for fire and for reporting an injury.
Treating work ethics and IT/ITeS compliance as a list of virtues, so answers about confidentiality, data protection and professional conduct stay abstract instead of applying rules such as need-to-know access, client data handling, and reporting a breach.
Ethics is revised as adjectives ('honest', 'punctual') rather than as concrete obligations with procedures, and candidates have little exposure to real confidentiality agreements or escalation paths, so they cannot answer scenario questions.
What to do instead
Convert each ethical principle into a behaviour and a procedure: confidentiality becomes 'access only what the task requires, never copy client data to personal devices, report any suspected breach to the supervisor immediately'. For scenario questions, answer in three parts: what the rule is, what the person should do now, and whom to inform. Practise five short scenarios aloud.