Free OS installations and upgrades practice questions

A feature update is the large, infrequent release that moves the operating system to a new version, adding new functionality, changing the interface, and sometimes revising system requirements. Because it behaves like a mini operating-system upgrade, it takes longer to install and carries a higher risk of application or driver incompatibility, which is why it deserves the same caution as a version upgrade. A quality update is the frequent, smaller patch that fixes bugs and closes security holes without adding new capabilities, so it does not match the description of changing the interface or advancing to a new version. A cumulative update refers to how quality updates roll earlier fixes into the latest release, but it does not describe a version-advancing release with new features. A driver update installs software that lets the OS communicate with specific hardware and does not advance the operating system to a new version. Recognizing the difference matters because feature updates should be tested and are often deferred in managed environments, while quality updates should be applied promptly to close security gaps.

GPT (GUID Partition Table) is the modern partition style that supports very large drives well beyond 2 TB and many partitions. It pairs with UEFI firmware and is required to take full advantage of features such as Secure Boot, which is why Windows 11 uses GPT. Because the boot drive is 4 TB and must support Secure Boot, GPT is the only valid choice. MBR (Master Boot Record) is the older style that supports drives only up to 2 TB and pairs with legacy BIOS firmware, so it cannot use the full 4 TB drive as a boot disk or support Secure Boot. FAT32 and exFAT are file systems, not partition styles, so neither answers the question about how partitions are organized and how the system boots. FAT32 is limited to a 4 GB maximum file size and is used on small removable media, while exFAT is designed for flash and removable storage without the 4 GB limit. Choosing GPT with UEFI is the standard for modern installations and is what allows drives larger than 2 TB to be used as boot disks.

exFAT is designed for flash and removable storage and removes the 4 GB file-size limit of FAT32 while maintaining broad compatibility across operating systems and devices. Since the drive must hold video files larger than 8 GB and be read and written by both Windows and macOS, exFAT is the correct choice. FAT32 is widely compatible across devices but is limited to a maximum file size of 4 GB, so it cannot store the large video files described. NTFS is the standard for Windows system and data drives with support for large files, permissions, and encryption, but macOS can typically only read NTFS volumes without additional software, making it unsuitable for two-way transfer. ext4 is a native Linux file system and is not natively supported by either Windows or macOS for direct read/write, so it would fail the cross-platform requirement entirely. Choosing the file system based on file size limits and cross-device compatibility is a routine but important decision when preparing removable media.

The most likely reason is that TPM 2.0 is disabled in the UEFI firmware. Windows 11 enforces strict hardware gating that requires UEFI firmware with Secure Boot capability and a Trusted Platform Module (TPM) 2.0. Some firmware ships with TPM disabled by default, so a machine that appears unsupported may actually qualify once the feature is switched on in the UEFI setup. Since the CPU, RAM, and storage are all clearly sufficient, a disabled security feature is the strongest candidate. An NTFS-formatted boot drive is exactly what Windows requires, so it would never block the upgrade. The installed RAM being insufficient is incorrect because 16 GB far exceeds the Windows 11 minimum requirement. The graphics adapter lacking a compatible driver would cause reduced display functionality after installation rather than block the eligibility check performed by PC Health Check. When a machine appears unsupported, the technician should verify whether TPM and Secure Boot are present but simply turned off in firmware before concluding the hardware must be replaced.

Running the old application inside a virtual machine is the best workaround when an essential application has no version compatible with the target operating system. A virtual machine (or a compatibility layer) allows the legacy software to keep running in its supported environment while the physical machine is upgraded, resolving the conflict between the required application and the new OS. Installing a generic built-in driver applies to hardware devices that lack a full manufacturer driver, not to application incompatibility, so it does nothing to make the software run. Performing an in-place upgrade to retain the software will not help because the vendor has already confirmed the application is incompatible with the target OS, meaning it will not function even if the upgrade process attempts to carry it forward. Reformatting the boot drive using a full format is a disk-preparation step that scans for bad sectors and overwrites data; it has no bearing on whether an incompatible application can run. Line-of-business and specialty applications deserve extra scrutiny during upgrade planning precisely because they are the most likely to lack support for a new OS.

The most likely cause is that the operating system could not find a compatible driver for the label printer. Drivers are the software that lets the operating system communicate with hardware, and a new OS needs drivers written specifically for it. Niche peripherals such as label printers, signature pads, and older printers and scanners are among the devices most likely to have driver problems after an upgrade. A warning icon in Device Manager quickly reveals hardware for which the OS could not locate a driver. A boot partition formatted as FAT32 instead of NTFS would not allow a modern Windows installation to run at all, so it does not explain a single malfunctioning peripheral on a working system. A pending feature update is unrelated to a specific device failing immediately after an upgrade, as feature updates advance the OS version rather than resolve individual driver issues. The firmware being switched from UEFI to legacy BIOS would affect boot behavior and partition compatibility, not the driver status of a single USB peripheral. The technician should check the manufacturer's website for a driver that explicitly supports the new operating system.

A full format is the correct choice because it scans the disk surface for bad sectors and, on modern Windows, overwrites the data area, making it safer when a drive is suspected of physical problems or when previous data should be more thoroughly overwritten. Since this drive has reported read errors, the surface scan a full format performs is exactly what is needed. A quick format only rewrites the file system's index without checking the disk surface, so it would not detect the bad sectors that are the technician's concern and would leave the questionable drive unverified. Converting to GPT changes the partition style to support large drives and UEFI booting, but it does not scan for bad sectors or overwrite data. Converting to dynamic disk changes how volumes are managed for features like spanning or software RAID, and it likewise performs no surface check or data-overwrite function. A quick format is fine for a healthy drive, but a full format is the safer option whenever a drive's physical integrity is in doubt.

The primary reason is that major version releases, or feature updates, carry a higher risk of breaking applications or drivers because they add new functionality, change the interface, and can revise system requirements. Administrators frequently defer feature updates to allow time for testing while still applying quality updates quickly, so that important security fixes are not delayed by the extra caution feature updates require. Requiring a full disk image before installing security patches is incorrect because quality updates are small, low-risk, cumulative patches that are applied promptly and routinely without imaging each time. Version releases only installing on GPT-formatted drives is inaccurate, as partition style relates to drive capacity and boot firmware, not to whether a feature update can be deployed. Security patches removing features that users depend on is wrong because quality updates fix bugs and close security holes without adding or removing capabilities. The distinction between frequent low-risk quality updates and infrequent higher-risk feature updates is the foundation of a sound patch-management strategy.

A clean install is the best choice because it resets the foundation of the system entirely, removing persistent crashes, boot issues, and suspected malware to establish a known-good baseline with fewer unknowns. When a system stays unstable after repairs or shows signs of deep infection, starting clean often saves time in the long run. An in-place upgrade install is incorrect because it keeps the current foundation and can preserve bad configuration; it cannot fix a system that is already failing in basic ways and may complete but leave the same instability. A repair installation only replaces or fixes system files without wiping everything, so it may not fully eliminate deep malware or the underlying instability the user is experiencing. Deploying a thin image over the network is not the best fit for a single troubled laptop; imaging is designed for setting up many PCs quickly and consistently, and it would require deployment infrastructure that is unnecessary here. Before performing the clean install, the technician should back up user data, verify licensing and activation, and confirm any BitLocker recovery keys are available.

Using the one-time boot menu, often opened with a function key during startup, is correct because it makes a temporary choice that boots from the selected device once and then returns to the normal boot order on the next restart. This is safer for service tasks because it reduces surprises for the user and prevents the system from repeatedly trying to boot from a device that may later be removed. Changing the persistent boot order in firmware is incorrect because it makes a lasting change; the PC would keep trying the USB first until someone changes it back, which could cause a boot to an empty USB port or confuse a non-technical user. Disabling Secure Boot permanently is unnecessary and introduces a security weakness; while Secure Boot policies can sometimes block unsigned tools, permanently disabling it is not required just to boot a single USB scan and is not the safest approach. Reconfiguring PXE boot priority relates to network booting for imaging and deployment, not booting from a local USB drive for an offline scan. After finishing, the technician should confirm the internal drive returns to the top of the boot list and run a final restart test.