HSC Information and Digital Technology (VET) common mistakes
HSC Information and Digital Technology (VET) · Understand the traps and how to avoid them.
When asked to identify a workplace safety hazard or risk control, the candidate lists a general hazard (e.g., 'electrical equipment') without specifying the concrete unsafe condition or the hierarchy-of-control measure required.
Candidates memorise broad hazard categories from the syllabus but do not practise applying the hierarchy of risk control (eliminate, substitute, isolate, engineer, administrate, PPE) to a specific scenario, so their answers stay at the level of a label rather than an action.
What to do instead
For every WHS scenario, force yourself to write two sentences: one naming the specific hazard condition (e.g., 'a frayed power lead on a bench tester with exposed inner wires') and one naming the highest-level control that is reasonably practicable, then the residual administrative or PPE control. Practise with ten common IT workplace scenarios (cable trays, battery disposal, workstation ergonomics, server room heat, manual handling of monitors) until the pattern is automatic.
The candidate describes environmental sustainability only as 'recycling' and misses the full asset lifecycle (procurement, energy use, reuse, refurbishment, responsible disposal, e-waste legislation).
Sustainability is often taught as a single lesson on e-waste, and candidates default to the most familiar example rather than structuring an answer around the lifecycle stages the marking criteria reward.
What to do instead
Build a one-page lifecycle template with six stages and one IT example each: procurement (energy-star rating, packaging), operation (power management, virtualisation), reuse (redeploying leased laptops), refurbishment (battery replacement), disposal (certified e-waste recycler, data sanitisation), and reporting (waste audit). Use the template to answer any sustainability question so every stage is considered.
The candidate answers customer-service and teamwork questions with generic attitudes ('be polite', 'communicate well') instead of naming the specific technique, the audience, and the measurable outcome.
These questions look easy, so candidates write the first pleasant-sounding sentence that comes to mind and stop, not realising that the marks are in the specificity of the technique (e.g., active listening, paraphrasing, escalating with a ticket reference) and the outcome for the customer.
What to do instead
Use a three-part answer frame for every service scenario: technique named, exact words or action taken, and result for the customer or team. For example, instead of 'I would be polite', write 'I would paraphrase the customer's issue back to them to confirm understanding, then give a ticket number and a callback time'. Rehearse five scenarios: angry customer, non-technical user, remote team member, missed deadline, and a colleague who is not pulling their weight.
The candidate confuses hardware, software and operating-system layers-for example, describing a device driver as hardware, or an operating system as application software-and mislabels components in a troubleshooting sequence.
The syllabus introduces these categories separately and candidates memorise definitions in isolation without practising classification of real examples, so boundary cases (firmware, drivers, utilities, virtual machines) are guessed.
What to do instead
Create a three-column classification table (hardware, system software, application software) and sort 30 real items into it, including boundary cases: BIOS/UEFI firmware, device drivers, antivirus, disk defragmenter, hypervisor, word processor, and a web app. For each boundary item, write one sentence explaining why it belongs where it does. Re-test yourself weekly until sorting is error-free.
The candidate describes a troubleshooting process as a single step ('I would fix it' or 'I would restart the computer') instead of following a logical, documented sequence with verification and prevention.
Candidates remember the punchline of a fault (the fix) rather than the method, and exam questions that ask for 'the steps you would take' are marked on the process, not the final action.
What to do instead
Memorise and apply a six-step troubleshooting model to every scenario: gather information and question the user, identify and reproduce the problem, establish a theory of probable cause (starting with the simplest), test the theory, implement the solution and verify full functionality with the user, then document the outcome and any prevention step. Write out this sequence for five different faults (no network connection, printer offline, slow PC, forgotten password, malware alert) until it is automatic.
The candidate gives network and security answers that name a technology without explaining its purpose or the risk it addresses-for example, writing 'use a firewall' or 'use encryption' with no mention of what is being protected or from what.
Security terminology is memorable, so candidates list buzzwords and assume the marker will infer understanding. Marks are awarded for linking the control to the threat and the asset.
What to do instead
For every security control you mention, write a three-part sentence: asset protected, threat addressed, and mechanism. For example, 'A firewall protects the internal network from unauthorised external traffic by filtering packets against rules'. Build a table of ten controls (firewall, antivirus, MFA, encryption at rest, encryption in transit, backups, patching, least privilege, physical locks, acceptable-use policy) with this three-part sentence for each, and use the same structure in exam answers.
The candidate treats data and information as synonyms and cannot explain the data-to-information-to-knowledge progression, or fails to apply data-quality criteria (accuracy, completeness, timeliness, relevance, validity) to a scenario.
The distinction is taught early and assumed to be understood, so candidates skip revision of it and then lose marks on questions that ask them to evaluate whether a dataset is fit for purpose.
What to do instead
Practise with a concrete example: a list of raw scan codes (data), a sorted inventory report with counts (information), and a decision to reorder stock based on the report (knowledge). Then evaluate the same dataset against the five quality criteria, writing one sentence per criterion stating whether it is met and why. Apply this to three scenarios: a customer database, a network log, and a student records system.
The candidate answers legal and ethical questions with opinion ('it is wrong to copy software') instead of naming the specific law, obligation, or industry code and the consequence of breaching it.
Candidates rely on personal ethics and general knowledge, not the syllabus content on copyright, privacy, workplace surveillance, intellectual property, and acceptable use, so answers lack the named instrument and the consequence.
What to do instead
Build a legal-and-ethical reference card with five columns: issue, relevant law or code, obligation on the IT worker, consequence of breach, and a workplace example. Cover copyright and software licensing, privacy and personal information handling, workplace monitoring, intellectual property in code, and responsible use of AI tools. For each row, write a two-sentence scenario answer and check that it names the instrument and the consequence.
The candidate describes employability skills as a list of adjectives ('I am reliable, hardworking and a team player') without giving evidence of the skill in a workplace context or linking it to a career pathway.
Employability questions invite self-description, and candidates answer as they would in a job interview rather than in the evidence-based style the exam requires, where marks come from demonstrating the skill through a specific example.
What to do instead
Prepare a bank of eight STAR (situation, task, action, result) examples, one for each employability skill group: communication, teamwork, problem solving, initiative and enterprise, planning and organising, self-management, learning, and technology. Each example must be two to three sentences with a measurable result. Then map each example to at least one IT career pathway (help desk, network technician, web developer, cybersecurity analyst) so you can answer pathway questions with the same evidence.
The candidate misreads the command word in the question-answering 'describe' with a list, 'evaluate' with a description, or 'justify' with a statement of fact-and so loses marks despite knowing the content.
Under time pressure, candidates read for the topic noun and ignore the verb, and the syllabus uses a small set of command words with distinct mark expectations that are rarely drilled explicitly.
What to do instead
Before writing, circle the command word and write its required response shape in the margin: identify (name it), describe (say what it is and how it works), explain (give the mechanism and the why), compare (state similarities and differences), evaluate (weigh strengths and weaknesses and give a judgement), justify (give reasons for a position). Practise by taking ten past-style questions and writing only the first sentence of each answer, checking it matches the command word before completing the answer.