70-463 · Question #207
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 Ser
The correct answer is B. Use the dtutil/copy command.. The requirements eliminate several options: no CLR integration rules out the Project Deployment Model (which requires the SSIS Catalog, a CLR-dependent feature), and automation rules out manual GUI tools. The dtutil /COPY command (B) is a command-line utility that copies SSIS pac
Question
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?
Options
- AUse the gacutil command.
- BUse the dtutil/copy command.
- CUse the Project Deployment Wizard.
- DCreate an OnError event handler.
- ECreate a reusable custom logging component.
- FRun the package by using the dtexec/rep/conn command.
- GRun the package by using the dtexec/dumperror/conn command.
- HRun the package by using the dtexecui.exe utility and the SQL Log provider.
- IAdd a data tap on the output of a component in the package data flow.
- JDeploy the package by using an msi file.
How the community answered
(13 responses)- B69% (9)
- C15% (2)
- E8% (1)
- G8% (1)
Explanation
The requirements eliminate several options: no CLR integration rules out the Project Deployment Model (which requires the SSIS Catalog, a CLR-dependent feature), and automation rules out manual GUI tools. The dtutil /COPY command (B) is a command-line utility that copies SSIS packages between locations using the Package Deployment Model, which does NOT require CLR integration. Connection Managers in the Package Deployment Model can be made configurable via XML package configuration files or environment variables - no package editing needed. Because dtutil is a CLI tool, it can be scripted and automated easily. Option J (MSI) is possible but less automatable than a scripted dtutil call. Option C (Project Deployment Wizard) is eliminated because the SSIS Catalog it targets requires SQL Server CLR integration to be enabled.
Topics
Community Discussion
No community discussion yet for this question.