Picking a file system by familiarity, not by platform and file size
The wrong answers choose a file system that sounds familiar. FAT32 reads and writes on both platforms, but it caps a single file at 4 GB, so an 8 GB video cannot be stored. NTFS handles large files, yet macOS mounts it read-only by default. APFS is the macOS format, and Windows cannot mount it natively. exFAT is the one that is natively read/write on both Windows and macOS and has no practical 4 GB file limit.
See it in a sample questionPlacing Windows features in the wrong edition
The wrong answers credit Home with features it lacks, or pick an edition above the one needed. Home cannot join an Active Directory domain and has no Group Policy Editor or BitLocker. Its Device Encryption is limited and is not manageable BitLocker, and EFS protects chosen files rather than the whole volume. Enterprise, Education and Pro for Workstations do qualify, but each costs more or sits above Pro in licensing. Pro is the lowest edition with domain join, Group Policy and BitLocker.
See it in a sample questionCrediting a macOS tool with a neighbouring tool's job
The wrong answers swap macOS utilities that sound related, or offer a Windows tool instead. Time Machine takes hourly versioned backups, FileVault encrypts the whole startup volume, Gatekeeper checks where an app came from, and Keychain Access stores passwords and certificates. File History, BitLocker and Credential Manager are the Windows equivalents and do not exist on macOS. Disk Utility repairs volumes and does not schedule backups.
See it in a sample questionReading the wrong Event Viewer log
The wrong answers send the technician to the wrong log, or to a live tool. The System log holds kernel-power, driver and service events, so it explains an unexpected restart or a driver that fails to load. The Application log holds user-mode program crashes. The Security log holds audited logons, and the Setup log covers installation. Task Manager shows only live data and keeps no history across a reboot.
See it in a sample questionSwapping sfc, chkdsk and DISM
The wrong answers hand one repair command the job of another. sfc /scannow replaces corrupt protected system files from a cached copy. chkdsk repairs file-system structures, and chkdsk /r also locates bad sectors and recovers readable data. When sfc cannot repair because its own source is damaged, DISM /Online /Cleanup-Image /RestoreHealth repairs the component store. Rerunning sfc fails for the same reason, and chkdsk does not touch that store.
See it in a sample question