74-697 · Question #11
You work for an OEM system builder. You use Windows Deployment Services (WDS) to deploy Windows operating system images. WDS contains a 32-bit boot image. You receive a new client computer model…
The correct answer is B. Add the 32-bit driver for the mass storage device into the boot image. You might aim to deploy 64-bit editions of Windows 8. But you may find that you have to deploy some 32-bit installations because of legacy hardware or application/driver compatibility issues. Some legacy hardware will have 32-bit processors. This means that you will have to use…
Question
You work for an OEM system builder. You use Windows Deployment Services (WDS) to deploy Windows operating system images. WDS contains a 32-bit boot image. You receive a new client computer model that is 64-bit. You add a 64-bit install image of Windows 8 to WDS. You attempt to deploy a new install image to the new computer model by using WDS. The boot image loads on the new computer, but you fail to apply the install image. From Diskpart, you run the List disk command and you discover that no objects are found. You need to ensure that you can deploy the new install image to the new computer model. What should you do?
Options
- AAdd the 64-bit driver for the mass storage device into the boot image.
- BAdd the 32-bit driver for the mass storage device into the boot image.
- CAdd the 64-bit driver for the mass storage device into the install image.
- DAdd the 32-bit driver for the mass storage device into the install image.
How the community answered
(64 responses)- A5% (3)
- B77% (49)
- C6% (4)
- D13% (8)
Explanation
You might aim to deploy 64-bit editions of Windows 8. But you may find that you have to deploy some 32-bit installations because of legacy hardware or application/driver compatibility issues. Some legacy hardware will have 32-bit processors. This means that you will have to use 32-bit boot images for them.
Topics
Community Discussion
No community discussion yet for this question.