220-1102 Operating Systems 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.

• ✓

  In-place upgrades between 32-bit and 64-bit architectures are not supported

  Why this is correct

  The Windows Setup upgrade engine can only replace the existing OS image with another image of the same processor architecture because every executable, service, and system DLL is compiled for a specific instruction set. Moving from 32-bit to 64-bit requires restructuring the entire system partition, boot manager, and the Windows side-by-side store, which the in-place upgrade mechanism is not capable of doing. Consequently, the only supported path is a clean install of the 64-bit edition, including reinstallation of all applications and driver packages.

• ✗

  Windows 11 requires a Microsoft account for upgrade

  Why it's wrong here

  The Microsoft account requirement applies only to the Out-of-Box Experience during a fresh installation of Windows 11 Home/Pro consumer editions, and it is a post-install setup choice, not a compatibility or upgrade blocker. During an in-place upgrade, existing user accounts, including local accounts, are preserved unchanged, and Setup never prompts to add or convert a Microsoft account as part of the upgrade flow. Even with an active Microsoft account linked afterwards, the upgrade itself remains fully functional, so this is not a reason the upgrade would fail.

• ✗

  The system lacks TPM 2.0 support

  Why it's wrong here

  The scenario explicitly states that the hardware meets all Windows 11 requirements, which includes TPM 2.0, UEFI with Secure Boot, and a supported CPU. The Windows Setup compatibility check (as seen in the PC Health Check app) would therefore pass this validator, and the upgrade would not be stopped by a TPM error. If the TPM were absent or disabled, the upgrade would indeed be rejected, but that hypothetical does not apply here because TPM 2.0 support is already declared as present.

• ✗

  Windows 10 Pro cannot be upgraded to Windows 11 Pro

  Why it's wrong here

  Windows 10 Pro and Windows 11 Pro are the same feature edition from the same retail/licensing channel, so Microsoft explicitly supports an in-place upgrade between them as long as the architecture is identical (64-bit to 64-bit in this case). The upgrade keeps the existing Pro product key, edition, user accounts, files, and applications, with Setup performing only a component and build replacement. A 32-bit source installation is the only condition that forces a clean install; if this system were 64-bit Pro, the in-place path would be entirely valid, proving this option is not the blocker.

Go deeper

Related to this question