Your network contains two servers named Server1 and Server2 that run Windows Server 2008 R2.
Server1 and Server2 have the Windows Deployment Services (WDS) server role installed. You need
to prestage a computer. The solution must ensure that when the prestaged computer is deployed, it
downloads a boot image from Server2. What should you do?

A.
At the command prompt, run the dsadd.exe server command.

B.
From Active Directory Users and Computers, create a new computer account.

C.
From Windows PowerShell, run the New-Object cmdlet and specify the property parameter.

D.
From the Windows Deployment Services console, modify the PXE Response Settings for the
server.

Explanation:

Creating Computer Account Objects in AD DS You can use Windows Deployment Services to link
physical computers to computer account objects in Active Directory Domain Services (AD DS).
Computer accounts are created when you:
Create an account before you have attempted a network boot. You can do this using the Active
Directory Users and Computers snap-in or WDSUTIL. Once a computer is linked to a computer
account object in AD DS, the computer is considered “prestaged” or “known.” Then, you can
configure properties on the computer account to control the client’s installation (using WDSUTIL
alone). For example, you can configure the unattend file that the client should receive and the server
that the computer should contact for a network boot. For instructions, see the “Prestage
Computers” section in How to Manage Client Computers. Benefits of Prestaging Client Computers
Prestaging clients provides three main benefits:
An additional layer of security. You can configure Windows Deployment Services to answer only
prestaged clients, therefore ensuring that clients that are not prestaged will not be able to boot from
the network. Additional flexibility. Prestaging clients increases flexibility by enabling you to control
the following. For instructions on performing these tasks, see the “Prestage Computers” section of
How to Manage Client Computers.
– The computer account name and location within AD DS.
– Which server the client should network boot from.
– Which network boot program the client should receive.
– Other advanced options — for example, what boot image a client will receive or what Windows
Deployment Services client unattend file the client should use.
The ability for multiple Windows Deployment Services servers to service the same network segment.
You can do this by restricting the server to answer only a particular set of clients. Note that the
prestaged client must be in the same forest as the Windows Deployment Services server (trusted
forests do not work).
Source: http://technet.microsoft.com/en-us/library/cc770832(WS.10).aspx