HSC Enterprise Computing exam 2026Exam: Thu 29 Oct · NESA timetable
Your HSC Enterprise Computing exam:
When and how long
- Enterprise Computing9.50 am to 12.20 pm2 h 30 min in total, including reading time
NESA: the exam start time shown on your timetable is when reading time begins, and you must arrive well before it. Finishing times marked approximate are shown as approx.
Source: 2026 HSC written exam timetable (NESA), checked Wednesday 23 September 2026. Where a start time, reading time or duration isn't shown, the timetable doesn't publish it: check your personal timetable and the front of your paper.
Paper format
Higher School Certificate Examination - Enterprise Computing: 80 marks, 2 h 20 min writing time plus 10 minutes reading time.
- Objective response20 marks
- Short answer60 marks
NESA HSC exam specification for Enterprise Computing 11-12 (2022): an online exam of 2 hours 30 minutes including 10 minutes reading time, 80 marks, sat on a computer. About 20 marks of objective-response items (14 to 18 items, each worth 1 to 4 marks) and about 60 marks of short-answer items (16 to 18 items, at least three worth 4 to 8 marks). This desk mock uses 1-mark multiple choice for the objective items and, as the course has no bank of past questions yet, fills the short-answer section with our original dot-point practice questions. The time split per section is our suggestion.
From the official specification: source.
What the exam covers
We don't have past-paper frequency data for this exam, so here is the course, module by module. Make sure every module is covered.
Night-before and exam-morning checklists
The night before
- Check your personalised timetable on Students Online: the start time shown is when reading time begins.[2]
- Confirm your venue and the start time.[1]
- Pack a clear bag: several black pens (no erasable ink), 2B pencils, sharpener, eraser and a ruler.[1]
- Pack an approved calculator (check NESA's list) and a compass or protractor if the exam needs them.[1]
- Fill a clear, label-free water bottle.[1]
- A plain watch only if you want one (no smart or programmable watch); it goes on the desk.[1]
- Stop revising around 7 to 8 pm, set two alarms and sleep.[1]
Exam morning
- Eat a real breakfast.[1]
- Arrive well before the start time to allow for seating and checks.[2]
- Leave your phone and other electronic devices outside the exam room.[1]
- Use the bathroom before you go in.[1]
- In reading time, read and plan only: no writing, marking or annotating.[1]
- You can't leave in the first hour or the last 15 minutes.[1]
Exam-week survival kit: The last 7 days · The night before and exam morning · What to bring, and what's banned · How to use reading time · If you're sick or something goes wrong · Handling exam-week stress.
Last-week revision
- Timed mock examHigher School Certificate Examination - Enterprise Computing
- FlashcardsSpaced-repetition cards from the syllabus pages
- QuizData Science: HSC Enterprise Computing objective-response practice
- QuizData Visualisation and the Enterprise Project: HSC Enterprise Computing objective-response practice
- QuizIntelligent Systems: HSC Enterprise Computing objective-response practice
- Study guides3 guides
HSC Enterprise Computing cram sheet
Key formulas, definitions and facts copied from our Enterprise Computing syllabus pages. One page when printed.
Data Science
Tampering with an old block changes its hash, breaking the link to every later block, and the altered copy disagrees with all the other copies. Blockchain makes records tamper-evident and gives a trusted shared history without a single central authority.
Nominal: named categories with no order (payment method, suburb). Valid: counts, mode.
Relevance: does it answer this question, for this population and time?
- Legal: required by law (privacy law, copyright law).
- Ethical: what is right, even if legal (not exploiting vulnerable users).
- Social: effects on communities and society (loss of trust, discrimination, cultural harm).
Many issues are all three. Say which aspect you are discussing.
Data Visualisation
Simplifying understanding: people read shapes, colours and positions faster than rows of numbers.
Roll-up: aggregate to a higher level (month to year).
Accuracy: do the values and the visual impression match reality? A correct number can still be shown misleadingly.
Data backup
- Regular automated backups (full, incremental or differential).
- The 3-2-1 rule: three copies, two media, one off-site.
- Version history to recover from mistakes or ransomware.
- Regular restore testing.
Enterprise Project
- Verification: "Did we build the system right?" Does it meet the specification and work correctly (tests pass, calculations correct)?
- Validation: "Did we build the right system?" Does it meet the client's and users' real needs in their environment?
Ask: How clear and stable are the requirements? How big and complex is the system? What skills, time and budget are available? How involved can users be? What are the risks if it fails?
Direct (cut-over): switch completely on a set date. Cheapest and fastest; highest risk.
Intelligent Systems
Is it fair? Is it transparent and explainable? Who is accountable? Is privacy protected? Is it safe and reliable? Does it benefit the people it affects?
Structured (automated decisions): routine, repetitive, clear rules and complete information. The system can decide automatically (reorder stock at the reorder point, calculate pay, approve a small refund).
Truth maintenance: records the justification for each belief so that when a fact changes, dependent conclusions are withdrawn or revised. Keeps knowledge consistent over time.
Benefits: security, crime and fraud prevention, safety, efficiency and personalised services.
Concerns: privacy, consent, accuracy and bias (misidentification), function creep, data breaches, chilling effects on behaviour and freedom of expression.