70-463 · Question #5
You are developing a SQL Server Integration Services (SSIS) project that copies a large amount of rows from a SQL Azure database. The project uses the Package Deployment Model. This project is…
The correct answer is I. Configure the SSIS solution to use the Project Deployment Model. This question tests that the SSIS catalog only supports the Project Deployment Model, so a project using the Package Deployment Model must be converted before it can be deployed to the catalog.
Question
You are developing a SQL Server Integration Services (SSIS) project that copies a large amount of rows from a SQL Azure database. The project uses the Package Deployment Model. This project is deployed to SQL Server on a test server. You need to ensure that the project is deployed to the SSIS catalog on the production server. What should you do?
Options
- AOpen a command prompt and run the dtexec/dumperror/conn command.
- BCreate a reusable custom logging component and use it in the SSIS project.
- COpen a command prompt and run the gacutil command.
- DAdd an OnError event handler to the SSIS project.
- EOpen a command prompt and execute the package by using the SQL Log provider and
- FOpen a command prompt and run the dtexec/rep/conn command.
- GOpen a command prompt and run the dtutil/copy command.
- HUse an msi file to deploy the package on the server.
- 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
(26 responses)- A4% (1)
- E15% (4)
- H8% (2)
- I73% (19)
Why each option
This question tests that the SSIS catalog only supports the Project Deployment Model, so a project using the Package Deployment Model must be converted before it can be deployed to the catalog.
dtexec /dumperror writes error dump files to disk and is an execution diagnostic tool, not a deployment mechanism for the SSIS catalog.
A custom logging component addresses observability, not the deployment model incompatibility that prevents catalog deployment.
gacutil registers assemblies in the GAC for custom components and is unrelated to deploying a project to the SSIS catalog.
An OnError event handler handles runtime errors within a package and does not change the deployment model or enable catalog deployment.
Executing a package with the SQL Log provider via dtexec is a run-time action, not a deployment action targeting the SSIS catalog.
dtexec /rep generates execution reports at runtime and does not deploy a project to the catalog.
dtutil /copy copies package files between file system locations and cannot deploy to the SSIS catalog.
An MSI file deployment targets the file system or legacy SSIS service store, not the SSIS catalog which requires Project Deployment Model packages.
The SSIS catalog (SSISDB) exclusively supports the Project Deployment Model; packages using the Package Deployment Model cannot be deployed to it. Converting the solution to the Project Deployment Model using the Project Conversion Wizard enables deployment via the catalog's deployment wizard or dtutil, meeting the requirement to deploy to production SSISDB.
A data tap captures data flow output for debugging; it does not change the deployment model or enable catalog deployment.
Concept tested: SSIS Package vs Project Deployment Model for catalog deployment
Source: https://learn.microsoft.com/en-us/sql/integration-services/packages/deploy-integration-services-ssis-projects-and-packages
Topics
Community Discussion
No community discussion yet for this question.