You are deploying a new SQL Server Integration Services (SSIS) package to several 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 the package.
• The deployment procedure must be automated as much as possible.
You need to set up a deployment strategy that meets the requirements.
What should you do?
A.
Use the gacutil command.
B.
Use the dtutil /copy command.
C.
Use the Project Deployment Wizard.
D.
Create an OnError event handler.
E.
Create a reusable custom logging component.
F.
Run the package by using the dtexec /rep /conn command.
G.
Run the package by using the dtexec /dumperror /conn command.
H.
Run the package by using the dtexecui.exe utility and the SQL Log provider.
I.
Add a data tap on the output of a component in the package data flow.
J.
Deploy the package by using an msi file.
K.
Deploy the package to the Integration Services catalog by using dtutil and use SQL Server to store the
configuration.
https://www.mssqltips.com/sqlservertutorial/215/command-line-deployment-tool-for-ssis-packages/
DTUTIL is used for legacy package deployment, which is the case here. They don’t want .Net CLR which is needed for project deployment.
Reference: https://www.sqlservercentral.com/Forums/Topic1577722-2799-1.aspx