UPMSP Computer Technology and Maintenance common mistakes
UPMSP Computer Technology and Maintenance · Understand the traps and how to avoid them.
When converting between binary, octal, decimal and hexadecimal, candidates convert the integer part correctly but drop or misplace the fractional part, or they regroup bits for octal/hex from left to right instead of from the radix point outward.
Most practice is done on whole numbers, so the fractional conversion step (repeated multiplication by the base) is rarely rehearsed. Grouping errors happen because candidates memorize 'groups of three or four bits' without anchoring the grouping at the radix point.
What to do instead
Before every conversion, write the radix point explicitly and pad with zeros outward on both sides (e.g. 1011.101 -> 001 011 . 101 100 for octal). Practice ten conversions that include fractions with terminating and non-terminating results, and verify each by converting back to the original base.
Candidates answer questions about primary versus secondary storage, volatile versus non-volatile memory, and cache/RAM/ROM roles by matching brand names or capacity figures rather than by the functional definition, so they label ROM as volatile or confuse cache with virtual memory.
Everyday usage ('8 GB memory', 'SSD memory') blurs the technical distinctions, and candidates revise from spec sheets rather than from definitions of function and access.
What to do instead
Build a one-page table with rows for registers, cache, RAM, ROM, SSD/HDD and columns for volatility, typical access speed order, writability and role in the boot process. Answer each practice item by locating the device in that table before choosing an option.
When identifying a connector, port, cable or expansion slot, candidates choose the option that looks physically similar (e.g. HDMI vs DisplayPort, SATA vs eSATA, PCIe x1 vs x16, DDR4 vs DDR3 notch) instead of stating the distinguishing feature first.
Revision is often done from labelled diagrams without handling real hardware, so recognition is visual and shallow; exam items that describe a feature in words then defeat a purely picture-based memory.
What to do instead
For each interface, write three facts: pin/contact count or keying feature, typical device attached, and one transfer or power characteristic. Where possible, handle real cables and slots and describe them aloud using those three facts.
Candidates describe assembly or installation steps out of order, for example connecting power before confirming standoffs are fitted, installing the CPU after the heatsink, or applying thermal paste on top of the heatsink instead of the CPU heat spreader.
Steps are memorized as a list without the reason behind each one, so order is fragile under exam wording that starts mid-procedure or asks 'what should be done next'.
What to do instead
Learn the build as a sequence of safety gates: ESD precautions, standoffs and case preparation, CPU and cooler, RAM, storage, PSU and power routing, front-panel headers, then first boot and BIOS check. For each step, state in one sentence what damage or fault occurs if it is skipped.
On troubleshooting scenarios, candidates jump straight to a component replacement (usually the PSU or motherboard) without first establishing a symptom history, checking the obvious external causes, or applying a divide-and-conquer test.
Real-world habits and 'swap it out' instincts override the structured method examiners reward; candidates also confuse a POST failure with an operating-system boot failure.
What to do instead
Use a fixed answer template for every scenario: gather symptoms and recent changes, check external power and cabling, observe POST beep codes or LEDs, isolate by removing or substituting one variable at a time, then confirm the repair. Practice classifying each scenario as POST-stage, boot-stage or OS-stage before choosing an action.
Candidates treat preventive maintenance as only cleaning, omitting environmental controls, backup verification, update scheduling and documentation, and they recommend liquids or aggressive solvents for cleaning internal components.
Preventive maintenance is studied as a list of chores rather than as a risk-reduction programme, and cleaning products are chosen by household familiarity rather than by electrical safety.
What to do instead
Organize the topic into four pillars: physical (dust, temperature, humidity, ESD), logical (updates, defragmentation or TRIM, malware scans), data (backup schedule and restore test), and records (maintenance log). For cleaning, state the approved method and the hazard avoided, e.g. compressed air and anti-static brush, never liquid sprays inside the case.
Candidates mix up IP addressing fundamentals: they assign a gateway address inside the DHCP pool, apply the wrong subnet mask to a given address class or CIDR prefix, or confuse a MAC address with an IP address when explaining how a switch forwards frames.
Addressing is learned by memorizing default masks for classes A, B and C without practising prefix-to-mask conversion, and the OSI layer at which each device operates is not linked to the identifier it uses.
What to do instead
Drill prefix-to-mask conversion until /24, /25, /26 and /30 are instant, then practise placing host, gateway and broadcast addresses in a small subnet and justifying each. Write one line linking device to identifier: hub repeats bits, switch forwards by MAC, router forwards by IP.
Candidates describe backup and malware protection in vague terms, for example 'install antivirus and take backups', without distinguishing full, incremental and differential backups, the 3-2-1 rule, offline versus cloud copies, or the difference between a virus, worm, trojan and ransomware.
These topics attract generic answers that feel sufficient; candidates rarely rehearse restore scenarios or the infection vector of each malware type, so specific exam options look equally plausible.
What to do instead
For backups, learn the definitions plus one restore procedure for each type and the storage-count rule (three copies, two media, one offsite). For malware, make a table of type, self-replication, need for a host file, and typical delivery method, and add one concrete preventive control for each row.
In office application items, candidates select a feature by name similarity rather than by function, for example confusing absolute and relative cell references, COUNT versus COUNTA, or a section break versus a page break, and they forget that formulas must begin with the equals sign.
Menu-driven familiarity replaces understanding of what the feature does, and spreadsheet functions are remembered by name rather than by the type of data they accept.
What to do instead
For each function or feature, write the question it answers in plain words (COUNTA: how many non-empty cells; absolute reference: which part must not shift when copied) and predict the result of copying a formula before checking it in a spreadsheet.
On environmental safety and e-waste items, candidates dispose of batteries, toner cartridges and CRTs in general waste, or they answer workplace-safety questions by describing the fastest action rather than the safe sequence, such as handling a swollen battery or a PSU without isolation and PPE.
Local disposal practice and everyday convenience conflict with regulated handling, and safety procedures are studied as slogans without the order of steps or the reason for each control.
What to do instead
Learn the disposal route and the specific hazard for each waste stream: lead and phosphor in CRTs, lithium fire risk in batteries, toner inhalation risk, and precious-metal recovery for circuit boards. For incidents, memorize the sequence isolate, make safe, report, record, and state the PPE or control that applies at each step.