Maharashtra HSC IT Science common mistakes
Maharashtra HSC IT Science · Understand the traps and how to avoid them.
Writing HTML tags without closing them or closing them in the wrong order (for example <b><i>text</b></i>), and leaving out the </body> and </html> tags entirely when asked to write a full page.
Candidates practise isolated tags in the browser, which tolerates sloppy nesting, so they never build the habit of checking the open/close stack. Under time pressure in the exam they write the visible content first and forget the structural wrapper.
What to do instead
Before writing any answer, sketch the skeleton first: , , with , then <body>. Fill content inside the body last. For nested tags, say the closing order aloud in reverse of the opening order. After finishing, mentally parse the page from top to bottom and tick each opened tag once it is closed.</p>
Confusing CSS selectors: using a dot for an id (#) or a hash for a class (.), and expecting inline styles to be overridden by an external stylesheet.
The two selector symbols look interchangeable and candidates memorise them as decoration rather than as type markers. Specificity rules are rarely practised because in simple demos only one rule applies to an element at a time.
What to do instead
Anchor the symbols to words: dot = class = many elements, hash = id = one element. Learn the specificity ladder as a short list (inline style beats id beats class beats element) and practise by writing two conflicting rules and predicting the winner before checking. In the exam, state the specificity order explicitly when explaining why a style applies.
Treating JavaScript as if it were PHP or HTML: writing <?php ?> inside a script block, using document.write() when the question asks for a form validation function, or forgetting that comparison uses === and not =.
The syllabus moves from HTML to JavaScript to PHP in sequence, and candidates carry syntax from the previous unit. The single equals sign is also natural to read as comparison in plain English.
What to do instead
Keep a one-page syntax card per language and revise it just before the paper. For any validation question, always produce the pattern: read the value with document.getElementById(...).value, test with ===, show a message with alert() or innerHTML, and return false to block submission. Re-read your answer and check every = inside an if condition.
Writing PHP variables without the $ sigil, forgetting semicolons, or mixing up echo and print in a way that breaks string concatenation, and placing PHP code outside <?php ?> tags.
PHP is the first server-side language candidates meet, and the $ prefix plus the dot concatenation operator feel unfamiliar. Since the output is not visible in a static editor, errors are discovered late.
What to do instead
Adopt a fixed writing order for each PHP answer: open . Use the dot operator only for joining strings and echo for output. When a question asks for form handling, write $_POST['field'] with the exact name attribute from the HTML form and mention that the form method must be post.
Writing SQL queries with the wrong clause order (SELECT ... WHERE ... FROM) or omitting the FROM clause, and using = NULL instead of IS NULL.
Candidates translate the English sentence word by word rather than following the fixed grammar of a SELECT statement. NULL behaves unlike ordinary values, which is counter-intuitive.
What to do instead
Memorise the clause order as a chant: SELECT, FROM, WHERE, GROUP BY, HAVING, ORDER BY. For every query, write the FROM table immediately after SELECT before adding conditions. Treat NULL as a special case and always write IS NULL or IS NOT NULL. For aggregate questions, check whether the filter belongs in WHERE (rows) or HAVING (groups).
Describing cloud service models by example only, so the answer says 'AWS is IaaS' or 'Gmail is SaaS' without defining what the provider manages versus what the user manages.
Textbook examples are easy to memorise, but exam questions often ask for a comparison or a justification, and the memorised label does not answer that.
What to do instead
Learn one sentence per model in terms of responsibility: IaaS gives virtual machines and storage while you manage the OS and above; PaaS gives a runtime and you manage only the application; SaaS gives a finished application and you manage only your data and access. In any answer, state the responsibility split first, then give the example as support.
Answering cyber law questions with generic moral statements ('hacking is bad') instead of naming the relevant provision, such as the IT Act, 2000 sections on unauthorised access, identity theft, or publishing obscene material, and the role of CERT-In.
Candidates treat this unit as general awareness and do not revise section numbers or the difference between civil and criminal liability under the Act.
What to do instead
Build a short table of offences with the section number, the act it covers, and the punishment in brief. Learn the roles separately: CERT-In for incident response and advisories, adjudicating officers for civil penalties, and police/courts for criminal offences. In an answer, name the Act and section, then apply it to the facts in the question.
Explaining operating system concepts only by definition, so a question on scheduling, deadlock, or memory management gets a textbook sentence with no worked example or comparison.
Definitions are the easiest part to memorise, and candidates stop there without practising the small numerical or comparative parts that carry the marks.
What to do instead
For each OS topic, prepare one concrete illustration: a three-process FCFS versus SJF timeline, the four necessary conditions for deadlock, or the difference between paging and segmentation. When answering, give the definition in one line, then the example or comparison, then a one-line conclusion. This structure earns the application marks that a bare definition misses.
Confusing bits and bytes, and binary and decimal conversions, when answering basics questions about storage units, number systems, or data representation, such as writing 1 KB = 1000 bytes or misplacing the place values in a binary-to-decimal conversion.
The units are taught quickly at the start of the course and then assumed, and candidates convert binary by guessing rather than by writing place values.
What to do instead
Write the place-value row 128, 64, 32, 16, 8, 4, 2, 1 above every binary number before converting. Memorise the ladder 8 bits = 1 byte, 1024 bytes = 1 KB, 1024 KB = 1 MB. For each conversion answer, show the working line so a single slip does not lose the whole mark.
Treating IoT and 5G questions as buzzword lists, listing 'smart cities, smart homes, sensors' without explaining the data flow from sensor to gateway to cloud to application, or the significance of low latency and high device density in 5G.
These are recent topics with less textbook depth, so candidates collect terms from current-affairs reading and never learn the architecture that the question is really testing.
What to do instead
Learn one four-stage IoT pipeline (sensing, connectivity, processing, action) and describe any IoT example through it. For 5G, remember the three headline capabilities: enhanced mobile broadband, ultra-reliable low latency, and massive machine-type communication, and link each to an IoT use case. In an answer, name the stage or capability before giving the example.