RBSE VU IT and ITeS common mistakes
RBSE VU IT and ITeS · Understand the traps and how to avoid them.
When asked to identify hardware versus software, the candidate labels firmware, an operating system, and a device driver as hardware because they are 'already inside the machine', and labels a smartphone's preinstalled apps as hardware.
Everyday language treats anything not visibly installed by the user as part of the machine, and the candidate has memorized examples (keyboard, mouse, monitor) without the defining criterion of whether the item is a physical component or a set of instructions.
What to do instead
Apply a single test to every item: if it can be touched or has mass it is hardware; if it is instructions or data it is software, regardless of where it is stored. Practise sorting a list of 20 mixed items, including firmware, BIOS, drivers, RAM, ROM, and cloud storage, and write one sentence justifying each borderline case.
The candidate computes spreadsheet results by hand instead of stating the formula, or writes =2+3*4 and reports 20, and confuses relative and absolute references when a formula is copied across a row.
The candidate has used a spreadsheet to get answers but never learned operator precedence or the meaning of the $ sign, so they reason about numbers rather than about what the formula instructs the software to do.
What to do instead
Before answering, rewrite the formula with brackets showing evaluation order (2+(3*4)=14) and state the result of the expression, not the result of the problem. For copying questions, trace one cell: write the original formula, then rewrite it with each reference shifted by the number of columns and rows moved, and remember $ locks the column, the row, or both.
The candidate describes a mail merge, a slide transition, or a database relationship in vague general terms ('it combines things', 'it makes it look nice') without naming the required steps, fields, or objects, so the answer cannot be credited.
The candidate recognizes the feature name and assumes recognition equals knowledge, and has never performed the operation end to end, so no procedural memory exists to draw on.
What to do instead
For each major feature, memorize a short ordered procedure with named parts: mail merge = main document, data source, insert merge fields, preview, finish and merge; slide transition = effect between slides, animation = effect on objects within a slide; relationship = primary key to foreign key, one-to-many. Rehearse each aloud in under 30 seconds.
When asked what happens when a URL is typed, the candidate answers only 'the page opens' or claims the browser searches the internet directly, omitting DNS resolution, the request to the server, and the response.
The browser hides all intermediate steps, so the candidate has only ever observed the start and the end of the process and has never been taught the middle.
What to do instead
Memorize a five-step chain and always write all five: the browser asks a DNS server to translate the domain name into an IP address, it opens a connection to that server, it sends an HTTP/HTTPS request, the server returns a response with a status code and content, and the browser renders the page. Attach one sentence to each step so the chain is meaningful rather than recited.
The candidate writes email and customer-service answers in casual chat style, with no subject line, no greeting or sign-off, emojis, and SMS abbreviations, and treats a complaint reply as a place to defend the company.
The candidate's only model for written communication is messaging with friends, and the exam's professional-context cues (subject line, formal register, acknowledgement before explanation) have never been made explicit.
What to do instead
Use a fixed skeleton for every written answer: clear subject, courteous greeting, acknowledgement of the customer's issue in the first sentence, factual explanation or action, next step with a timeframe, professional sign-off. Ban emojis and abbreviations, and check that the reply never blames the customer.
The candidate answers database questions by describing physical storage ('the data is kept in a folder on the hard disk') or confuses a table with a database, a row with a field, and a primary key with any unique-looking column, and cannot explain what a foreign key does.
The vocabulary is new and similar-sounding, and the candidate has seen data only in files and spreadsheets, so they map unfamiliar terms onto familiar objects instead of learning the relational model.
What to do instead
Draw a two-table example (Customers and Orders) and label every part: the database contains tables, a table contains records (rows) and fields (columns), the primary key uniquely identifies a row and cannot be null or duplicated, and the foreign key in Orders repeats the Customers primary key to link the two. Answer using these labels rather than storage language.
The candidate describes BPM/BPO work as 'handling calls' and cannot distinguish front-office from back-office processes, inbound from outbound, or an SLA from a KPI, and gives no measurable content when asked how service quality is tracked.
The industry is familiar only as a consumer experience, and the operational vocabulary (SLA, AHT, first-call resolution, shrinkage, escalation) is never used in daily life, so the candidate substitutes a lay description.
What to do instead
Build a one-page glossary with an example for each term: front office = voice support and customer contact, back office = data processing, claims, and finance work; SLA = the contractual commitment, KPI = the measure used to track it; AHT = total talk plus hold plus after-call work divided by calls handled. Use at least two of these terms with numbers in any service-delivery answer.
On security and ethics items, the candidate says a strong password is one with a capital letter and a symbol, agrees to share login credentials with a colleague 'to help', and forwards customer data to a personal email to finish work at home.
Convenience habits from personal use are carried into a work context, and the candidate has learned password rules as a checklist for creating passwords rather than as principles for protecting accounts and data.
What to do instead
Anchor every answer to three principles: credentials are personal and never shared, personal data is used only for the purpose it was collected for and never moved to personal accounts or devices, and any suspected incident is reported to the designated authority rather than handled quietly. For password questions, state length and uniqueness first, then complexity, then multi-factor authentication.
In employability and entrepreneurship answers, the candidate lists only 'hard work, honesty, good communication' with no situation, action, or result, and cannot name a concrete IT/ITeS role, its entry-level skill set, or a realistic next step after Class 12.
The candidate has absorbed values as slogans and has not connected the syllabus to their own pathway, so they produce generic adjectives instead of evidence and specifics.
What to do instead
Prepare three STAR stories (Situation, Task, Action, Result) from school, project, or part-time work that each demonstrate a named skill such as teamwork, problem solving, or customer focus. Separately memorize three entry routes with their core skills, for example technical support (troubleshooting, OS and networking basics, ticket handling), data entry and BPO associate (accuracy, typing speed, process compliance), and web or app development (HTML/CSS/JavaScript, version control).
For the practical and portfolio component, the candidate submits screenshots or a file dump with no explanation of purpose, tools, steps, or their own contribution, and cannot answer a viva question about why a design or formula choice was made.
The candidate treats the project as a deliverable to hand over rather than as evidence of a process, and has not documented decisions while doing the work, so nothing remains to explain afterwards.
What to do instead
Maintain a project log from day one with date, task, tool used, problem encountered, and how it was solved, and keep earlier versions. In the final report, add a short section for each artefact stating its purpose, the tools and features used, the steps taken, and what you would improve. Rehearse a two-minute walkthrough of one artefact that names a specific decision and its reason.