Study guide · Core 1 · Domain 1 · 13% of the Core 1 exam
Mobile Devices: the CompTIA A+ objectives in plain English
Domain 1 opens CompTIA A+ Core 1 (220-1201) with the phones, tablets, and laptops that users carry everywhere. It covers what lives inside those devices, how to connect accessories and networks, how to set up mail and managed applications, and how to work through the faults users report most often. At 13 percent of the Core 1 exam, it is not the largest domain, but it is one of the most practical, because almost every topic maps to a real ticket: a battery that will not hold a charge, a screen that will not respond, a headset that will not pair, or mail that stopped syncing. The exam expects you to know the parts, the settings, and the safe order of steps, and to choose the action a careful technician would take first in a real workplace.
What the objectives cover
1.1 Monitor and maintain internal mobile device components
Most mobile devices are sealed units, so maintenance starts with knowing what is inside, what its normal behavior looks like, and which parts a technician can service and which parts require a replacement device or a manufacturer repair. Batteries are the most safety critical component. Most phones and tablets use lithium ion cells that lose capacity over time, charge more slowly, and may swell when damaged or worn. A bulging case, a lifting screen, or a device that rocks on a flat surface points to a swollen battery, and that device should stop being used and charged until the battery is replaced under proper safety guidance. Cameras include front and rear modules with lenses that can crack, fog, or fail, and a camera that shows a black image in every application usually has a hardware fault rather than a software setting. Wi-Fi antennas are small internal parts, often placed near the edges of the case, and a drop can loosen or damage them, which shows up as weak signal right next to a working access point. Displays combine the visible screen with a touch layer, so a cracked panel, dead spots, flicker, or no image with sound present each point to different faults, and brightness and auto rotate settings should be checked before the panel is condemned. Storage on most mobile devices is fixed internal flash memory rather than a removable drive, so monitoring free space matters, because a nearly full device slows down, fails updates, and stops saving photos, and some devices add removable cards that can be checked, formatted, or replaced.
1.2 Configure accessories and connectivity options
Accessories extend a mobile device, and this objective covers how each connection type works and where its settings live. USB connections charge the device and move data, and the connector type, the cable quality, and the port condition all matter, because a cable that charges but never offers a data connection may be a charge only cable or a damaged port with lint or bent contacts. When a device is connected to a computer, the user may also need to choose a transfer mode on the device itself before files appear. Bluetooth pairs short range accessories such as headsets, keyboards, mice, speakers, and vehicle systems, and pairing means putting the accessory into pairing mode, selecting it on the device, and confirming a code when one is shown. NFC, or near field communication, works only at very short range and supports tap based actions such as contactless payment, quick pairing, and reading tags. Docking stations connect a phone, tablet, or laptop to external displays, wired networking, and desktop peripherals through one connection, which makes them common at shared desks. A mobile hotspot turns a phone into a small wireless access point that shares its cellular data with nearby devices, with its own network name, password, and data limits. Wearables such as smartwatches and fitness trackers pair over Bluetooth, rely on a companion application on the phone, and need charging, permissions, and software updates of their own.
1.3 Configure network connectivity and application support
A mobile device is only useful when it connects, and this objective covers the three main paths and the application support that runs on top of them. Wi-Fi setup means selecting the correct network, entering credentials accurately, and confirming that the device received a valid address, and forgetting and rejoining a network clears saved settings that no longer match. Bluetooth connectivity supports accessories and file sharing, and it can be toggled, unpaired, and paired again to clear a bad pairing record. Cellular data connects through the carrier, depends on signal, the SIM or eSIM profile, and the account plan, and settings such as data roaming and data limits change behavior when a user travels or nears a cap. Email setup requires the account type, server names, ports, and encryption expected by the provider, and modern accounts often add multifactor prompts during setup, so a correct password can still fail if a step is skipped. Synchronization keeps mail, contacts, calendars, and files consistent across devices through the account, and sync settings control what is included and how often it updates. Mobile device management, often shortened to MDM, lets an organization enroll devices, push settings and applications, require a passcode and encryption, and locate or wipe a lost device, so a managed device behaves differently from a personal one and some settings are controlled by policy rather than by the user.
1.4 Troubleshoot common mobile device issues
Troubleshooting in this domain follows the same discipline as any other support work: identify the symptom clearly, check the simple and safe causes first, change one thing at a time, and verify the fix with the user. Hardware problems include a device that will not power on, a battery that drains quickly or will not charge, an unresponsive or cracked touchscreen, overheating, and physical damage from drops or liquid. Start with the charger, cable, and outlet, check for case or port obstruction, and look for swelling or damage before assuming a board level fault. Connectivity problems include no service, weak Wi-Fi, dropped Bluetooth accessories, and data that works on one network but not another. Toggling airplane mode, restarting the device, forgetting and rejoining a network, and checking account and signal status resolve many of these without deeper work. Application problems include applications that crash, freeze, run slowly, fail to install, or stop syncing. Checking available storage, updating the application and the operating system, clearing cached data where the platform allows it, and removing and reinstalling the application are standard steps, in that general order. Throughout, protect user data first: confirm what is backed up before a reset, explain what a step will erase, and treat any sign of battery damage as a safety issue that stops normal troubleshooting.
Worked example
A user reports that a tablet case is bulging and the back panel is lifting on one side. The device still powers on. What should the technician do first?
A bulging case is a classic sign of a swollen lithium battery. The safe response is to stop using and charging the device and replace the battery following manufacturer and safety guidance, because a damaged battery can overheat or catch fire.
Why the other options are wrong
- BCharging overnight: Charging a swollen battery adds heat and stress and increases the risk of failure, so it makes the problem worse.
- CPressing the panel down: Forcing the panel down can puncture or further damage the swollen cell and does not fix the underlying fault.
- DDraining the battery: Draining the battery does not reverse swelling, and continued use while it drains keeps a hazardous device in service.
Acronyms and terms in this domain
| Term | What it means |
|---|---|
| NFC | Near Field Communication, a very short range wireless link used for tap payments, pairing, and reading tags |
| MDM | Mobile Device Management, software that enrolls devices and controls settings, applications, and security policy |
| IMEI | International Mobile Equipment Identity, a unique identifier assigned to a mobile device on cellular networks |
| eSIM | Embedded SIM, a built in programmable SIM profile that replaces a removable carrier SIM card |
| OTA | Over the Air, delivery of software updates and settings to a device over a wireless connection |
| GPS | Global Positioning System, satellite based location used by maps, directions, and location services |
| LCD | Liquid Crystal Display, a screen type that uses a backlight behind the liquid crystal layer |
| OLED | Organic Light Emitting Diode, a screen type where each pixel makes its own light without a backlight |
| Li-ion | Lithium Ion, the rechargeable battery chemistry used in most phones, tablets, and laptops |
| Tethering | Sharing a phone cellular data connection with another device, by hotspot, USB, or Bluetooth |
Where the help desk meets this domain
You already do this work, even if your tickets use plain words instead of objective numbers. When a user says their phone battery barely lasts the morning, you check battery health, look for an application using unusual power, and talk about replacement when the cell is worn or swollen. When a new hire cannot get mail on their phone, you walk through account setup, confirm the server and security prompts, and check whether the device is enrolled in management, because a missing enrollment or a policy that requires a stronger passcode will block mail in ways a password reset cannot fix. When a headset will not pair with a laptop or a watch stops syncing with a phone, you clear old pairings, put the accessory back into pairing mode, and rebuild the connection step by step. Those are objectives 1.1, 1.2, and 1.3 in daily form, and the exam simply asks you to name the parts and pick the safest, most methodical next step.
The troubleshooting objective is the help desk job itself. A cracked screen with a working display is a different ticket from a black screen with sound, and a device that will not charge on one cable but charges on another points at the cable or port, not the battery. Good notes matter here: recording the symptom, the charger and cable tested, the network the user was on, and the exact error an application showed lets the next technician continue instead of starting over. Safety and data protection run through all of it. You stop and escalate when a battery is swollen, you check backup status before suggesting a reset, and you explain data loss in plain language before you erase anything. Users remember that care more than speed, and the exam rewards the same judgment, because many questions are really asking whether you protected the user, the device, and the data before reaching for a more drastic fix.
Traps to watch for
The most common trap in this domain is a choice that fixes the symptom while ignoring a safety problem. A swollen battery is the clearest example: charging it longer, pressing the case back down, or draining it flat all sound like actions, but each one keeps a damaged battery in use or makes the damage worse. The correct answer stops use, removes power, and follows manufacturer and safety guidance for replacement. The same pattern appears with liquid damage, overheating, and burning smells, where the right first step is to power down and stop, not to keep testing. A second trap is skipping the simple checks. Exam stems often include a small clue, such as a new case blocking a port, a charge only cable, airplane mode left on, or a device connected to the wrong wireless network with a similar name. Choices that jump straight to a factory reset, a board repair, or a replacement device are usually wrong when a cable swap, a setting, or a rejoin has not been tried yet.
Connectivity and account wording creates another set of traps, because similar symptoms have different owners. Mail that fails on one managed phone while coworkers work fine points to that device enrollment, account setup, or policy status, not to the mail server. Data that stops after travel may be a roaming setting or a plan limit, not a broken radio. Bluetooth problems are often pairing records, not failed hardware, so removing the pairing and pairing again is a standard early step, while Wi-Fi problems after a password change usually mean the saved network needs to be forgotten and rejoined with the new credentials. Also watch for storage hiding inside other symptoms: applications that will not update, photos that will not save, and updates that fail can all be a full device, not a faulty application. Read the stem for what changed, what still works, and who else is affected, then match the fix to that scope, because the wrong choices are often good fixes for a different problem than the one described.
Now try it. The 3 free sample questions for this domain are in practice mode, with full explanations.
Practice Domain 1 questions