70-463 · Question #6
You are developing a SQL Server Integration Services (SSIS) package. To process complex scientific data originating from a SQL Azure database, a custom task component is added to the project. You…
The correct answer is B. Open a command prompt and run the gacutil command. This question tests how to correctly deploy a custom SSIS task component, which requires registering its assembly in the Global Assembly Cache using gacutil.
Question
You are developing a SQL Server Integration Services (SSIS) package. To process complex scientific data originating from a SQL Azure database, a custom task component is added to the project. You need to ensure that the custom component is deployed on a test environment correctly. What should you do?
Options
- AAdd an OnError event handler to the SSIS project.
- BOpen a command prompt and run the gacutil command.
- CConfigure the SSIS solution to use the Project Deployment Model.
- DOpen a command prompt and run the dtexec/dumperror/conn command.
- EConfigure the output of a component in the package data flow to use a data tap.
- FOpen a command prompt and execute the package by using the SQL Log provider and
- GOpen a command prompt and run the dtexec/rep/conn command.
- HRun the dtutil command to deploy the package to the SSIS catalog and store the
- IUse an msi file to deploy the package on the server.
- JOpen a command prompt and run the dtutil/copy command.
How the community answered
(30 responses)- A3% (1)
- B70% (21)
- C17% (5)
- G7% (2)
- J3% (1)
Why each option
This question tests how to correctly deploy a custom SSIS task component, which requires registering its assembly in the Global Assembly Cache using gacutil.
An OnError event handler manages runtime error responses within a package and does not deploy or register a custom component assembly.
Custom SSIS task components are .NET assemblies that must be placed in the GAC so the SSIS runtime can locate and load them on the target machine. Running gacutil.exe /i against the component's DLL registers it in the GAC, which is the required and supported deployment step for custom SSIS components on any environment.
Switching to the Project Deployment Model changes how the package project is deployed to the catalog, but does not register a custom component's assembly in the GAC.
dtexec /dumperror is an execution diagnostic switch that generates error dump files; it does not install or register a custom component.
A data tap captures data flow component output for debugging and does not affect component registration or deployment.
Executing the package with the SQL Log provider via dtexec is a run-time logging action unrelated to custom component deployment.
dtexec /rep generates execution reports and does not deploy or register custom component assemblies.
dtutil deploys SSIS packages to catalog or file system locations, not component assemblies to the GAC.
An MSI installer can wrap gacutil internally but is not the direct tool specified; the question asks what to do, and gacutil is the direct command that performs GAC registration.
dtutil /copy moves package files between storage locations and does not register custom component assemblies.
Concept tested: Deploying custom SSIS components to the Global Assembly Cache
Source: https://learn.microsoft.com/en-us/sql/integration-services/extending-packages-custom-objects/building-deploying-and-debugging-custom-objects
Topics
Community Discussion
No community discussion yet for this question.