Odisha CHSE +2 Vocational Information Technology common mistakes
Odisha CHSE +2 Vocational Information Technology · Understand the traps and how to avoid them.
Writing spreadsheet formulas as typed text (e.g., '=A1+B1' shown as a literal string) because the cell was formatted as Text before entering the formula, or because the formula was typed with a leading apostrophe.
Candidates paste or pre-format a whole column as Text to preserve roll numbers and marks, then type formulas into those same cells; Excel/Calc treats the entry as a label and displays it verbatim, so totals stay blank or show the formula itself.
What to do instead
After typing a formula, check the cell's number format and look for the green error triangle or a left-aligned result. Convert the column to General/Number before entering formulas, or re-enter the formula after clearing the apostrophe. Verify by confirming the displayed value differs from the typed expression.
Using relative cell references (B2, C2) in a formula that is then copied down a table, so marks are pulled from the wrong row, or using absolute references everywhere so every row repeats row 2's value.
Candidates learn the fill handle first and assume copying 'just works'; they have not internalised that $B$2 locks a cell while B2 shifts with the copy. Without a mixed-reference example in practice, the choice looks arbitrary.
What to do instead
Before copying, ask whether the reference should move with the row. Lock only constants (fixed rate, max marks) with $, leave data references relative. Test by copying two rows and clicking each copied cell to read the formula bar, confirming the intended shift.
Confusing primary key with foreign key in a table-design question, or declaring a foreign key on the wrong table, so the answer describes a column that references another table as if it uniquely identifies rows.
Both are 'keys' and both appear in the same CREATE TABLE statement; candidates memorise definitions as sentences rather than as roles played by a column in a specific table, so they cannot apply the definition to a given schema.
What to do instead
For each key question, state in one line: 'Which table does this column live in, and does it identify a row there or point to a row elsewhere?' A column that identifies its own table's row is primary; a column that matches another table's primary key is foreign. Write both lines before choosing.
Writing SELECT queries with WHERE placed before FROM, or omitting GROUP BY while using an aggregate such as COUNT(*) alongside a plain column, producing a query that runs but returns one unexpected row.
Candidates write SQL in the order they think ('I want these rows, from this table') rather than the clause order the DBMS parses. Aggregates are learned as functions, not as grouping operators, so the mandatory GROUP BY is forgotten.
What to do instead
Memorise the skeleton SELECT … FROM … WHERE … GROUP BY … HAVING … ORDER BY and write it top-down even when thinking bottom-up. Before submitting, check: any aggregate plus a non-aggregate column requires GROUP BY on that column.
Describing an algorithm or program only in prose ('take input, add the numbers, print result') instead of giving ordered steps with initialisation, loop condition, and termination, so the logic cannot be traced.
Candidates can solve the problem mentally and assume the examiner can follow the same leap; they have not practised writing pseudocode or a flowchart as a graded artefact, so they omit the counter increment or the loop exit condition.
What to do instead
Write every answer as numbered steps: declare and initialise variables, state the loop condition and what changes each iteration, then the output step. Dry-run with two sample inputs (including an edge case such as zero items) and show the trace alongside the steps.
Using the wrong relative/absolute path or omitting the extension when answering file-management tasks, e.g., saving to C:\ rather than the specified folder, or naming a file report instead of report.docx.
Candidates focus on content and treat saving as an afterthought; they also conflate the folder shown in the dialog with the actual save location, and assume the application will append the right extension.
What to do instead
Treat the save step as part of the task: navigate to the named folder, type the full filename with extension, and confirm the extension matches the application (docx, xlsx, pptx, odt). Reopen the file from the stated path to prove it is where the question asked.
Confusing the roles of RAM and secondary storage, or of ROM and cache, in questions about volatility and boot process, e.g., stating that data in RAM survives a power cut or that the OS is permanently stored in RAM.
Everyday language calls both 'memory', and candidates learn definitions as isolated sentences without a mental model of the boot sequence (ROM firmware → load OS from disk → run in RAM), so the terms blur under exam pressure.
What to do instead
Anchor each term to one behaviour: RAM is volatile working space, ROM is non-volatile firmware, disk is non-volatile long-term storage, cache is fast small memory near the CPU. Answer by tracing the boot sequence in order and naming which memory holds what at each stage.
Answering email and web questions with the wrong protocol or field, e.g., saying SMTP downloads mail, putting the recipient in Cc when Bcc was required, or confusing a URL's domain with its path.
Protocols are memorised as a list (SMTP, POP3, IMAP, HTTP, FTP) without attaching direction or purpose; addressing fields are learned visually from a mail client rather than by function, so To/Cc/Bcc get treated as interchangeable.
What to do instead
Attach one verb to each protocol: SMTP sends, POP3/IMAP retrieve, HTTP transfers web pages, FTP transfers files. For addressing, state the purpose in one line (To = primary recipient, Cc = visible copy, Bcc = hidden copy) and check the question's wording for 'hidden' or 'without other recipients seeing'.
In presentation questions, pasting whole paragraphs onto a slide, or describing animation and transition as the same feature, so the answer names the wrong effect for 'movement between slides' versus 'movement of an object on a slide'.
Candidates transfer document habits to slides and equate more text with more marks; the animation/transition distinction is a one-word difference that is easy to skim past in a question stem.
What to do instead
Apply a slide rule: no more than about six short lines per slide, keywords not sentences. For effects, decide whether the movement is between slides (transition) or within a slide on an object (animation) before naming the feature, and state that distinction explicitly in the answer.
Giving a definition-only answer to a practical or project question, e.g., listing steps to create a table without mentioning the fields, data types, or the final saved filename, or describing a project's objective without stating the tools used and the outcome.
Candidates revise theory notes and reuse them for applied questions; practical tasks are marked on observable actions and artefacts, which theory answers never mention, so marks are lost despite correct concepts.
What to do instead
For practical answers, produce an artefact list: tool used, exact steps in order, field names with data types, filename with extension, and how the result was verified. For project answers, add objective, tools, output and one measurable result, so the answer contains evidence rather than description.