70-463 · Question #154
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…
The correct answer is D. Open a command prompt and run the dtutil/copy command. The dtutil utility is the standard command-line tool for managing SSIS packages. Running dtutil /copy automates the deployment of package files (.dtsx) to multiple SQL Server instances from a script or batch process, satisfying the automation requirement. The Package Deployment…
Question
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?
Options
- AAdd an OnError event handler to the SSIS project.
- BUse an msi file to deploy the package on the server.
- COpen a command prompt and run the gacutil command.
- DOpen a command prompt and run the dtutil/copy command.
- EOpen a command prompt and run the dtexec/rep/conn command.
- FOpen a command prompt and run the dtexec/dumperror/conn command.
- GOpen a command prompt and execute the package by using the SQL Log provider and
- HCreate a reusable custom logging component and use it in the SSIS project.
- IConfigure the SSIS solution to use the Project Deployment Model.
- JConfigure the output of a component in the package data flow to use a data tap.
How the community answered
(29 responses)- A17% (5)
- B3% (1)
- D69% (20)
- F3% (1)
- J7% (2)
Explanation
The dtutil utility is the standard command-line tool for managing SSIS packages. Running dtutil /copy automates the deployment of package files (.dtsx) to multiple SQL Server instances from a script or batch process, satisfying the automation requirement. The Package Deployment Model uses XML-based package configuration files or environment variables to configure Connection Managers at runtime without editing or redeploying the package, satisfying the configurability requirement. CLR integration is not required for this approach. The Project Deployment Model (option I) would require CLR-dependent SSISDB catalog objects and is therefore excluded by the first requirement. The other command options (dtexec variants) are for executing packages, not deploying them.
Topics
Community Discussion
No community discussion yet for this question.