220-1201 Practice Question: After updating the firmware on a workstation, the…

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 hard drive has failed due to the update

  Why it's wrong here

  A firmware update primarily affects the motherboard's basic input/output system and its integrated components, not the physical integrity or data on a storage drive. If the hard drive is still detected within the UEFI/BIOS setup utility, it indicates that the drive's controller and basic hardware are functional. A boot issue immediately after a firmware update is far more likely related to system configuration changes rather than a sudden, catastrophic hardware failure of the drive itself.

• ✗

  Secure Boot is blocking the bootloader

  Why it's wrong here

  Secure Boot is a security feature within UEFI that prevents unauthorized operating systems or bootloaders from loading during startup by verifying their digital signatures. If Secure Boot were blocking the bootloader, the system would typically display a specific error message indicating a "Secure Boot Violation" or "Invalid Signature," rather than simply failing to find a boot device. Furthermore, Secure Boot primarily affects unsigned bootloaders, which is less common for standard Windows installations.

• ✓

  The boot mode changed from Legacy to UEFI (or vice versa)

  Why this is correct

  Firmware updates often reset UEFI/BIOS settings to their default values, which can include the crucial boot mode setting. If the system was previously configured to boot in Legacy BIOS (CSM) mode with an MBR-partitioned drive and the firmware update defaults to UEFI mode, the system will fail to find a bootable operating system. Conversely, if a GPT-partitioned drive was set up for UEFI boot and the system reverts to Legacy mode, it also won't recognize the boot partition, leading to a boot failure.

• ✗

  The CMOS battery needs replacement

  Why it's wrong here

  The CMOS battery powers the real-time clock and retains UEFI/BIOS settings when the system is unplugged from power. While a dead CMOS battery can cause settings to revert to defaults, this issue typically manifests after the system has been powered off and unplugged for an extended period, not immediately following a firmware update. A firmware update itself is a controlled process that writes new settings, making a dead CMOS battery an unlikely immediate cause for a boot error.

Go deeper

Related to this question

Same concept, more angles

1 more way this is tested on 220-1201

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.