The $ Block: Where the Marks Really Hide
In HKDSE ICT, candidates consistently throw away easy marks on spreadsheet formula questions in Paper 1 Section B. The biggest culprit? Failing to apply absolute referencing ($). When a question asks you to write a formula in a cell (e.g., cell B2) that will be replicated down to a range (e.g., B3:B8), you must identify which cell addresses must remain anchored. If you are referencing a lookup table like A2:B5, writing it without dollar signs will cause auto-fill execution errors as the range shifts downward. Always write $A$2:$B$5. Top scorers double-check every coordinate before moving to the next question.
Stop Saying 'It is Faster' - The Precision Trap
Examiners consistently penalize superficial answers. Writing generic terms like 'it is faster' or 'more secure' without technical justification will yield zero marks. You must explain the underlying technical cause:
- Instead of 'it is faster', write: 'it has a higher network bandwidth', 'shorter computational cycle', or 'lower data transfer latency'.
- Instead of 'RAM is faster than SSD', clearly isolate the logical states: 'RAM is volatile whereas SSD is non-volatile' and 'RAM has a higher data transfer rate than SSD'.
- Instead of 'it is more secure', explain: 'the data is encrypted using an SSL/TLS key' or 'it uses a firewall to filter unauthorised packet transmission based on security rules'.
The SQL Survival Guide: Group By or Drop Out
For elective Paper 2A (Databases), SQL syntax is the ultimate make-or-break topic. A common pitfall is omitting the GROUP BY clause. If your SELECT statement includes both a raw attribute and an aggregate function (such as AVG(MARK) or SUM(SMARK)), you must group by the non-aggregated attribute. Furthermore, candidates frequently forget to define relational JOIN criteria in their WHERE clause when querying multiple tables, or confuse DROP TABLE (which destroys the database schema structure completely) with DELETE FROM (which only clears table records while keeping the structure intact). Ensure your constraints, such as PRIMARY KEY and NOT NULL, are explicitly declared when completing DDL tasks.
Dry-Running Pseudo-Code: Defeating the Off-by-One Beast
Algorithm questions in both Papers require you to trace or complete pseudo-code. Many candidates fail due to invalid array index syntax (such as using parentheses A(i) instead of standard brackets A[i]) or off-by-one errors in loop boundaries. To avoid this, always perform a quick dry-run with a minimal dataset (e.g., an array of size 3). Trace the loop variables at the start, middle, and termination boundaries to verify that your exit conditions (such as Until X = 0 or While i <= N) execute exactly the intended number of times.
The 5-Minute Habit: Active Retrieval of Misconceptions
Before entering the exam hall, spend 5 minutes reviewing key theoretical boundaries. Remember: 5GHz Wi-Fi signals offer higher speed but lower physical wall penetration power than 2.4GHz due to higher frequency; CAPTCHA's primary role is distinguishing automated bots from humans, not encrypting data; and open-source software is defined by access to its source code for modification, which is not the same as freeware.