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.

• ✗

  Windows System Image Manager (WSIM)

  Why it's wrong here

  Windows System Image Manager is part of the Windows Assessment and Deployment Kit (ADK) and is used solely to create and manage unattended answer files (Unattend.xml) that automate settings during Windows installation. It enables administrators to configure components and packages within a Windows image's configuration passes, but it does not process or modify an installed operating system. As such, it cannot remove the unique security identifiers, computer name, or device-specific drivers that must be generalized before deploying a golden image to multiple machines.

• ✓

  Sysprep

  Why this is correct

  System Preparation (Sysprep) is the correct built-in utility for preparing a Windows 10 Pro installation for imaging. It generalizes the operating system by stripping machine-specific information such as the computer name, SID, and hardware-specific driver caches, and then configures the system to boot into Out-of-Box Experience (OOBE) so a new user can set it up. It also resets activation and prepares the installation for capture into a WIM file using DISM or other imaging tools. This is why it is the standard step before deploying Windows to multiple different devices.

• ✗

  Deployment Image Servicing and Management (DISM)

  Why it's wrong here

  Deployment Image Servicing and Management (DISM) is a command-line suite that services and manages Windows images, including mounting and editing WIM files, adding drivers, enabling features, and capturing or applying images. However, DISM on its own does not generalize a Windows installation; it never removes computer-specific identifiers or resets the system for out-of-box configuration. In a typical deployment workflow, you must run Sysprep first to generalize the reference machine, then use DISM to capture that generalized state as an image file. Therefore, DISM is a complementary tool but not the one that performs the required generalization step.

• ✗

  Microsoft Deployment Toolkit (MDT)

  Why it's wrong here

  Microsoft Deployment Toolkit (MDT) is a full-featured solution for automating Windows deployments with task sequences, driver management, and application wizard interfaces, but it is not a built-in component of Windows 10; it must be downloaded separately as part of the ADK or standalone. Even when MDT is used to create a reference image, it relies internally on Sysprep to execute the generalization phase before capturing the WIM file. Thus, while MDT can orchestrate the entire deployment process, it is not the underlying built-in tool that directly removes machine-specific information. If you are looking for the native utility built into Windows that accomplishes the generalization step, Sysprep is the answer.

Go deeper

Related to this question