MATSEC SEC Information Technology common mistakes
MATSEC SEC Information Technology · Understand the traps and how to avoid them.
Writing a definition that only restates the term, e.g. 'a database is a base of data', instead of giving the concept plus an example.
Candidates memorise the keyword but never rehearse a full-sentence definition, so under time pressure they produce a tautology that earns no marks.
What to do instead
For every key term, prepare a one-sentence definition containing the concept, its purpose, and one concrete example (e.g. 'A database is an organised collection of related data stored so it can be queried, such as a school's pupil records'). Rehearse it aloud until it is automatic.
Confusing hardware and software components, for example naming RAM as 'software' or the operating system as 'hardware' in a classification question.
Revision is often done from lists without a mental model of the machine, so categories blur when the wording of the question changes.
What to do instead
Build a two-column table of components and sort each one by asking 'can I physically hold it and does it store or process data?'. Test yourself with shuffled cards until classification is instant.
Converting between binary, denary and hexadecimal by guessing or by copying a pattern, and showing no working.
Candidates learn one worked example and cannot generalise, and they skip writing place values so a single slip is invisible and unrecoverable.
What to do instead
Always write the place-value row (128 64 32 16 8 4 2 1) above the bits before converting. Practise ten conversions each way daily, and for hexadecimal group bits in fours from the right and pad with leading zeros.
Describing input, processing and output for a scenario in vague terms ('the computer processes the data') rather than naming the actual device and operation.
Candidates treat the scenario as a comprehension exercise and paraphrase the story instead of mapping it to system components.
What to do instead
For each scenario, write three labelled lines: Input (device and data), Processing (the specific operation, e.g. 'compare scanned barcode against stock file'), Output (device and result). Name real hardware every time.
Listing advantages of a technology without linking each one to the stated context, so generic points like 'it is faster' are given for a question about a specific business.
Mark schemes reward applied points, but candidates revise from generic lists and reproduce them unchanged.
What to do instead
After each advantage, add a 'because' clause naming the user or organisation (e.g. 'faster checkout because the cashier does not key prices, reducing queues at peak times'). Aim for two applied points rather than five generic ones.
Confusing validation with verification, or claiming a validation check prevents all incorrect data.
The two terms sound similar and are often revised together, so candidates merge them into one idea.
What to do instead
Memorise the distinction: validation checks data is reasonable and within rules (range, type, presence, length, format); verification checks data was copied or entered accurately (double entry, visual check, parity). Practise sorting examples into the two columns.
Answering a 'describe how' or 'explain' question with a single word or a list of nouns rather than a sequenced process.
Candidates read the command word as 'name' and run out of marks because each stage of the process needs its own point.
What to do instead
Underline the command word before writing. For 'describe how', number the steps in order (1, 2, 3) and give one action per step. Check the mark allocation and write roughly one distinct point per mark.
Ignoring units and magnitudes when discussing storage or data transfer, e.g. treating a megabyte and a gigabyte as interchangeable.
Candidates remember abbreviations but not the ordering or the factor of 1024, so comparisons and capacity calculations go wrong.
What to do instead
Write the ladder bit, byte, kilobyte, megabyte, gigabyte, terabyte with the multiplier (1024, or 1000 for transfer rates) and practise sizing real files, e.g. estimating how many photos fit on a 32 GB card.
Giving a security answer that names a method without saying what it protects against, e.g. 'use a firewall' with no further explanation.
Candidates list controls from memory but do not connect each control to a specific threat, which is what earns the explanation marks.
What to do instead
Use a two-part sentence for every control: the measure plus the threat it blocks (e.g. 'a firewall filters incoming traffic to block unauthorised access'). Prepare this pairing for firewall, encryption, strong passwords, backups and access rights.
Running out of time because the final long-answer question is left blank or half-written.
Candidates spend too long on early short questions and do not budget time against the total mark allocation.
What to do instead
Before starting, divide the minutes by the total marks to get minutes per mark, and note a checkpoint time for the halfway question. If a question stalls, leave a gap, move on, and return with the remaining time.