Study guide · Core 1 · Domain 5 · 28% of the Core 1 exam
Hardware and Network Troubleshooting: the CompTIA A+ objectives in plain English
CompTIA A+ Core 1 (220-1201) Domain 5 is about fixing things in a clear order and knowing what a symptom is really telling you. It applies a formal method to motherboards, memory, processors, power, storage, displays, mobile devices, network services, connectivity, peripherals, and printers. At 28 percent of the Core 1 exam, this is the largest Core 1 domain, and it is also the domain that looks most like daily help desk work. Most questions give you a short story: a user, a device, and a symptom. Your job is to pick the next best step or matching fix.
What the objectives cover
5.1 Apply the best practice troubleshooting methodology
The methodology has six steps, and the exam expects them in order. Step one is identify the problem: gather information, question the user, identify symptoms, check logs and error messages, and ask what changed recently. Step two is establish a theory of probable cause: form the most likely explanation, question the obvious first, and consider more than one cause if the evidence points that way. Step three is test the theory to determine the cause: run the checks that prove or rule out the theory, and if it fails, form a new theory or escalate. Step four is establish a plan of action to resolve the problem and implement the solution: plan the fix, note its possible effects, get approval when other users are affected, and then carry it out. Step five is verify full system functionality and implement preventive measures if applicable: test the whole system, have the user confirm the result, and add steps that stop the problem from returning. Step six is document findings, actions, and outcomes: record what you found, what you did, and how it ended.
5.2 Troubleshoot motherboards, RAM, CPUs, and power
POST, the power on self test, checks core hardware before the operating system loads, and beep codes can point to the failing part when there is no display. No display with fans spinning often means a display, memory, or video problem, so reseat RAM and check the monitor cable and input before you replace a board. Random crashes can point to faulty or poorly seated memory, and a memory test helps separate bad RAM from a software fault. Overheating shows up as slowdowns, loud fans, and shutdowns under load. Check blocked vents, dust, failed fans, and a heat sink that is not seated flat. Intermittent shutdowns with no error also raise power questions: a failing PSU, a loose connector, or a swollen capacitor on the motherboard can cut power without warning. Swollen or leaking capacitors and a burning smell are stop and replace signs. Always rule out the simple power path first, outlet, strip, and cable, because a dead system is often a power problem rather than a dead board.
5.3 Troubleshoot storage drives and RAID arrays
Storage symptoms usually warn you before a drive fails completely. Clicking or grinding from a hard drive points to mechanical failure, and the right move is to protect the data and plan replacement rather than running tool after tool on it. Slow reads, freezes, and corrupted files can also signal a failing disk. S.M.A.R.T. is the monitoring system built into drives that reports health indicators, so a S.M.A.R.T. warning means back up now and replace soon, even if the drive still boots today. Boot device errors, such as no bootable device found, can come from a dead drive, a loose cable, or the wrong boot order in firmware, so check cables and boot order first. RAID adds shared rules. RAID 0 stripes data with no redundancy, so one failed drive loses the array. RAID 1 mirrors data, so one drive can fail and the system keeps running until you replace and rebuild the mirror. RAID 5 uses striping with parity and tolerates one failed drive, but performance drops during a rebuild and a second failure in that window loses data. RAID 10 combines mirroring and striping, tolerates at least one failure per mirrored pair, and usually rebuilds faster, at the cost of half the capacity.
5.4 Troubleshoot video, projector, and display issues
Display work starts by separating no signal from a bad picture. No signal means check power, cable seating, and the correct input source, because a monitor on the wrong input looks like a dead monitor. If a known good cable fixes it, you have isolated the fault. A dim image has different causes by device. On a laptop, a very dim screen where a faint image is still visible can point to backlight failure, but check brightness settings and power plans first. On a projector, dim output often means an aging lamp near the end of its lamp life, and lamp hours give you evidence instead of a guess. Flicker can come from a loose cable or a failing backlight. A blurry or stretched picture is often a resolution mismatch: displays look sharpest at their native resolution, so set the output to that value before you blame the panel. Swap one variable at a time until the fault follows one part.
5.5 Troubleshoot common mobile device issues
Mobile troubleshooting starts with safety and power. A swollen battery is a safety issue: the case may bulge or the screen may lift, and the correct response is to stop using and charging the device and replace the battery through proper service channels, never to press it flat or puncture it. For charging problems, work from the wall outward: try a known good outlet, cable, and charger with the right wattage, and check the port for lint. Note whether it charges slowly, only at one angle, or not at all, because each pattern points to a different part. A frozen screen calls for the maker specific force restart steps, after you check whether the freeze follows one app or happens everywhere. If one app crashes or drains the battery, update it, clear its cache where the system allows it, or remove and reinstall it. If every app struggles, look at nearly full storage or overheating. For touch problems, remove the case and screen protector as a test before you assume the digitizer has failed.
5.6 Troubleshoot common network services issues
Network services questions test whether you can tell DNS and DHCP apart by their symptoms. DHCP hands out IP addresses, subnet masks, gateways, and DNS settings automatically. When DHCP fails, a client often gives itself an APIPA address in the 169.254 range, which means it cannot reach the gateway or the internet. Scope exhaustion is a specific DHCP failure: the pool is full, so new clients cannot get a lease until addresses are freed or the scope is expanded. DNS is different. DNS turns names into IP addresses, so a DNS failure looks like this: the device has a valid address and can reach sites by IP address, but names fail. An unreachable gateway is a third pattern: the client has a valid address and local devices may respond, but nothing beyond the local network answers, which points to the gateway or the router. Test in order: confirm the address, ping the gateway, ping an outside address by number, then test a name.
5.7 Troubleshoot common network connectivity and peripheral issues, including printers
Limited connectivity means the device is connected to something but cannot pass useful traffic, so read the address first. An APIPA address points back to DHCP, a missing gateway blocks outside access, and a good address with no traffic points to the cable, switch port, wireless signal, or authentication. For wired links, check link lights and try a known good cable. For wireless, check signal strength and the correct network name, and note whether other devices fail too, because one device failing is a device problem and every device failing is a network problem. Printers combine connectivity, drivers, and mechanics in one ticket. Paper jams need the maker path followed in order: open the listed access points and pull paper in the direction of travel so you do not tear it and leave scraps behind. If jobs sit in the queue and nothing prints, restart the print spooler service, clear a stuck job, and confirm the printer is not paused or set offline. Garbled output, strange characters, or wrong formatting almost always point to the driver: install the correct model specific driver rather than a generic one, and retest with a simple page. Driver version belongs in your notes for every printer fix.
Worked example
A user reports that a workstation will not print and provides only a brief description of the problem. According to the CompTIA troubleshooting methodology, what should a technician do FIRST?
Identifying the problem is the first step. The technician gathers information, questions the user, identifies symptoms, and checks for recent changes before forming a theory.
Why the other options are wrong
- BEstablish a theory of probable cause based on external research: Establishing a theory comes after the problem has been identified and information has been gathered.
- CTest a theory to determine the cause: Testing a theory comes after a theory of probable cause has been established.
- DDocument findings, actions, and outcomes in the ticket: Documenting findings is the final step, after the solution has been implemented and verified.
Acronyms and terms in this domain
| Term | What it means |
|---|---|
| POST | Power On Self Test, the hardware checks a computer runs at startup before the operating system loads |
| S.M.A.R.T. | Self Monitoring, Analysis, and Reporting Technology, drive health monitoring that warns of likely failure |
| RAID | Redundant Array of Independent Disks, combining drives for speed, redundancy, or both |
| APIPA | Automatic Private IP Addressing, the 169.254 address a device gives itself when DHCP does not answer |
| BSOD | Blue Screen of Death, a Windows stop error screen shown after a serious system failure |
| PSU | Power Supply Unit, the component that converts wall power into the voltages a computer uses |
| ESD | Electrostatic Discharge, static electricity that can damage components during handling and repair |
| DHCP | Dynamic Host Configuration Protocol, the service that assigns IP addresses and network settings automatically |
| DNS | Domain Name System, the service that translates domain names into IP addresses |
| Spooler | Print Spooler, the service that holds print jobs in a queue and sends them to the printer in order |
Where the help desk meets this domain
This domain is your shift, written as exam objectives. The morning queue is full of it: a workstation that will not boot after a desk move, a monitor that went dark after cleaning, a printer that prints symbols instead of words, and a laptop that only works when it is plugged in. Each ticket rewards the same habit: ask what changed and write down what you see before you touch a setting. A brief report such as it will not print can mean no power, no network, or a stuck queue, and each cause has a different fix. A clear theory, a tested fix, and a verified result are also easier to explain than parts swapped on hope.
You also meet the services side of this domain every time someone says the internet is down. That phrase can mean DHCP ran out of addresses, DNS is failing while the connection is fine, or one laptop has an old static gateway. The address on the device tells the story faster than any speed test. An APIPA address sends you to DHCP, a good address with name failures sends you to DNS, and a good address with a silent gateway sends you to the local network path. Most printer calls are not a broken printer: they are a jam, a spooler stopped by one bad document, or a driver replaced by an update.
Traps to watch for
Methodology questions are order traps, built to punish skipping ahead. If the stem says the technician has only a brief report, the answer is almost never a theory, a test, or a repair: it is to identify the problem first by gathering information and questioning the user. If a theory has been tested and disproved, the next step is a new theory or escalation, not a plan of action. If the fix worked, look for verify full system functionality before documentation, because documentation is always last. Learn the six steps as a sentence you can say without pausing, match the stem to the last step the story has completed, and pick the next step.
RAID questions are capacity and rebuild traps. RAID 0 sounds safe because it uses several drives, but it has no redundancy at all, so one failure loses everything. RAID 5 rebuilds are slow, stress the remaining drives, and leave the array exposed: a second failure during the rebuild loses the data. RAID 10 costs half the capacity to mirroring, which tempts test takers to call it wasteful, but it rebuilds by copying a mirror, so it is usually faster and safer during recovery than a parity rebuild. Watch drive counts too: RAID 5 needs at least three drives, while RAID 10 needs at least four and loses half the capacity.
Now try it. The 3 free sample questions for this domain are in practice mode, with full explanations.
Practice Domain 5 questions