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

• ✓

  Prepare bootable media, then connect drives, then boot from USB, then select source and destination drives, then recover data.

  Why this is correct

  Preparing the bootable media first guarantees that a functional recovery environment (e.g., a USB stick with Windows PE or a Linux live ISO) exists before any drives are touched; this avoids the risk of accidentally writing recovery data to the failed drive. Connecting the drives afterward — and before booting — ensures the system's BIOS/UEFI and the recovery OS enumerate both the source and destination devices during initial hardware detection, which is required for the recovery tool to list them later. Booting from the prepared USB then allows you to launch the recovery software, select the source and destination disks, and perform the data copy in a logical sequence.

• ✗

  Connect drives first, then prepare bootable media, then boot from USB, then select source and destination drives, then recover data.

  Why it's wrong here

  Connecting drives before preparing the bootable media is not only inefficient but can create avoidable risks: when the bootable media creation utility runs, it may reassign drive letters or, if the utility auto-detects various drives, it could write the image to the wrong disk, overwriting the very data you intend to recover. Furthermore, without the bootable media already prepared, you cannot boot into a recovery environment, so connecting drives first simply leaves them idle and may introduce confusion about which drive is which. The correct workflow keeps bootable media creation as the first action so that all subsequent steps — connection, boot, and recovery — reference a known, verified environment.

• ✗

  Boot from USB first, then connect drives, then prepare bootable media, then select source and destination drives, then recover data.

  Why it's wrong here

  Booting from a USB stick before preparing it is physically impossible because a blank or non-bootable USB contains no boot sector or operating system to load; the system will either stop with a 'No bootable device' error or fall through to another boot device. Additionally, even if the USB were somehow bootable (which contradicts the sequence), connecting drives after the recovery environment has already started means the operating system may not rescan the SATA/SCSI bus, so the failed drive and destination may never appear in the disk list — especially for controllers that do not support hot-plugging. Therefore, this order fails both logically and operationally, making the first step of preparing media and connecting drives before boot mandatory.

• ✗

  Prepare bootable media, then boot from USB, then connect drives, then select source and destination drives, then recover data.

  Why it's wrong here

  Preparing the bootable media and then immediately booting from it without connecting the failed and destination drives is a critical mistake because the recovery environment performs a one-time hardware enumeration at startup; any drives attached after boot are not automatically detected by the OS unless the controller explicitly supports hot-swap and the recovery driver handles it, which is rare in a standalone USB-booted PE environment. Consequently, the recovery tool would show no source or destination disks, forcing an unwanted reboot and making this sequence inefficient at best. The drives must be physically connected before the USB boot occurs so that they are present in the device list when the recovery application asks you to select source and destination drives.

Go deeper

Related to this question