Server 2003 Network Environment

After a disk is replaced, it needs to be Reactivated, so that the fault tolerant volume will be rebuilt.

[A: Extended partitions are used only on basic disks. Windows Server 2003 does not support fault tolerant configurations running on basic disks.]

[B: Windows Server 2003 is not capable of automatically repairing a volume.]

[C: The Computer Management utility is not specifically intended to be used for Disk Management.]

Mount points provide a quick and easy way to mount a volume as an empty folder on an NTFS volume, and provide extra space.

[A: Because the application cannot be configured to use a temporary folder on the second drive, this will not resolve the problem.]

[B:Mounting the system partition as a temp folder would probably result in the server failing to boot.]

[C: The term partition indicates that this is a basic disk. Only volumes on dynamic disks can be used as mount points.]

When a mirrored drive fails, you must first "break" the mirror to separate the volumes. After the volumes are separated, you can replace the failed drive. After the failed drive is replaced, you must recreate the mirror.

[A: In Windows Server 2003, you must manually add the drive back to the mirror, it will not automatically regenerate.]

[B & C: When a drive shows a status of missing, that usually indicates a hardware failure. Simply deleting and recreating the mirror will most likely not fix the problem]

This solution produces the desired result and both optional results. Turning on Disk Quotas limits the space that the users have available, and it can be configured to warn them and the administrator when they are running low on space.

This solution produces the desired result and one of the optional results. Turning on Disk Quotas limits the space that the users have available, and it can be configured to warn them and the administrator when they are running low on space. However, Disk Quotas cannot be used to warn the administrator when the volume is running low on space.

Performance Monitor can be used to issue an alert when various thresholds are reached. These alerts can be received in various ways, such as system messages, e-mail notification, or pages.

[A: This will warn only if an Individual user is running out of free space, it will not monitor the free space at the volume level.]

[B: Disk Quotas cannot be used to monitor or report on the free space on a volume.]

[C: This counter does not exist.]

Configuring the printer in a printer pool will distribute the print jobs among all of the printers in the pool. This should allow print jobs to be completed faster, because all printers will be used.

[A: This by itself will not improve the speed of printing reports.]

[B: This won't solve the issue, because it just results in some print jobs and users having different priorities.]

[D: Print auditing will not improve the speed of printing reports, it will only tell you who is doing the printing.]

The Performance Logs and Alerts utility allows you to log the contents of the counters that you select to evaluate the performance of your server and the applications that are running on it. It is very useful because it allows you to monitor performance over a period of time.

[A: Although it is always a good idea to check the Event Viewer for errors whenever a user reports a problem, the Event Viewer would be more helpful if there was a more specific symptom.]

[B: Performance Monitor is only available in pre-Windows 2000 systems]

[D: There is no such tool as System Performance Monitor.]

The Task Manager utility is included in Windows Server 2003 to give administrators a way to monitor and manage the state of currently running applications and processes. Almost a mini-performance utility, this tool provides a quick glance into a system's health. In addition, Task Manager provides the administrator with a summarized view of the basic system resources in use.

[A: Although it is always a good idea to check the Event Viewer for errors whenever a user reports a problem, the Event Viewer would be more helpful if there was a more specific symptom.]

[B: Performance Monitor is only available in pre-Windows 2000 systems.]

[C: The Performance Logs and Alerts utility allows you to log the contents of the counters that you select to evaluate the performance of your server and the applications that are running on it. It is very useful because it allows you to monitor performance over a period of time. What is required in this instance is a tool that will provide a quick snapshot of system performance.]

Disconnected Sessions cannot be displayed via Task Manager.

[A: The Task Manager Applications tab displays a list of the currently active applications, along with their status - either Running or Not Responding.]

[B: The Task Manager Processes tab displays a list of the currently active processes, along with the resources they are using.]

[C: The Users tab displays the users currently logged on to your server.]

Windows Server 2003 uses the Configure Your Server Wizard to tune the operating system for a specific role, such as file server, domain controller, or DNS server. However, the wizard is not included in the in the Windows Server 2003 Web Edition operating system. Which is logical because that version is intended to be used only for web servers, and it comes optimized for that role out of the box.

[A: Although not a full blown performance monitoring tool, the Task Manager can give you a quick overview of system performance.]

[C: This tool is very handy for tuning a web server, as it not only has counters to monitor the performance of the server hardware, but features counters specific to IIS.]

[D: This tool can give you a quick overview of system performance, or can be used to view the logs that were generated using the Performance Logs and Alerts tool.]

System Monitor can give you a quick overview of system performance, or can be used to view the logs that were generated using the Performance Logs and Alerts tool.

The Task Manager utility is included in Windows Server 2003 to give administrators a way to monitor and manage the state of currently running applications and processes. Almost a mini-performance utility, this tool provides a quick glance into a system's health. In addition, Task Manager provides the administrator with a summarized view of the basic system resources in use.

[B & E: This is not a tool that is included in Windows Server 2003.]

[C: This tool was included in pre-Windows 2000 operating systems. It is not available for Windows Server 2003.]

Auditing logon failures is the quickest way to spot what user accounts and machines are being used for failed logon attempts.

[B & D: Unlike previous versions of Windows, in Windows Server 2003, auditing is enabled by default.]

[C: Although this might be a good thing to audit if you suspected that you had someone trying to perform administrative tasks without the proper authority, it won't help you to track failed logon attempts.]

The solution does not satisfy the required result. Although turning off anonymous access and turning on Integrated Authentication protects the Web site from unauthorized users, Integrated Authentication does not work through most firewalls.

Basic Authentication is the only option that supports all browsers, and SSL is required to encrypt the traffic between the browser and the Web site, so the proposed solution produces the required result and both the optional results.

Per seat mode is generally the most efficient licensing mode when the clients require access to more than one server. One Client Access License (CAL) will need to be purchased for each device, for a total of 15 CALs.

[A & B: Client and Server Mode does not exist.]

[D: Although Per Server Mode is the most efficient licensing method for a single server, it is not cost effective when users need to access multiple servers. For example 15 devices x 3 servers = 45 Client Access Licenses (CALs) vs. per seat = 15 CALs.]

This is the proper way to assign IRQs for non-Plug and Play cards. Windows Server 2003 assumes that it can control any IRQ that is available. If an IRQ is reserved via the CMOS, it will not be available for Windows Server 2003 to assign.

[A & B: The Device Manager cannot be used to assign IRQs to non-Plug and Play devices.]

[D: This answer is incorrect because modems require an IRQ, and don't use DMA.]

All non Plug and Play device removals are performed via the Device Manager utility. Most Plug and Play devices are automatically removed from Device Manager after removal from the server.

[A: There is no Add/Remove Hardware Wizard in Windows Server 2003.]

[C: This is definitely NOT recommended! All non Plug and Play device removals are performed via the Device Manager utility.]

[D: The Modem Troubleshooter is used for diagnosing problems with your modems, not for de-installing it. All non Plug and Play device removals are performed via the Device Manager utility.]

If you share a printer with users running other versions of Windows (Windows 9x or Windows NT 3.5 and 4.0), you can install additional printer drivers on your computer so those users can connect to your printer without being prompted to install the drivers missing from their systems.

[A: If the Windows 2000 and Windows XP clients are working, the drivers were installed correctly.]

[B: Manually copying driver files to the folder will not install the drivers.]

[D: Windows NT 4.0- and Windows 2000/2003/XP-based clients check the printer driver each time they connect to the printer. If the driver is not installed or isn't the current version, a copy of the driver is downloaded automatically.]

Terminating the offending process via Task Manager is the cleanest way to recover from this problem.

[A: Restarting the Server service affects only those processes that are remotely connected to your server, such as users connected to file shares, etc.]

[B: The Explorer.exe process is responsible for the user interface, it will have no effect on the database process; stopping it will probably hang the server.]

[D: The e-mail application is probably not hanging the server, and Task Manager cannot restart processes.]

This is the best solution. This solution minimizes, but not totally protects, the workstation from access by unauthorized users. In environments where the users are frequently away from their workstations in a high traffic area, such as a nursing station or a workstation on a sales floor in a department store, users should always lock their workstations when they will be away from them. Automating this process after a period of inactivity provides an extra layer of protection.

[A: Since the files are on the local computer, and being accessed from the console, share permissions do not apply.]

[B: Although this solution is a good security practice, it won't be effective if the nurses leave the workstation logged on and step away from it for a few minutes.]

[D: If the workstation was locked down so that access to the files was limited, the nurses wouldn't be able to access them either.]

Because Mary is accessing the folder through a share, her permissions will be the more restrictive of the combined share and NTFS permissions.

[B: Modify is an NTFS permission, not a share permission.]

[C: This answer is incorrect because the Engineering group has more access than just Read.]

[D: Mary is not a member of the Managers group, and their members are the only ones who have full control over the files.]

Terminal Services effectively allows gives users who are logging on to that server the right to log on locally. This gives users the equivalent access to sitting at the server console, so only NTFS permissions apply.

[A: Because Mary is not accessing the folder through a share, share permissions do not apply.]

[C: This answer is incorrect because the Engineering group has more access than just Read.]

[D: Mary is not a member of the Managers group, and their members are the only ones who have full control over the files.]

Only administrators can log on to a server via Terminal Services unless the Application mode of Terminal Services is installed.

[A: The TSUsers group was used in previous versions of Terminal Services. It has been replaced by the Remote Desktop Users group in Windows Server 2003.]

[B: There is not RDC Users group in the default configuration of Windows Server 2003.]

[C: Terminal Services users should not be granted the log on locally right on Windows Server 2003. By default, the members of the Remote Desktop Users group are granted the "Allow log on through Terminal Services" user right, which gives them only the permissions that are necessary.]

The Terminal Services specific Group Policy items are not supported on pre-Windows Server 2003 computers.

[A: Secedit is not supported in Windows Server 2003, it has been replaced by the Gpupdate command.]

[B: The new Terminal Services policies in Windows Server 2003 don't apply to Windows 2000.]

[D: There is no /TSPolicy switch for the Gpupdate command.]

Configuring the End a Disconnected session property will end the session after it has be in a disconnected state for the configured time and will return the sessions resources to the server. However, if the user left any files open in their session, there is the potential for data loss. In addition, if you have multiple Terminal Services servers, it can be tedious to configure this setting on all of your servers.

If you have multiple Terminal Services servers, it's more efficient to configure them via Group Policy versus configuring individual settings on all of your servers. Configuring the Set time limit for disconnected sessions policy will end the session after it has been in a disconnected state for the configured time, and will return the sessions resources to the server. However, if the user left any files open in their session, there is the potential for data loss.

The solution satisfies the required result and one of the optional results. Although the solution allows HR easy access to the share and blocks other users, all network users will know that it exists.

The solution satisfies the required result and both of the optional results. The solution prevents casual access to the share, because adding the "$" to the share name prevents it from appearing in the browse list, and access to non HR users is blocked via share permissions.

When you start your server using the Last Known Good Configuration, system setting changes made after the last successful startup are lost.

[A: The boot sector is not damaged, so there is no need to run the fixboot command.]

[B: The Winlogon service should not have been disabled, so enabling it will not correct your problem.]

[D: There are no boot diskettes for Windows Server 2003; likewise, the ERD no longer exists and it has been replaced by Automated Server Recovery (ASR).]

Because an authoritative restore was performed, the restored data will have a higher USN than the damaged data, so the restored data will overwrite the damaged data.

[A: The default replication interval for intra-site replication is five minutes, so it is unlikely that the administrator will be able to get the damaged domain controller offline soon enough to prevent replicating the damaged data to DC2.]

[B: The default replication interval for intra-site replication is five minutes, so it is likely that the AD databases on both domain controllers are damaged. Because an authoritative restore was not performed, the damaged data will have a higher USN than the restored data, so the restored data will be overwritten by the damaged data.]

[D: The Recovery Console is not used to restore backups.]

If the boot sector cannot find Ntldr, Windows 2003 cannot start. This can be caused by moving, renaming, or deleting Ntldr, corruption of Ntldr, or corruption of the boot sector.

[A & D: There are no bootable floppies supplied with Windows Server 2003.]

[C: This option is recommended only as a last resort, because it will overwrite your current configuration.]

Most servers will try to boot from a floppy disk, if it is in the floppy drive when the server is restarted. If the floppy disk doesn't have the necessary files, in this case NTLDR, the boot process will stop, and the previously mentioned error will appear.

[A & D: There are no bootable floppies supplied with Windows Server 2003.]

[C: This option is recommended only as a last resort, because it will overwrite your current configuration.]

The Recovery Console allows you to disable or enable drivers and services.

[A: Neither boot floppies nor the ERD are available in Windows Server 2003.]

[B: Restarting a server using the Last known good configuration option will discard any Registry changes (this includes driver installations) that were performed since the last restart. However, these changes are saved to the Registry when the user logs on, so they are no longer available.]

[D: This option will also work; however, it require two reboots, whereas the option to use the Recovery Console only required one, thus saving time.]

This is the best solution. Typically, document files are good candidates for compression; compressing them should free a large amount of space on the server.

[B: There is not a Maximum setting for disk compression, it is either enabled or disabled.]

[C: Enabling disk quotas helps you to identify the amount of space used by each user, but you must configure limits for your users to avoid using up all the space on the server.]

[D: Although defragging the files on your disk should improve performance, it has no effect on the amount of free space.]

This will free up space from Joe's quota so that he can save his article.

[A: Only an administrator can assign ownership of files and folders.]

[B: As long as the shared folder is on the same volume, the quota will still apply. Quotas are set by volume, so it doesn't matter what folder the file is saved in, it will still count against the quota.]

[D: The actual uncompressed size of the file counts against the quota, not the actual size on disk.]

Just adding an additional disk will not appreciably improve the write performance of the application.

Although the read performance of a RAID 5 device is very good, the write performance leaves something to be desired. The overhead of computing and writing the parity information negates any performance gain of spreading the writes over multiple drive spindles. In addition, the parity information will consume the equivalent of one drive, so the available free space will only be 40GB.

Striped drives have the best read/write performance of any drive configuration, because the activity is spread across multiple spindles. Because this is a single volume, it is represented by a single drive letter. In addition, because striped volumes don't use parity information, the full 60GB will be available for data storage. The downside of a striped volume is that it is not fault tolerant. However, because this volume is being used for temporary files, that shouldn't be a problem.

This is a situation where Per Server Mode is the most efficient licensing method for multiple servers. In this example, only 19 connections are needed vs. Per seat, which would require 20 CALs.

[A & B: Client Mode and Server Mode does not exist.]

[C: You cannot assume that Per Seat Mode will always be the most efficient licensing mode when the clients must access more than one server. One Client Access License (CAL) must be purchased for each device, for a total of 20 CALs, whereas there are only 19 CALs required for Per Server Mode.]