Assam ASSEB Higher Secondary Skill Subject IT/ITeS common mistakes
Assam ASSEB Higher Secondary Skill Subject IT/ITeS · Understand the traps and how to avoid them.
Writing 'RAM is a type of permanent storage' or 'ROM stores files you save' when answering a one-line recall question on memory, because the candidate has memorised the words volatile/non-volatile without attaching them to a meaning.
Memory questions are usually the first hardware topic taught and the last revised; students learn the acronyms by sound and never test them against a concrete example such as losing unsaved work at power-off.
What to do instead
For every memory type, write one sentence with a lived example: 'Unsaved Word text sits in RAM and disappears on power cut; the BIOS instructions sit in ROM and survive.' Then answer past-style items only after reciting that sentence. Keep a two-column table (volatile/non-volatile) with at least four devices in each column.
Confusing input, output and storage peripherals in classification items, for example labelling a touchscreen only as output, a pen drive as input, or a scanner as an output device.
Peripherals are taught as a list of pictures rather than as a direction-of-data flow, so candidates classify by what the device looks like instead of by whether data moves into or out of the CPU.
What to do instead
Draw an arrow diagram for each device: data direction relative to the computer. Mark hybrid devices explicitly (touchscreen = input and output; modem = both). Practise ten classification items and justify each with the direction of data, not the appearance.
Using spaces or repeated Tab presses to align text and columns in a word-processor task, and pressing Enter at the end of every line instead of letting text wrap.
Candidates transfer typing habits from mobile messaging and have never been shown that alignment is a paragraph or table property; they also fear the document will look wrong if they do not force line breaks.
What to do instead
Learn four tools and use them by name: paragraph alignment, tab stops or a table for columns, indent controls for first lines, and page break (Ctrl+Enter) for new pages. Redo one document twice, once with spaces and once with tabs/tables, and compare what happens when font size changes.
Entering a formula in a spreadsheet without the leading equals sign, or typing the computed number instead of a formula, so the sheet does not update when source data changes.
The spreadsheet looks like a table of text, and beginners do not distinguish a cell's displayed value from its underlying formula; they also fear error messages such as #NAME? and so avoid formulas.
What to do instead
Adopt the habit of typing '=' first and then clicking the cells rather than typing references. Practise five formulas (SUM, AVERAGE, MAX, MIN, a simple IF) on a small marks table, then change one input and confirm every dependent cell updates. Learn to read #NAME?, #DIV/0! and #REF! as diagnoses, not failures.
Answering internet and web questions by treating 'Internet', 'web', 'browser', 'search engine' and 'website' as synonyms, for example stating that Google is the Internet or that a browser is a search engine.
Everyday speech collapses these terms, and candidates have never been asked to separate the network layer from the service layer running on it.
What to do instead
Build a layered sketch: Internet = global network of networks and protocols (TCP/IP); web = one service on it (HTTP/HTTPS, pages, URLs); browser = client software that requests and renders pages; search engine = a website that indexes other pages. Then write a one-line definition for each with a concrete example and test yourself by sorting ten terms into the layers.
Describing cyber safety only as 'use a strong password and install antivirus', missing phishing, OTP sharing, UPI or banking fraud, oversharing on social media, and the reporting route when something goes wrong.
Safety chapters are skimmed as common sense, and the exam's scenario items reward specific recognition of an attack pattern and a specific response, not a general virtue.
What to do instead
Make a table of five attacks (phishing email, smishing SMS, vishing call, fake login page, OTP fraud) with the tell-tale sign and the correct action for each. Memorise the reporting channels used in India, including the national cybercrime reporting portal and the 1930 helpline, and the fact that no genuine bank asks for an OTP or PIN.
Answering database items by calling a row a 'field' and a column a 'record', or saying a primary key may contain duplicate values or be left blank.
Tables in everyday use are read horizontally, so the row/column vocabulary is not anchored, and the primary key rule is memorised as a phrase without a test case.
What to do instead
Anchor with a student table: one row = one student = a record; one column = one attribute = a field; roll number = primary key, unique and never null. Then attempt to insert two rows with the same roll number on paper and state exactly which rule is broken. Use the same table for every database question so the vocabulary stays consistent.
Writing a program or flowchart that ignores the order of operations in logic, for example using a single '=' for comparison, omitting the increment in a loop, or drawing a flowchart with no start or stop terminator and with decision boxes that have only one exit.
Candidates learn syntax by copying and never trace execution by hand, so off-by-one loops and missing terminators survive until the exam; flowchart symbols are also memorised as shapes without their exit rules.
What to do instead
Trace every algorithm on paper with a variable table, one row per iteration, before writing code. Enforce the conventions: '==' for comparison, '=' for assignment, every loop must change its control variable, every flowchart has one Start and at least one Stop, and every decision diamond has labelled Yes and No branches. Debug deliberately by planting an error in a working program and finding it.
Answering BPO/ITES and customer-handling scenarios with what the candidate personally feels is right, such as arguing with an angry customer, promising a refund outside policy, or transferring a call without logging it, instead of following escalation and empathy steps.
These items test process discipline, but candidates answer from instinct and have no model of a service-level process; they also equate being helpful with granting every request.
What to do instead
Learn a fixed sequence and apply it to every scenario: listen without interrupting, acknowledge the feeling, apologise for the inconvenience (not for fault), ask clarifying questions, state what you can do within policy, confirm agreement, log the interaction, and escalate only per the defined matrix. Practise by writing responses to three angry-customer scripts and checking each against that sequence.
In data entry and keyboard-skills tasks, watching the keyboard and correcting errors at the end, which produces high gross speed but poor accuracy, and using the wrong key for a symbol or for Indian currency and punctuation in a given layout.
Speed is visible and rewarded in practice drills, while accuracy is invisible until evaluation; candidates also never learn touch-typing home-row discipline or the location of less common keys.
What to do instead
Adopt the rule that accuracy comes first and speed follows: type at a pace where you can keep the error rate under about one per cent, keep fingers on the home row, and use the correct finger for each key. Do short timed passages of one minute, record both gross and net speed (net = gross minus errors), and drill the specific keys you miss rather than repeating whole passages.