DRAG DROP
You are maintaining a SQL Server Integration Services (SSIS) package. The package uses
custom functionality that is implemented in Microsoft Visual C.
The implementation of the custom functionality changes overtime. The design of the
package allows you to deploy new releases of the custom functionality without redeploying
the entire package.
You need to implement and deploy an update to the custom functionality without requiring
package redeployment.
Which three actions should you perform in sequence? (To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.)
Answer: See the explanation
Explanation:
Box 1: Open the Script task of the package that contains the custom functionality.
Box 2: Edit the C# code.
Box 3: Redeploy the package.Note:
* The Script task provides code to perform functions that are not available in the built-in
tasks and transformations that SQL Server Integration Services provides. The Script task
can also combine functions in one script instead of using multiple tasks and transformations.
Right answer is :
1. Open the custom object that contains the custom functionality
2. Edit the C# code
3. Rebuild and redeploy the custom object.
*Package uses custom functionality created with Custom Object, not Script Task/Component… open custom object (not Script Task)
**Of course, custom objects are written in Visual C#
**Implement and deploy an update to the custom functionality without requiring package redeployment… rebuild/redeploy custom object
So, yes Donk is right
It can’t be a script task because that would require a redeploy of the package. It’s bs because the real reason why you would choose component vs script is whether you want a control flow or a data flow move, not whether there’s a back door way for you to test whether you know the minutia of two components