Placing a methodology step out of order
The wrong answers pick a genuine step of the methodology that belongs at a different point. After a theory is formed they jump to planning or implementing, after a confirmed theory they jump to verification, and after a fix they jump to documentation. Once a theory of probable cause is established, the order runs: test the theory, establish a plan of action, implement the solution, verify full system functionality, then document findings. Testing comes before planning, and documentation is last.
See it in a sample questionAssuming a forced port still negotiates
The wrong answers treat a hardcoded port as if it still negotiates, or assume forcing one end settles the link. A port with autonegotiation disabled advertises nothing, so a neighbour left on auto uses parallel detection, which recovers speed but not duplex, and falls back to half duplex. Two ends forced to different speeds bring up no link at all. Gigabit expects negotiation, so forcing one end leaves the other unable to agree. Matching fixed settings, or leaving both ends on autonegotiation, avoids the mismatch.
See it in a sample questionSwapping one cable fault for another
The wrong answers name a different cable fault from the one the tester reports. An open shows a conductor with no continuity, and a cable tester can give a distance to fault along the run. A short reports two pins joined, typically strands touching inside a plug. A split pair keeps every pin continuous and correctly numbered while one signal pair is no longer carried over a single twist. A crossed or transposed pair shows swapped pin numbers on the wiremap.
See it in a sample questionMisreading a 169.254 address
The wrong answers read a 169.254 address as something it is not: a static assignment, an RFC 1918 private address, or a routable address made usable by a wide mask. The 169.254.0.0/16 range is APIPA link-local space under RFC 3927. A host assigns it to itself when no DHCP server answers, and it comes with no default gateway. It reaches only other hosts on the same link that also self-assigned.
See it in a sample questionWidening channels or raising power to fix wireless
The wrong answers try to gain range or capacity by widening channels or adding transmit power. A 40 MHz channel spans two of the three non-overlapping 2.4 GHz channels, so 20 MHz keeps the 1, 6, and 11 plan. A weak client at a distant corner needs a closer access point, not a wider channel. In a crowded room with healthy signal, more power adds no capacity; more access points at lower power divide clients across more channels.
See it in a sample question