Putting a troubleshooting step out of order
The wrong answers pick a genuine step from the CompTIA troubleshooting methodology at the wrong point. Before the problem is identified, they offer a driver reinstall, a cable swap or a theory about the cause. Identifying the problem comes first: question the user and ask what changed. Then establish a theory of probable cause, test it, and plan and implement a fix. Documentation is the last step, so recording a cause before any work is done is out of order.
See it in a sample questionBlaming firmware for lost CMOS settings
The wrong answers blame firmware, the operating system, RAM or the motherboard when a PC loses its clock and boot order after being unplugged. A re-flash, an OS reinstall or a new board cannot make settings survive without power. The BIOS or UEFI image sits in non-volatile flash and needs no battery. The CR2032 coin cell powers the real-time clock and the volatile CMOS settings while the system is off, so a depleted cell causes exactly this reset.
See it in a sample questionMixing up thermal shutdown and power overload
The wrong answers treat a heat fault as a power fault, or the reverse. Raising core voltage, replacing the supply or switching off the thermal protection are offered for shutdowns that a logged thermal event, a CPU reaching its thermal limit, or a cooler disturbed by a move already explains. A shutdown under CPU load calls for reseating the heatsink and reapplying thermal paste. A reboot only under graphics load, with temperatures in range, points to a supply that cannot meet peak demand.
See it in a sample questionRepairing a failing drive instead of saving its data
The wrong answers treat a dying drive as a fault a utility or setting can repair. For a clicking mechanical drive or a rising reallocated-sector count, they offer chkdsk, defragmenting, repeated scans or disabling the S.M.A.R.T. alert. These leave the physical degradation in place, and defragmenting adds head movement to a failing mechanism. The correct answers protect the data first: back up or clone to a healthy drive and replace it, or for irreplaceable photos on a clicking drive, power it down and use a recovery service.
See it in a sample questionGiving one RAID level another's redundancy
The wrong answers lend one RAID level the recovery method of another. After a drive fails in RAID 0, they offer a parity rebuild or a mirror resync, but RAID 0 stripes data with no parity and no mirror, so the data returns only from a backup. The level descriptions are swapped the same way. A two-drive mirror is RAID 1, while RAID 5 needs a minimum of three drives and survives one failure through distributed parity.
See it in a sample question