UPMSP High School IT & ITeS common mistakes
UPMSP High School IT & ITeS · Understand the traps and how to avoid them.
When asked to convert a binary number to decimal (or the reverse), the candidate flips the place-value order and reads the leftmost bit as 2^0 instead of the highest power, producing answers that are exactly reversed.
Candidates memorise the sequence 1, 2, 4, 8, 16 without anchoring it to positions, and under time pressure they write the weights left-to-right in the order they recall them rather than aligning the highest weight to the leftmost bit. The topic is usually practised only with 4-bit examples, so longer strings expose the confusion.
What to do instead
Always write the weights above the bits before computing: for an n-bit number, label the leftmost bit 2^(n-1) and step down to 2^0 on the right. Do five 8-bit conversions forwards and backwards daily, and verify by re-converting the answer back to the original base. Also memorise that an 8-bit group spans 0-255, which catches reversal instantly.
In a spreadsheet question the candidate types a formula such as =A1+B1*C1 and reports the arithmetic result without applying operator precedence, or copies a formula and assumes the cell references stay fixed.
Candidates treat spreadsheet formulas as ordinary left-to-right arithmetic and have not internalised that multiplication binds before addition. The relative-versus-absolute reference distinction is often learned as a definition ('dollar sign means fixed') without ever dragging a formula to observe what changes.
What to do instead
Before evaluating, bracket the expression mentally: =A1+(B1*C1). Practise on paper by writing the formula, marking which parts evaluate first, then substituting numbers. For references, build a small table where one formula uses A1 and a copy uses $A$1, fill it two columns right and two rows down, and record which cells each version points to. State the rule in your own words: no dollar sign moves, a dollar before the letter locks the column, a dollar before the number locks the row.
For a mail-merge or document-formatting task, the candidate describes the menu path vaguely ('go to the Mailings tab and click something') or lists steps out of order, so the answer cannot be followed as a procedure.
Practical work is often revised by reading screenshots rather than by performing the task, so the candidate recognises the feature but cannot reconstruct the sequence. Written exams reward ordered, named commands, and candidates underestimate how strictly step order is marked.
What to do instead
Rehearse each procedure aloud in numbered steps using exact ribbon and dialog names: create the main document, select recipients, insert merge fields, preview results, finish and merge. Write the sequence from memory three times, then actually perform it once on a small list of five fictional recipients. In the exam, answer procedural questions as a numbered list rather than a paragraph.
The candidate confuses the roles of a browser, a search engine, a website and an internet service provider, and answers 'the internet' or 'Google' for questions about who stores a web page or who assigns an IP address.
Everyday language blurs these terms because the browser's home page is usually a search engine. Candidates also conflate the World Wide Web with the internet itself, a distinction the syllabus tests directly.
What to do instead
Build a one-line definition for each layer: the internet is the global network of networks; the web is a service running on it; a browser is client software that requests and renders pages; a search engine is a website that indexes other pages; an ISP provides your connection and usually your IP address. Test yourself by assigning each of ten statements to exactly one layer, and be able to say where DNS resolution and web hosting sit.
On URL and email-address questions, the candidate mislabels the parts, for example calling 'www' the domain, treating '.org' as the server name, or placing the '@' symbol before the username.
The parts are learned as a single string to be recognised, not as labelled components. Candidates rarely see a URL decomposed, so they guess from position rather than from function.
What to do instead
Annotate five real URLs by hand, labelling protocol, subdomain, domain name, top-level domain, path and query string, and five email addresses labelling local part, @ symbol and domain. Learn the anchor facts: the top-level domain is the rightmost label, the domain is the label immediately left of it, and the local part always precedes the @. Then cover the labels and reconstruct them from a blank diagram.
The candidate defines BPO and ITeS only as 'outsourcing' and cannot distinguish front-office from back-office processes, or inbound from outbound voice work, when given a scenario such as handling a customer complaint versus processing payroll.
The terms are studied as glossary entries without scenario practice, so the candidate can recite a definition but cannot classify an unfamiliar example. The front/back and inbound/outbound axes are also easily mixed because both sound like 'customer contact'.
What to do instead
Learn two independent axes and apply both to every scenario: front office touches the customer directly (sales, support, complaint handling) while back office supports internally (payroll, accounting, data processing); inbound means the customer initiates contact while outbound means the organisation initiates it. Classify ten short scenarios into the correct cell of a two-by-two table and justify each placement in one sentence.
When asked to validate or clean a data-entry batch, the candidate accepts obviously wrong records, such as a date of 31 February, a pincode with five digits, or a phone number containing letters, instead of flagging them.
Candidates read records for meaning rather than checking each field against its rule, and they assume the source data must be correct. Validation types such as range, format, length and consistency checks are memorised as names but not applied.
What to do instead
For every dataset question, run a fixed checklist field by field: type, length, format, range, and consistency with a related field. Practise on a ten-row table seeded with three deliberate errors and state which validation rule each violates. Learn to name the rule when flagging: 'rejected because the date fails a range check' is a complete answer, whereas 'wrong date' is not.
In networking questions the candidate assigns two devices the same IP address, or puts devices on different subnets that are then expected to communicate directly, and cannot say what a default gateway or subnet mask does.
Addressing is taught as a list of numbers to copy rather than as a logical scheme. Candidates do not connect the subnet mask to the question 'is the destination on my network?', so they treat the gateway as optional decoration.
What to do instead
Work small addressing exercises: given a network address and mask, list the usable host range, the broadcast address and how many hosts fit. Then answer the routing question explicitly: compare the destination with the mask, and if it falls outside the local subnet, the packet goes to the default gateway. Draw a three-device LAN with a router and label every address, including the gateway on each side.
Faced with a troubleshooting scenario, the candidate jumps straight to a drastic fix such as reinstalling the operating system or replacing hardware, skipping basic checks like power, cabling, and whether the device is switched on.
Textbook fault lists are memorised as isolated causes, so the candidate pattern-matches to the most dramatic one. The discipline of a cheapest-first, most-likely-first sequence is rarely practised under exam conditions.
What to do instead
Adopt and always write out the same ordered routine: confirm power and physical connections, check the obvious indicators, reproduce the fault, isolate by swapping one component or cable at a time, then apply the fix and verify. For any scenario question, list at least two low-cost checks before any major action, and state how you would confirm the problem is resolved. Reinstalling software is an answer only after simpler causes are excluded.
On digital-safety and ethics questions the candidate gives a moral opinion ('it is bad to share passwords') instead of naming the specific threat, practice or safeguard, and cannot distinguish a virus, worm, Trojan and phishing message in a short scenario.
These topics invite everyday judgement, so candidates answer from common sense and skip the technical vocabulary. The malware categories overlap in casual speech, and the ethical and legal dimensions (consent, plagiarism, licensing) are treated as separate subjects rather than as named rules.
What to do instead
For each scenario, answer in three labelled parts: name the threat or issue precisely, state the mechanism or rule that makes it so, and give one concrete safeguard or correct action. Build a comparison table for virus, worm, Trojan, ransomware and phishing covering how each spreads and its tell-tale sign. For ethics, learn the named principles, such as informed consent, attribution, and licence compliance, and cite the relevant one by name in every answer.
In the viva or project section the candidate describes what the project does but cannot explain how a specific part works, why a particular tool or formula was chosen, or what they would change, and answers in one-word replies.
Projects are often completed by following a guide, so the candidate has output but no ownership of decisions. Viva practice is neglected because it feels like conversation rather than exam preparation, and candidates underestimate the marks attached to justification.
What to do instead
Prepare a one-page project brief covering aim, tools used, key steps, one problem encountered and its solution, and one improvement. For every formula, script or formatting choice in the project, write a single sentence beginning 'I used this because...'. Rehearse answering aloud in full sentences with a peer who asks 'why' three times in a row for each feature, and be ready to demonstrate one core operation live.