Karnataka KSEAB SSLC NSQF Information Technology common mistakes
Karnataka KSEAB SSLC NSQF Information Technology · Understand the traps and how to avoid them.
When asked to convert a decimal number to binary, the candidate divides by 2 but writes the remainder digits in the order they are produced (top to bottom) instead of reading them bottom to top, so 13 is written as 1011 rather than 1101.
The repeated-division method is memorised as a list of steps but the reason for reversing the remainders is never understood; the first remainder is the least significant bit, and candidates who only practise with palindromic values such as 5 (101) never notice the error.
What to do instead
Practise a fixed five-step routine on non-palindromic numbers (13, 19, 26, 45): divide, note remainder, stop at quotient 0, then read upwards and verify by expanding the place values back (8+4+1=13). Always check the answer by converting back before moving on.
The candidate labels a folder tree or file path incorrectly, for example writing C:/Projects/Notes.txt as though Notes.txt were a folder, or confusing the root directory with the current working directory when asked where a saved file will be stored.
Paths are learned as strings to copy rather than as a hierarchy; students rarely see the difference between a drive, a directory, a subdirectory and a file because they work inside a single window and never view the address bar or the folder tree pane.
What to do instead
Draw the tree by hand for every path question: root at the top, each backslash as one level down, the last item as the file. Practise reading the address bar in File Explorer and answering 'name the parent folder' and 'give the full path' for the same file until both are automatic.
In a word processor question, the candidate applies direct formatting (selecting text and pressing Bold or changing the font size) when the task asks for a heading style, automatic table of contents, or consistent formatting across a document.
Toolbar buttons are the most visible controls, so they are used for everything; the Styles gallery and its role in generating a table of contents or navigation pane are usually demonstrated once and never practised.
What to do instead
Learn one rule: structure comes from Styles, appearance comes from direct formatting. Rebuild a two-page document using Heading 1 and Heading 2 for every section, insert an automatic table of contents, then change one heading style and confirm every heading updates at once.
When writing a spreadsheet formula, the candidate types the numbers directly (for example =25*4+10) instead of referring to cells (=A2*B2+C2), and then copies the formula and reports wrong results because the values did not move with it.
Spreadsheet questions often show one worked row, and candidates reproduce the visible arithmetic rather than the reference logic; the idea that a formula is a reusable instruction, not a calculation, is not made explicit.
What to do instead
Adopt the habit of never typing a number that already exists in a cell. Build a small marks table, write =SUM(B2:D2) and =AVERAGE(B2:D2), fill down, then deliberately change one input value and check that all dependent results update. This proves the references are live.
The candidate confuses absolute and relative references, so a formula containing a fixed rate cell (for example a tax or percentage stored in one cell) gives correct answers in the first row but wrong answers after being filled down.
The dollar sign is treated as decoration; the difference between A1, $A$1, A$1 and $A1 is taught as four symbols to memorise rather than as 'lock the column, lock the row' behaviour, and the fill handle silently shifts whatever is not locked.
What to do instead
Use the F4 key to cycle the four reference forms while watching the formula bar. Practise one exercise: a percentage in a single cell, a column of amounts, and a formula that must lock the percentage cell with $ so that filling down twenty rows keeps every answer correct.
In a presentation task, the candidate pastes whole paragraphs onto slides and reads them aloud, or adds animations and transitions to every element, so the slide fails the stated requirement of being readable and focused.
Word-processing habits carry over into slide design, and animation effects are the most entertaining feature in the software; rubrics that reward concise bullet points, a consistent theme and a clear visual hierarchy are rarely discussed in class.
What to do instead
Apply a strict limit: no more than six bullet points per slide and no more than about eight words per bullet, with detail moved into speaker notes. Design one title slide, one bullet slide and one chart slide using a single theme and one transition, then present it to a partner who checks whether the slides support the talk rather than replace it.
The candidate treats a web address as a single string and cannot separate the protocol, domain name, path and file type, so questions about secure sites, top-level domains or the difference between a search engine and a browser are answered by guessing.
Browsers hide most of the address, and searches are usually started from the address bar, so students never see the structure of a URL or the distinction between typing a URL and typing a query.
What to do instead
Take three real URLs and label each part on paper: https, the domain, the top-level domain such as .gov.in or .com, the folder path and the file extension. Then practise explaining why https matters, what a search engine returns, and how a browser differs from a search engine, using those labelled examples.
When asked to identify a primary key or to choose a data type for a field, the candidate picks any unique-looking column, such as a name or a phone number, or stores a date as text, and then cannot explain why duplicate or empty values cause problems.
Primary keys are defined as 'unique' but the additional requirements (never null, never changing, minimal) are omitted, and data types are chosen by appearance rather than by the operations that will be performed on the field.
What to do instead
For each field in a sample table, ask three questions: can it be empty, can it change, is it guaranteed unique? Choose a roll number or ID as the key and justify it in one sentence. Then test the choice by trying to insert a duplicate and a blank value in a real table and observing the rejection.
The candidate traces a loop by executing it in their head and reports the final value only, missing off-by-one errors, the number of iterations, or the difference between a condition tested before and after the body runs.
Loops are read as text rather than simulated; without writing down each pass, the update step and the test condition blur together, and the first or last iteration is where errors concentrate.
What to do instead
Use a trace table with one column per variable and one row per iteration. For a loop from 1 to 5, write the value of the counter and the accumulator at every pass, then compare with a while loop that tests at the start and a do-while that tests at the end. State the iteration count explicitly before answering.
When a scenario describes a phishing message, a weak password, or sharing personal information, the candidate answers with a slogan such as 'be careful online' instead of naming the specific threat, the warning sign in the scenario, and the concrete action to take.
Cyber safety is revised as a list of warnings rather than as a set of recognisable signals; candidates also conflate related terms such as phishing, spam and malware, so they cannot match the scenario to the correct label.
What to do instead
Build a three-column table of threat, warning sign, action, with one row each for phishing, spam, malware, cyberbullying, identity theft and unsafe password practice. For every practice scenario, answer in the form 'this is X because of Y, so I would do Z', which matches how marks are awarded.
In employability-skills questions, the candidate describes teamwork or communication in abstract terms ('I am a good team player') without giving a situation, the action taken and the result, and cannot match a résumé or cover-letter item to the job requirement stated in the question.
These answers are written as self-descriptions rather than as evidence; the situation-action-result structure and the practice of mirroring the employer's stated requirement are rarely rehearsed, so answers stay generic.
What to do instead
Prepare four short stories (a group project, a problem solved, a deadline met, a skill learned) each in three sentences: situation, action, result. For résumé and cover-letter tasks, underline the requirement in the question and write one line that directly answers it with evidence from those stories.