70-463 · Question #122
You have received reports regarding a current existing SQL Server Integration Services (SSIS) package not completing its execution, and not transferring data. You have decided to make use of the…
The correct answer is A. CLR integration is NOT required on the database engine. D. Events that are created by the package are NOT captured automatically during execution. The Package Deployment Model differs from the Project Deployment Model in that CLR integration is not required on the database engine and package execution events are not automatically captured to the catalog.
Question
You have received reports regarding a current existing SQL Server Integration Services (SSIS) package not completing its execution, and not transferring data. You have decided to make use of the Package Deployment Model. Which of the following is TRUE with regards to using the Package Deployment Model?
Options
- ACLR integration is NOT required on the database engine.
- BEnvironment-specific parameter values are stored in environment variables.
- CEvents that are created by the package are captured automatically and saved to the catalog
- DEvents that are created by the package are NOT captured automatically during execution.
How the community answered
(57 responses)- A86% (49)
- B5% (3)
- C9% (5)
Why each option
The Package Deployment Model differs from the Project Deployment Model in that CLR integration is not required on the database engine and package execution events are not automatically captured to the catalog.
The Package Deployment Model uses the legacy msdb-based or file system deployment and does not rely on the SSISDB catalog, so CLR integration on the SQL Server database engine is not a requirement for its operation.
Storing environment-specific parameter values in environment variables is a feature of the Project Deployment Model using the SSISDB catalog, not the Package Deployment Model.
Automatic capture of events to the catalog is a feature of the Project Deployment Model, not the Package Deployment Model - this statement is false for the Package Deployment Model.
Unlike the Project Deployment Model where execution events and logs are automatically written to the SSISDB catalog, the Package Deployment Model does not automatically capture or persist execution events to the catalog.
Concept tested: SSIS Package Deployment Model characteristics vs Project Deployment Model
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.