Karnataka KSEAB II PUC Information Technology (Vocational) common mistakes
Karnataka KSEAB II PUC Information Technology (Vocational) · Understand the traps and how to avoid them.
When asked to convert between number systems (binary, decimal, octal, hexadecimal), the candidate converts only the integer part and either drops the fractional part or converts it in the wrong direction, producing an answer like 1011.11 for a decimal fraction that should terminate.
Classroom drill usually stops at whole numbers, so the fractional conversion procedure (repeated multiplication by the target base, reading remainders top-down) is memorised weakly or not at all, and under time pressure the candidate reuses the integer algorithm out of habit.
What to do instead
Practise a fixed two-column layout: integer part by repeated division (read remainders bottom-up), fractional part by repeated multiplication (read integer digits top-down), and stop only when the fraction reaches zero or the required precision. Do ten mixed drills that include fractions such as 0.625 and 0.1, and verify every answer by converting back to decimal.
The candidate labels a device or medium as input or output by its physical appearance rather than by data flow, for example calling a touchscreen only an output device, treating a pen drive as input only, or classifying a plotter as an input device.
Everyday language ('I put the file on the drive') reinforces a one-way mental model, and hybrid devices are taught late, so students default to a simple list memorised from a textbook table.
What to do instead
For each device, write a one-line data-flow statement ('data enters the computer here' / 'data leaves here' / 'both, depending on mode') and classify by that sentence, not by the name. Build a personal table of at least fifteen devices including touchscreen, modem, plotter, scanner, and headset, marking the hybrid ones explicitly.
In file-management questions the candidate gives a path that is syntactically wrong for the operating system in question: mixing backslashes and forward slashes, omitting the drive letter on Windows, or writing a relative path where an absolute path was asked for.
Students practise on one machine and generalise its conventions, and the distinction between absolute and relative paths is often demonstrated only verbally, so it is not consolidated.
What to do instead
Learn the two canonical forms as templates: Windows absolute path C:\folder\subfolder\file.ext and Linux absolute path /home/user/folder/file.ext. For every practice question, first underline the words 'absolute' or 'relative', then write the path from the root, and check separator direction and extension before moving on.
The candidate confuses Save with Save As, or describes a shortcut incorrectly, so an answer claims that Ctrl+S creates a new copy under a new name, or that closing a document automatically saves changes.
The two commands look identical in a toolbar and the difference only appears when a second version is needed, which rarely happens in guided classroom exercises.
What to do instead
Memorise one discriminating sentence: Save overwrites the current file in its current location; Save As writes a new file and lets you choose name, location, and format. Test yourself with scenarios ('keep the original and make an edited copy', 'change the file to PDF') and state which command applies and why.
When writing spreadsheet formulas the candidate types the numbers instead of cell references, or omits the leading equals sign, so the cell shows the formula as text or the result does not update when source data changes.
Beginners think of a spreadsheet as a calculator and of the formula bar as a place to record a sum, not as a live dependency graph, so relative referencing and recalculation are not internalised.
What to do instead
Adopt a rule: every formula starts with = and refers to cells, never to constants unless the value is a true constant such as a tax rate. After writing a formula, change one input cell and confirm the result changes. Then copy the formula down and inspect how relative references shift, and use $ explicitly when a reference must stay fixed.
The candidate builds a chart or applies a filter without first selecting a clean data range, so headers are plotted as a data series, blank rows split the range, or totals rows are included in the chart.
Chart wizards accept whatever is selected and produce a plausible-looking but wrong chart, so the error is invisible unless the student reads the legend and axis labels critically.
What to do instead
Before inserting any chart, select exactly the header row plus data rows, with no blank rows and no totals. After insertion, read the legend aloud and check that each series name matches a column header and that the category axis shows the intended labels. Remove totals rows from the source range and compute them separately.
In database questions the candidate confuses a primary key with a foreign key, or writes a query that selects the wrong columns or omits the WHERE clause, returning every row when a filtered result was asked for.
Keys are taught as definitions rather than as constraints with consequences, and students translate a natural-language request word by word without mapping it to the SELECT–FROM–WHERE skeleton.
What to do instead
Write the key definitions as behaviour tests: a primary key uniquely identifies a row in its own table and cannot be null; a foreign key references a primary key in another table and enforces referential integrity. For queries, always draft the skeleton SELECT columns FROM table WHERE condition first, then fill in each clause, and check the column list against the question wording.
When tracing a short algorithm the candidate executes statements in the written order while ignoring loop boundaries and the effect of an accumulator, so the final value of a sum or counter is off by one iteration.
Tracing is done mentally rather than on paper, and the difference between a loop that runs while i < n and one that runs while i <= n is treated as cosmetic.
What to do instead
Trace on paper with a table of columns for each variable and one row per iteration, writing the condition result before each pass. Do paired exercises with < and <= on the same loop and compare the iteration counts. State the number of iterations before starting, then confirm it against the table.
The candidate writes HTML with unclosed or improperly nested tags, or expects a browser to display a page correctly when the file was saved with the wrong extension such as .txt instead of .html.
Editors forgive missing closing tags and browsers render something anyway, so the student never receives a clear failure signal and never learns to check structure or file type.
What to do instead
Follow a closing-tag discipline: type the opening and closing tag together, then insert content between them, and indent nested elements. Save with the .html extension explicitly and reopen the file in the browser to confirm. Validate structure by reading the nesting aloud ('list inside body, items inside list').
The candidate answers network questions by matching keywords rather than distinguishing topology, device, and protocol, for example calling a switch a device that routes packets between different networks, or naming HTTP as a protocol that assigns IP addresses.
The vocabulary is dense and many terms are introduced in one chapter, so students memorise labels without attaching each to a distinct function, and similar-sounding terms collapse together.
What to do instead
Build a three-column table: term, layer or category, one-sentence function. Force a distinguishing phrase for each pair that is commonly confused (hub versus switch, switch versus router, IP versus MAC address, HTTP versus FTP versus SMTP). Before answering, identify which category the question is asking about, then choose the term from that column only.