70-463 · Question #76
You are adding a new capability to several dozen SQL Server Integration Services (SSIS) packages. The new capability is not available as an SSIS task. Each package must be extended with the same new c
The correct answer is C. Develop a custom task.. A custom SSIS task is compiled into a .NET assembly and deployed to the GAC or a shared location. Once deployed, any SSIS package can reference it as a reusable control flow task without duplicating code. When the logic needs to change, only the assembly is updated - all packages
Question
You are adding a new capability to several dozen SQL Server Integration Services (SSIS) packages. The new capability is not available as an SSIS task. Each package must be extended with the same new capability. You need to add the new capability to all the packages without copying the code between packages. What should you do?
Options
- AUse the Expression task.
- BUse the Script task.
- CDevelop a custom task.
- DUse the Script component,
- EDevelop a custom component.
How the community answered
(24 responses)- A4% (1)
- B8% (2)
- C75% (18)
- E13% (3)
Explanation
A custom SSIS task is compiled into a .NET assembly and deployed to the GAC or a shared location. Once deployed, any SSIS package can reference it as a reusable control flow task without duplicating code. When the logic needs to change, only the assembly is updated - all packages that reference it automatically use the new behavior. Option B (Script task) embeds the code directly inside each package's XML, so the same code would need to be copied to every package - violating the 'no copying' requirement. Option A (Expression task) only evaluates SSIS expressions and cannot implement arbitrary custom logic. Option D (Script component) and Option E (custom component) are data flow components, not control flow tasks, and the scenario describes a control flow capability.
Topics
Community Discussion
No community discussion yet for this question.