220-1101 Mobile Devices Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  The battery is no longer able to hold a charge.

  Why it's wrong here

  A battery that can no longer hold a charge typically exhibits symptoms like rapid self-discharge, sudden shutdowns, or a short runtime even after a full charge. These symptoms are independent of the physical connection between the cable and port; a completely healthy battery would still charge intermittently if the connector were loose. Since the technician specifically observed a loose cable fit, the issue is mechanical in nature, not electrochemical capacity loss.

• ✓

  The charging port or connector is damaged or worn.

  Why this is correct

  The charging port's internal contacts or the retaining clip (e.g., the metal tongue in a USB-C socket) can become bent, widened, or contaminated over time, reducing grip on the cable and allowing it to shift. This physical looseness causes the electrical pins to lose contact intermittently, leading to charging that cuts in and out. Because the symptom is a poor mechanical fit, a worn or damaged port is the most common and direct cause—wiggling the cable would temporarily restore contact.

• ✗

  The operating system has a bug affecting charging.

  Why it's wrong here

  An operating system bug could potentially cause incorrect battery reporting, fail to negotiate power delivery, or trigger unexpected charging behavior, but it cannot alter the physical fit of the cable in the port. The technician's observation of a loose cable is a hardware-level condition; software has no means to compress or expand the connector's metal contacts. Furthermore, OS-related issues would not manifest as a cable that can be moved visibly in and out, as the user would instead see errors or inconsistent charge percentages.

• ✗

  The firmware controlling the charging circuit is corrupted.

  Why it's wrong here

  Corrupted firmware in the charging controller could cause erratic behavior such as refusing to charge, excessive heat, or failure to negotiate the correct voltage, but it cannot affect the mechanical tension of the port's contacts. A firmware glitch does not bend, stretch, or wear out the physical socket; the cable would still fit snugly if the hardware were intact. The definitive clue here is the loosely fitting cable, which is purely a hardware defect and not something that a firmware reflash or software update could resolve.

Go deeper

Related to this question