You are creating an HTTP endpoint that will be used to provide customer data to external applications. Your SQL Server 2005 computer is named SQL1. You create a stored procedure named dbo.usp_GetPersonData to retrieve the data in the Certkiller database. You create the endpoint by using the following code. CREATE ENDPOINT SQLEP_AWPersons AS HTTP (PATH = ‘/AWpersons’, AUTHENTICATION = (INTEGRATED), PORTS = (CLEAR), SITE = ‘SQL1’) FOR SOAP (WEBMETHOD ‘PersonData’ (NAME=’ Certkiller .dbo.usp_GetPersonData’), BATCHES = DISABLED, WSDL = DEFAULT, DATABASE = ‘ Certkiller ‘, NAMESPACE = ‘http://Adventure-Works/Persons’)
The first users to connect to the endpoint tell you that they do not get any data. You connect to the endpoint and discover that it is not responding. You need to modify the endpoint so that data is returned as expected. What should you do?
A.
Change the AUTHENTICATION property to KERBEROS.
B.
Specify BATCHES = ENABLED.
C.
Specify STATE = Started.
D.
Specify WSDL = ‘pr_GetPersonData’.
Explanation:
The possible states for an endpoint are STARTED, STOPPED, and DISABLED. For an endpoint to respond to requests, the state must be set to STARTED. To comply with the SQL Server 2005 "off by default" approach to security, the default state is STOPPED.