You are deploying a new SQL Server Integration Services (SSIS) package to five servers.
The package must meet the following requirements:
.NET Common Language Runtime (CLR) integration in SQL Server must not be enabled.
The Connection Managers used in the package must be configurable without editing and
redeploying the package.
The deployment procedure must be automated as much as possible.
Performance must be maximized.
You need to set up a deployment strategy that meets the requirements.
What should you do?
A.
Add an OnError event handler to the SSIS project.
B.
Use an msi file to deploy the package on the server.
C.
Open a command prompt and run the gacutil command.
D.
Open a command prompt and run the dtutil /copy command.
E.
Open a command prompt and run the dtexec /rep /conn command.
F.
Open a command prompt and run the dtexec /dumperror /conn command.
G.
Open a command prompt and execute the package by using the SQL Log provider and
running the dtexecui.exe utility.
H.
Create a reusable custom logging component and use it in the SSIS project.
I.
Configure the SSIS solution to use the Project Deployment Model.
J.
Configure the output of a component in the package data flow to use a data tap.
K.
Run the dtutil command to deploy the package to the SSIS catalog and store the
configuration in SQL Server.
The SSIS catalog is the SSISDB which needs the clr integration to work. It’s also known as the integration services catalog. This K, though attractive, is wrong
According to this ref,answer is D.we cant use dtutil to deploy on SSIS catalogue. question also clearly state that CLR must not be enabled. it’s not K. but like Israel said though attractive.
dtutil can be performed on any SSIS package that is stored in one of three locations: a Microsoft SQL Server database, the SSIS Package Store, and the file system.
https://msdn.microsoft.com/en-us/library/ms162820(v=sql.110).aspx