70-463 · Question #19
You are developing a SQL Server Integration Services (SSIS) package that imports data into a data warehouse hosted on SQL Azure. The package uses a Foreach container to process text files found in a f
The correct answer is C. Environment Variable. In the Project Deployment model, package and project parameters are supplied at execution time through SSIS catalog Environments and their Environment variables, not through legacy configuration files. Each SQL Agent job can reference a different Environment that holds a differen
Question
You are developing a SQL Server Integration Services (SSIS) package that imports data into a data warehouse hosted on SQL Azure. The package uses a Foreach container to process text files found in a folder. The package must be deployed to a single server by using the Project Deployment model. Multiple SQL Server Agent jobs call the package. Each job is executed on a different schedule. Each job passes a different folder path to the package. You need to configure the package to accept the folder path from each job. Which package configuration should you use?
Options
- A.dtsConfig file
- BRegistry Entry
- CEnvironment Variable
- DParent Package Variable
- EXML Configuration File
How the community answered
(28 responses)- A4% (1)
- C86% (24)
- D4% (1)
- E7% (2)
Why each option
In the Project Deployment model, package and project parameters are supplied at execution time through SSIS catalog Environments and their Environment variables, not through legacy configuration files. Each SQL Agent job can reference a different Environment that holds a different folder path value.
.dtsConfig files are a Package Deployment model configuration type that is not supported in the Project Deployment model.
Registry Entry configuration is a Package Deployment model mechanism that stores values in the Windows registry and is not compatible with the Project Deployment model.
In the Project Deployment model, SSIS catalog Environment variables are mapped to project or package parameters, allowing each SQL Server Agent job to reference a different Environment containing the appropriate folder path - this is the correct mechanism for passing runtime values in the SSISDB catalog deployment model.
Parent Package Variable configuration requires the package to be executed as a child package by a parent package using an Execute Package task, but here independent SQL Agent jobs call the package directly.
XML Configuration files are a Package Deployment model feature and are not used to supply runtime parameter values in the Project Deployment model.
Concept tested: SSIS Project Deployment model parameter passing via catalog Environment variables
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.