Windows 2000 Server
You install a new multiple-process database application named Application on your Windows 2000 Server computer. Two days later, users begin to report that the new application has suddenly stopped responding to queries. You verify that the server is operation and decide that you need to restart the application. What should you do before you restart the application?
End the Application.exe process tree
End the Application.exe process
End both the Explorer.exe process and the Application.exe process
Shut down the PDC of the existing Windows NT domain from the network. On the new computer, install Windows 2000 Server, and then run the Active Directory Installation wizard to install Active Director
Shut down the PDC of the existing Windows NT domain from the network. On the new computer, install Windows 2000 Server, and then run the Active Directory Installation wizard to install Active Director
On the new computer, install Windows NT Server 4.0 and designate the computer as a PDC in a new domain that has the same NetBIOS name as the existing Windows NT domain. Upgrade the computer to Windows
On the new computer, install Windows NT Server 4.0 and designate the computer as a BDC in the existing domain. Promote the computer to the PDC of the domain. Upgrade the computer to Windows 2000 Serve
Shut down, and restart a single domain controller by using the Recovery Console. Use Windows Backup to restore the System State data. Exit the Recovery Console. Restart the computer
On a single domain controller, use Windows Backup to restore the System State data. Shut down and restart the computer
Shut down and restart a single domain controller in directory services restore mode. Use Windows Backup to restore the System State data. Run the Ntdsutil utility. Restart the computer
Shut down and restart each domain controller by using the Recovery Console. Use Windows Backup to restore the Sysvol folder. Exit the Recovery Console. Restart the computer
Configure a Group policy for the Default Domain Controller to block all unsigned drivers
Configure the Windows 2000 file servers, Windows 2000 print servers, Windows 2000 professional computers and Windows 2000 file servers to block unsigned drivers
None of above
Configure a Group policy for the Domain that blocks all unsigned drivers