Maharashtra HSC IT Commerce common mistakes
Maharashtra HSC IT Commerce · Understand the traps and how to avoid them.
Writing HTML tags in uppercase or mixing cases and leaving unclosed tags such as <p>, <li>, or <td>, so the answer sheet shows sloppy nesting that the examiner marks down.
Students memorise tag names but practise by typing quickly in a browser where the page still renders despite bad nesting, so they never feel the consequence of an unclosed element.
What to do instead
Practise writing each answer on paper and close every tag immediately after opening it, then verify nesting by indenting child elements one level. Keep tag names lowercase throughout since HTML5 is case-insensitive but consistent lowercase is the accepted convention.
Confusing inline CSS, internal CSS, and external CSS, and writing a style rule with the wrong syntax such as missing the colon, semicolon, or curly braces, e.g. p {color=red}.
The three placement methods look similar in textbook diagrams, and students copy syntax loosely without learning that declarations are property:value pairs separated by semicolons.
What to do instead
Memorise the rule shape selector { property: value; } and the three placements: style attribute for inline,
Declaring JavaScript variables with var everywhere and then failing output questions because of function scope versus block scope, or mixing up == and === in comparisons.
Many school textbooks still lead with var, and students treat == and === as interchangeable because both appear to compare values in simple examples.
What to do instead
Use let and const by default and reserve var only when a question explicitly asks about hoisting or function scope. Learn the rule that === compares type and value while == performs type coercion, and trace short code snippets on paper with a table of variable values after each line.
Writing PHP variables without the $ sigil, forgetting the semicolon at the end of statements, or echoing an array directly and expecting readable output.
PHP syntax resembles JavaScript and HTML, so students carry over habits from those languages, and array printing looks fine in their head even though PHP prints only "Array".
What to do instead
Drill the basics: every variable starts with $, every statement ends with ;, strings are concatenated with . not +, and arrays are inspected with print_r() or var_export(). Write and mentally execute five short scripts covering variables, concatenation, and loops.
Writing a SQL query that selects columns but omits the FROM clause, uses WHERE before FROM, or confuses WHERE with HAVING when an aggregate function is involved.
Students learn clauses as separate facts rather than as a fixed order, and GROUP BY with aggregate filtering is taught late so the WHERE/HAVING distinction blurs.
What to do instead
Memorise the clause order SELECT ... FROM ... WHERE ... GROUP BY ... HAVING ... ORDER BY and always write it in that sequence. Remember WHERE filters rows before grouping and HAVING filters groups after aggregation, then practise one query that uses COUNT with HAVING.
Describing cloud service models by naming examples instead of defining responsibility, so IaaS, PaaS, and SaaS answers get swapped when the question asks who manages the operating system or the application.
The three models are taught with product examples such as Gmail or AWS, and students map products to models without learning the management-responsibility split that examiners actually test.
What to do instead
Anchor each model to what the provider manages: IaaS gives virtual machines and the user manages the OS upward, PaaS gives a runtime and the user manages only the application, SaaS gives a finished application the user only configures. Answer with that split first, then add an example.
Treating e-commerce payment and security questions generically, writing only that "encryption keeps data safe" without naming the mechanism, the parties, or the risk being addressed.
Cyber security topics are read as definitions to memorise, and students lack the habit of linking a control such as SSL/TLS, digital signature, or two-factor authentication to a specific threat like phishing, card fraud, or man-in-the-middle attack.
What to do instead
For each answer, state the threat, the control, and how the control blocks the threat, for example: card data in transit is exposed to interception, so TLS encrypts the channel between browser and server. Build a two-column table of threats and matching controls and revise it before the exam.
Answering operating system questions with a list of names only, such as "Windows, Linux, Android", when the question asks for a function, a scheduling type, or a comparison of GUI versus CLI.
Students revise OS by memorising brand names and logos rather than the concepts of process management, memory management, file systems, and user interfaces that the syllabus tests.
What to do instead
Prepare short structured answers for each core function: process and memory management, file system handling, device management, and user interface. For comparisons, use a two-column table of points rather than prose so each difference is explicit.
Giving vague definitions of IoT, AI, and 5G with no architecture or characteristics, for example "IoT means connecting devices to the internet" with no mention of sensors, actuators, connectivity, or data processing layers.
Emerging technology chapters are new and lightly practised, so students rely on general awareness from news rather than the four-layer IoT architecture and the specific characteristics listed in the textbook.
What to do instead
Memorise a small structural skeleton per technology: IoT as sensing, network, data processing, and application layers with sensors and actuators; AI by its goals and example applications; 5G by its key features such as high speed, low latency, and massive device density. Answer with the skeleton, then add one example.
Skipping or mislabelling the practical section, such as writing a program without the required output sample, not drawing the table or diagram the question asks for, or leaving the answer in rough work without transferring it.
Time pressure in the practical and theory paper leads students to attempt the coding question last, and they underestimate how many marks depend on showing output, comments, or labelled diagrams.
What to do instead
Practise timed papers where you write the program, a sample input, and the expected output together as one unit. Before submitting, check every question for the words draw, label, state output, or give an example, and confirm each of those elements is present.