You are a network administrator of your companys Active Directory domain, which consists of four Windows Server 2003 domain controllers and 75 Windows XP Professional computers. The companys written security policy mandates that network administrators must log on with their regular domain user accounts. When a higher level of privileges is required to perform an administrative task, administrators should use the runas command to launch the required application with a specially created account that has the rights to perform the specific task. Name resolution failures begin occurring on your network. You log on to one of your domain controllers by using your non-administrative domain user account. Next, you attempt to run Replication Monitor by using an administrative user account named RM1 by issuing the runas /user:rm1 replmon command. After you enter the password for RM1, the following error is displayed: RUNAS ERROR: Unable to run - replmon 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. You inspect the services on the domain controller to determine the reason that you cannot start Replication Monitor. Failure of which service is most likely to prevent you from starting Replication Monitor?
A. Secondary Logon B. Net Logon C. DNS Client D. DNS Server
Secondary logon-explanation: the most likely reason that you cannot start replication monitor by using the rm1 account is because the secondary logon service is stopped and disabled. secondary logon enables a user to issue the runas command to run a command or start an application using another user accounts security context. when the command has completed or the application is closed, the alternative security context is released; if you start other programs, they will run under the security context of the currently logged on user account. the net logon service is responsible for authenticating remote users and services. however, you are logged on locally. therefore, the net logon service is not preventing you from starting replication monitor. the dns client service is responsible for locating active directory domain controllers and for resolving and caching resolved dns names locally. the dns server service is responsible for answering name resolution queries from dns clients. dns updates will not occur if the dns server service is stopped; therefore, replication might be failing in this scenario because the dns server service has stopped. however, even if the dns server service or the dns client service were stopped, but the secondary logon service were running, you would still be able to use the runas command to start replication monitor.