CCSLC Digital Literacy common mistakes
CCSLC Digital Literacy · Understand the traps and how to avoid them.
Treating 'digital literacy' as synonym for 'knowing how to use a computer' and answering skills questions from general intuition instead of the stated definition of the term in the syllabus.
Candidates often study from generic internet-safety advice rather than the specific competency framework, so they answer what feels sensible rather than what the exam's definition requires.
What to do instead
Before answering, recall the exam's own breakdown of digital literacy (e.g. technical operation, information management, communication, safety, problem-solving) and map each question to one of those strands. Where a question asks 'what does X mean', answer from the definition in the specification, not from everyday usage.
Confusing hardware with software, or input with output devices, when classifying items such as a touchscreen, a scanner, a printer, or firmware.
Everyday language blurs these categories ('the computer did it'), and peripherals that both accept and deliver data (touchscreens, multifunction printers) are genuinely ambiguous unless the candidate applies the direction-of-data rule.
What to do instead
Apply the rule: an input device sends data into the system, an output device delivers data out, and a device that does both is described as such. Learn firmware as software embedded in hardware. Practise sorting a list of 20 devices into input, output, storage and processing before the exam.
Answering file-management questions with the wrong operation - saving instead of Save As, copying instead of moving, or deleting instead of cutting - because the candidate reads the goal rather than the exact verb in the question.
These commands feel interchangeable in casual use, and candidates skim the stem looking for the outcome ('the file ends up in the new folder') instead of the method named.
What to do instead
Underline the verb in the question before choosing. Memorise the pairs: copy leaves the original, move does not; Save overwrites the current file, Save As creates a new one; delete removes without placing on the clipboard, cut places it there. Write the distinction out once in your own words.
Mixing up the parts of a web address and a search engine - calling the domain the 'search term', or claiming a URL beginning https is automatically trustworthy.
Candidates learn 'https is safe' as a slogan and then over-apply it, and many have never had to parse a URL into protocol, domain and path.
What to do instead
Learn to read a URL left to right: protocol, subdomain, registered domain, top-level domain, path. State explicitly that https encrypts the connection but says nothing about the honesty of the site. When asked to evaluate a source, comment on author, date, purpose and cross-checking, not on the padlock alone.
Choosing the strongest-sounding password rule ('must contain a symbol') over the more effective one (length and uniqueness), or describing two-factor authentication as 'a longer password'.
Legacy advice about complex passwords is widely repeated, and candidates have not been taught that length and non-reuse defeat guessing and credential-stuffing better than symbol requirements.
What to do instead
Anchor on the principle: length plus uniqueness beats complexity. Describe two-factor authentication as a second, different type of evidence (something you have or are), not a second password. When a question offers both options, pick the one that addresses the actual threat named in the stem.
Treating phishing as only 'an email from a stranger asking for money' and failing to recognise smishing, vishing, clone websites, or a genuine-looking message from a known contact whose account was compromised.
Textbook examples are dated and simplistic, so candidates pattern-match on obvious cues and miss questions where the channel or the apparent sender is different.
What to do instead
Learn phishing by channel (email, SMS, phone, social media, fake login pages) and by cue (urgency, mismatched link, unexpected attachment, request for credentials or payment change). For each scenario question, name the channel and the cue before choosing the response, and remember the safe response is to verify through an independent channel, not to reply.
Answering copyright and plagiarism questions by personal opinion ('it's fine if I'm not selling it', 'I changed some words') rather than by the rules of attribution and permission.
Candidates rely on common practice among peers, where unattributed reuse is normal, and have not separated legal permission from academic honesty.
What to do instead
Learn the two separate questions: do I have permission or a licence to use this (copyright), and have I credited it honestly (plagiarism)? Paraphrasing without citation is still plagiarism. Learn what public domain, Creative Commons and fair-use/fair-dealing exceptions typically permit, and state the attribution requirement whenever an image, dataset or quotation is reused.
Giving vague answers to 'digital footprint' and 'netiquette' questions - saying 'be careful online' instead of naming concrete behaviours such as privacy settings, tagged content, permanence of posts, and audience awareness.
These topics sound like moral advice, so candidates produce reassurance rather than specifics, and they underestimate how much of their grade depends on naming mechanisms.
What to do instead
Prepare three concrete examples for each: for footprint, search results, cached copies and third-party tags; for netiquette, tone without nonverbal cues, all-caps as shouting, reply-all misuse, and the permanence of screenshots. Answer with the mechanism plus the consequence, not the slogan.
Describing a spreadsheet or word-processor task in general terms ('use a formula') instead of naming the actual function, cell reference or menu path the question asks for.
Candidates know the software visually but not the vocabulary, so they cannot produce the precise term the mark scheme expects even when they could perform the task.
What to do instead
Build a vocabulary list per application: cell reference, absolute versus relative reference, SUM/AVERAGE/COUNT, sort versus filter, wrap text, merge cells, header row. Practise describing a task aloud using only the correct terms, with no pointing at the screen.
Leaving multi-part scenario questions partly answered - giving the risk but not the prevention, or the action but not the reason - so marks are lost on the second half of each stem.
Candidates write the first thing that comes to mind and move on, and scenario stems often contain two or three implicit instructions ('identify', 'explain why', 'state one measure') that are easy to miss under time pressure.
What to do instead
Before writing, count the instruction verbs in the stem and number your answer points to match. Allocate roughly one minute per mark and reserve the last few minutes to check that every 'explain' has a because-clause and every 'state one measure' has a measure.