220-1102 - Software Troubleshooting (22% of the exam) - Section 3.4

Troubleshoot common mobile OS and application issues.

Diagnose mobile device problems such as poor battery life, overheating, slow performance, an app failing to launch or update, connectivity drops, and an inability to decrypt email. Map each symptom to the correct fix - closing background apps, clearing the app cache, forcing a stop, freeing storage, toggling radios, or performing a soft reset - and reserve a factory reset for unresolved cases after a backup.

Mobile troubleshootingApp crashesBattery drainSoft resetCache clearing

Practice question for this objective

Free sampleSoftware Troubleshootingmedium

Marcus reports that his company iPhone, which used to last all day, now drains from full to empty by early afternoon after he installed several new apps. Battery health still reads 92 percent. What should the technician check FIRST to identify the cause?

  • AEnable Low Power Mode so the phone throttles background activity, then ask Marcus whether the battery lasts longer over the next few days.
  • BReplace the battery, because rapid drain from a phone that once lasted all day points to a worn cell that can no longer hold its rated charge.
  • CPerform a factory reset and set the phone up as new to clear whatever background process is consuming the charge so quickly.
  • DOpen the battery usage screen in Settings to see the per-app breakdown and find which newly installed app is consuming the most power. Correct
Diagnose sudden mobile battery drain by reading the per-app battery usage screen to identify the offending app before applying fixes. Battery drain that starts right after installing apps, with battery health still high, is almost always a misbehaving app running in the background. The per-app battery usage screen quantifies each app's consumption, letting the technician identify the culprit before choosing a targeted fix rather than guessing.

Why A is wrong: Low Power Mode can extend runtime, but applying a mitigation before finding the cause skips identifying which app is responsible, so it is not the correct first diagnostic step.

Why B is wrong: A worn battery does cause drain, but 92 percent battery health and the onset right after new installs point to software, so a hardware swap is premature.

Why C is wrong: A reset might stop the drain, but it is heavy-handed and destroys the evidence before the offending app is identified, so it is not the first step.

Why D is correct: The battery usage breakdown names the specific app draining the charge, and the drain began right after new installs, so checking it first correctly identifies the cause before any fix is applied.

See more 220-1102 practice questions, answers explained.

Exam traps in Software Troubleshooting

Answers that look right on this material and are not. Each one is a distractor from a different question in the 220-1102 bank for this domain.

  • Perform a factory reset of the phone to eliminate any deep operating system corruption that is preventing this one application from running.

    Why it is wrong: A factory reset is disproportionate when only one app misbehaves and the OS runs everything else fine, so it is a last resort rather than the correct next step.

  • It returns the device to its factory state, erasing all user data, accounts, and installed applications.

    Why it is wrong: This is tempting because a soft reset is a common first step and users conflate it with a full reset, but wiping data describes a factory reset, not a soft reset.

  • Clear the app's storage and data from Settings so the app starts from a completely fresh state on next launch.

    Why it is wrong: Clearing storage does often fix a corrupt-state crash, but it also wipes saved logins and in-app data, so it is not the first, least-destructive step when that data must be kept.

Examworthy is not affiliated with or endorsed by CompTIA. Original, blueprint-aligned practice material only.