You have prepared a reference computer that runs Windows 7 and want to deploy its image to multiple machines. You create an unattended answer file named answer.xml. You need to ensure that the deployed installations automatically apply the settings in answer.xml after you capture and deploy the image. Which Sysprep command should you run on the reference computer before capturing the image?

Introduction / Context:
When you create a Windows 7 reference image for deployment, you typically customize the system, then run Sysprep to remove machine specific information and prepare it for cloning. If you also create an unattended answer file (answer.xml) to automate setup options such as product key, time zone, and user creation, you must tell Sysprep to use that file so that the deployed systems apply those settings during the Out of Box Experience (OOBE).

Given Data / Assumptions:

• The reference computer is running Windows 7 and has been configured as desired.
• An unattended answer file named answer.xml has been created.
• You will capture the reference image and deploy it to multiple machines.
• You want the answer file to be applied automatically during installation on the deployed machines.

Concept / Approach:
The Sysprep.exe tool prepares a Windows installation for imaging. The /generalize option removes unique information such as the SID, the /oobe option tells Windows to present the initial setup experience to the end user, and the /unattend:filename option tells Sysprep to associate a specific unattended answer file with the image. Running Sysprep with these options ensures that when the image boots on a new computer, Windows Setup uses answer.xml to automate configuration.

Step-by-Step Solution:
1. Confirm that the tool you must use before imaging is Sysprep.exe, which is used for preparing Windows for deployment. 2. Identify that you need to both generalize the image and configure it to run through OOBE on the target machines. 3. Recognize that the /generalize switch removes system specific data, while /oobe configures the next boot to go into Out of Box Experience. 4. Attach the /unattend:answer.xml parameter so that Sysprep knows which answer file to use during the next boot and setup phase. 5. The resulting command Sysprep.exe /generalize /oobe /unattend:answer.xml meets all of these requirements.

Verification / Alternative check:
Microsoft documentation for deploying Windows 7 images shows examples where admins run Sysprep with /generalize /oobe /unattend:unattend.xml before capturing an image. When the image is deployed and the machine boots, Windows Setup uses that file to fill in configuration answers without manual input. Audit mode (/audit) is used for further customization, not for final customer deployment. Imagex.exe is used only to capture and apply .wim images; it does not process answer files by itself.

Why Other Options Are Wrong:
Options a and b both use Imagex.exe, which is not the correct tool for associating an answer file with the deployment; Imagex is used for image capture and deployment, not for Sysprep configuration. Option c uses Sysprep with /reboot /audit /unattend:answer.xml, which restarts the system in audit mode instead of OOBE and is typically used for further customizations by OEMs, not for final deployment to end users. It does not meet the requirement of applying the answer file during the actual customer facing installation.

Common Pitfalls:
Many administrators confuse audit mode with OOBE and mistakenly run /audit when they actually want the end user experience. Another common mistake is failing to run /generalize, which can cause deployment issues due to duplicated SIDs or hardware specific settings. Finally, some forget to specify /unattend and then wonder why their answer file was ignored at deployment time.

Final Answer:
You should run Sysprep.exe /generalize /oobe /unattend:answer.xml on the reference computer before capturing the image.