RBSE Prav Voc IT and ITeS common mistakes
RBSE Prav Voc IT and ITeS · Understand the traps and how to avoid them.
When a spreadsheet question asks for the result of a formula such as =SUM(A1:A3)*2 or =AVERAGE(B2:B5), candidates manually add or average the visible numbers and type the arithmetic answer instead of stating what the formula returns, or they treat the range A1:A3 as including A3 only when a cell is empty.
Candidates memorise SUM and AVERAGE as 'add up' and 'average' without practising how ranges, operators and precedence behave, and they rarely test formulas with an empty cell or a text cell in the range. Under exam pressure they fall back on mental arithmetic, which also introduces slips.
What to do instead
Practise reading formulas aloud in operator order: first evaluate each range, then apply * and / before + and -, and treat empty cells as ignored by SUM and AVERAGE but counted by COUNTA. Build a 10-row drill sheet where you predict the output of five formulas before pressing Enter, and note that text inside a range is ignored by SUM but breaks multiplication.
In word-processing questions, candidates describe how to centre a heading or set line spacing by saying 'use the toolbar' or 'change the font settings' instead of naming the exact tab, group and command, for example Home tab > Paragraph group > Center, or Layout tab > Paragraph group > Spacing.
Most candidates learn Word or Writer by clicking icons from memory and never map commands to their tab and group names. Exam items test the ribbon structure, so a vague answer that would work in practice still loses marks.
What to do instead
Make a one-page command map for the ten most examined actions (alignment, line spacing, indents, bullets, page orientation, margins, header/footer, page break, find and replace, spell check), each written as Tab > Group > Command. Recite the map weekly and verify each entry on a real installation.
Candidates answer operating-system questions by mixing categories: they call Windows an application, describe RAM as permanent storage, or say that deleting a file from a folder removes it from the Recycle Bin and frees space immediately.
Everyday use hides the distinction between hardware, the operating system and applications, so candidates repeat loose phrasing they have heard. The Recycle Bin behaviour is rarely observed because most users empty it without thinking about what happened.
What to do instead
Draw a three-layer diagram (hardware, operating system, application) and place ten named examples in each layer. Separately, trace the file-deletion lifecycle: move to Recycle Bin, restore, permanent delete with Shift+Delete, empty Recycle Bin. State in one sentence what changes at each step and where space is actually released.
On internet and email items, candidates confuse protocols and services: they say SMTP is used to receive mail, describe HTTP as a secure protocol by default, or explain that a URL and an IP address are the same thing because both locate a site.
Protocols are invisible in normal use, so candidates learn them as vocabulary lists without a model of what each one does. The send-versus-receive distinction and the role of DNS are the parts most often skipped.
What to do instead
Learn protocols as a send/receive table: SMTP for sending, POP3 and IMAP for receiving (with IMAP keeping mail on the server), HTTP/HTTPS for web pages, FTP for file transfer, DNS for resolving names to IP addresses. Then explain one full email journey from typing an address to the recipient reading it, naming each protocol at its step.
In database questions, candidates use table, field, record, primary key and foreign key interchangeably, for example saying a primary key may contain duplicate values or that a foreign key must be unique within its own table.
The relational model is taught with definitions but few concrete examples, so the constraints on keys are remembered as slogans. Candidates also confuse a row with a column when reading a sample table described in text.
What to do instead
Build one small table on paper (StudentID, Name, Class, Email) and label the row as a record, the column as a field, StudentID as the primary key with the uniqueness and no-null rules written beside it, and a ClassID column as a foreign key referencing a Class table. Redo the labelling from memory until the constraints come out unprompted.
Cyber-safety items are answered with vague advice such as 'be careful online' or 'use a strong password' without naming the mechanism, for example not identifying phishing cues in a described message, not explaining what two-factor authentication adds, or not stating that HTTPS and the padlock indicate encryption rather than trustworthiness of the site.
Safety content is absorbed as general awareness from posters and assemblies, not as testable specifics. Candidates also assume that any site with a padlock is safe, which is a common real-world misconception carried into the exam.
What to do instead
Practise with a checklist applied to short written scenarios: sender address mismatch, urgency and threat, unexpected attachment, link text versus real destination, request for OTP or password. For each scenario, name the cue and the correct action. Separately memorise what the padlock does and does not prove.
When asked about IT-enabled services and BPO operations, candidates describe them only as 'customer care by phone' and cannot distinguish front-office from back-office work, inbound from outbound processes, or voice from non-voice services, so they misclassify examples such as payroll processing, medical transcription or data entry.
The domain is often taught through a few familiar job titles rather than through the process categories that exam items test. Candidates generalise from personal experience of call centres and miss the non-voice majority of the sector.
What to do instead
Create a two-way grid: front office versus back office on one axis, voice versus non-voice on the other, and place at least twelve named services (technical support, telemarketing, payroll, claims processing, transcription, data entry, HR helpdesk, chat support) into cells. Justify each placement in one line using who interacts with the customer and whether speech is involved.
Presentation-software questions are answered by describing content rather than function: candidates say 'add animation to make it interesting' without naming entrance, emphasis and exit effects, or they cannot explain slide master, transitions versus animations, or why a master slide saves effort.
Presentations are learned by making one deck quickly, so the feature names and the distinction between a transition (slide to slide) and an animation (object within a slide) are never fixed. The master slide is usually never opened.
What to do instead
Learn four named feature pairs with one-line contrasts: transition versus animation, slide master versus individual slide, slide sorter versus normal view, embed versus link. Then build a five-slide deck that uses a master slide for a consistent footer and one entrance and one exit animation, and write down which pane you used for each.
Emerging-technology items are answered with buzzwords but no mechanism: candidates call any online storage 'cloud computing' without naming IaaS, PaaS or SaaS, describe artificial intelligence as 'computers thinking like humans' only, or claim blockchain is the same as a database with a password.
These topics change quickly and are often covered through news headlines, so candidates pick up labels without the defining properties. Exam items usually test one distinguishing property, which the headline-level answer cannot supply.
What to do instead
For each technology (cloud, AI, machine learning, IoT, blockchain, big data), write a three-line card: definition in one sentence, one distinguishing property, one concrete example with the service model or layer named. Test yourself by classifying five real services into SaaS, PaaS or IaaS and justifying each in a phrase.
Soft-skills and communication items are answered with slogans such as 'communication should be good' or 'listen actively' without applying them: candidates fail to identify the barrier in a described exchange, cannot rewrite an aggressive sentence into an assertive one, or ignore audience and channel when asked to choose how to convey a message.
Soft skills are treated as personality rather than as assessable technique, so candidates never practise naming barriers or restructuring sentences. They also answer from instinct rather than from the scenario given in the question.
What to do instead
Learn a short barrier list (physical, semantic, psychological, organisational, cultural) and tag ten described incidents with the barrier and a remedy. Then rewrite five blunt sentences into assertive, audience-appropriate versions, stating what changed (word choice, tone, channel). For channel questions, justify the choice by urgency, need for a record and audience location.