220-1101 Hardware 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.

• ✗

  Initialize the drive using Disk Management

  Why it's wrong here

  Disk Management's Initialize Disk function writes a protective partition table (MBR or GPT) and assigns a disk signature, but the tool only lists physical disks that the operating system has already enumerated. If a SATA port is disabled in UEFI/BIOS firmware, the drive never appears in the BIOS POST screen, Device Manager, or Disk Management, so there is no 'Unknown Disk' entry to right-click and initialize. Initialization assumes detection; it cannot force the OS to scan a disabled bus, making it a premature step in this diagnostic sequence.

• ✓

  Enable the SATA port in the BIOS/UEFI settings

  Why this is correct

  In the UEFI/BIOS setup utility, navigate to the SATA Configuration or Peripherals menu and verify the specific port (e.g., SATA5) is set to 'Enabled' rather than 'Disabled' or 'Auto'. When a port is disabled, the firmware does not execute the SATA out-of-band handshake, so the SSD is invisible to both the boot manager and the OS regardless of its power state. Enabling the port and rebooting is the quickest, cheapest corrective action because it addresses a common firmware-level cause of total non-detection for a newly installed SATA drive.

• ✗

  Update the SSD firmware using a USB bootable tool

  Why it's wrong here

  SSD firmware updates are released through bootable ISO/USB images or vendor utilities and are designed to resolve bugs that occur while the drive is in operation, such as performance degradation, TRIM anomalies, or controller errors. If the drive is not detected by the UEFI/BIOS, the bootable firmware tool will also fail to see the drive because it relies on the same SATA controller interface to communicate, so the update cannot proceed. Flashing firmware is never a first step for non-detection; it is a mitigation applied after a recognized drive exhibits a specific bug pattern.

• ✗

  Replace the SATA cable with a known-good cable

  Why it's wrong here

  A failed or marginal SATA cable can independently cause a drive to disappear from the bus, but the scenario explicitly states the technician confirmed the cable is securely seated on both ends. Replacing the cable adds hardware-elimination time and, on a new install, a brand-new cable is statistically far less likely to be at fault than a firmware port being toggled off. The correct initial move is to inspect BIOS/UEFI settings because a disabled port reproduces identical symptoms while being a configuration oversight rather than a physical component failure.

Go deeper

Related to this question