A company has a line-of-business application named App1 that runs on an internal IIS server. App1 uses a SQL Server 2008 database that is hosted on the same
server. You move the database to a dedicated SQL Server named SQL1.
Users report that they can no longer access the application by using their domain credentials.
You need to ensure that users can access App1.
Solution: You configure Kerberos-constrained delegation and then run the following command from an administrative command prompt:
setspn-a MSSQLsvc/SQLl:1433 <domain>\\<sql_service>
Does this meet the goal?
A.
Yes
B.
No
b. no
man must change the string connection between App and SQL server
0
0
When setting a SPN for SQl, I believe you have to register with the Netbios name and FQDN. The above when be incomplete unless I am missing something (most likely am).
https://blogs.msdn.microsoft.com/sqlupdates/2014/12/05/sql-server-kerberos-and-spn-quick-reference/
0
0
I believe this variant of this question is giving the correct answer. There are variants of this question that give the answer as “You configure app1 and SQL1 to use NTLM authentication. The you restart the IIS and SQL Server services.” – obviously wrong.
0
0
Some explanation and comments here https://www.briefmenow.org/microsoft/does-this-meet-the-goal-126/
0
0