Your team is creating SQL Server Integration Services (SSIS) packages that have several
dependencies. The packages use parameters for configuration purposes.
Your company’s IT policies include the following change control requirements:
After a package is ready for deployment, your team must hand over the process to junior IT
personnel.
The process must guarantee that when a package has been validated, that same package
(and all its dependencies) is deployed to production.
The process must be repeatable and reliable and must be executed with the least
administrative and training effort by junior IT personnel.
You need to use the most appropriate deployment unit to satisfy the company policies, while
minimizing issues such as incorrect version or configuration.
Which type of deployment unit should you use?
A.
dtsx
B.
SSISdeploymentmanifest
C.
msi
D.
ispac
Why do you use project deployment(ispac)? The policies require to hand over the package to junior IT personnel package by package upon complicion. So you have to use package deployment -> dtsx.
The question also requires that all dependencies and configuration be also deployed and you need to reduce the risk of a incorrect version of configuration or a dependent package is used. So to avoid all this, use project deployment rather than package deploy.
Agreed D is the correct answer;
https://msdn.microsoft.com/en-us/library/hh213290(v=sql.110).aspx
I would normally agree with Briquet because dtsx is the package extension and iscap is the project extension, however Microsoft is notoriously bad at asking questions. It’s really fifty fifty here. Are they testing that you know dtsx needs corresponding configuration files so it’s more than one file to deliver to the junior guy and redeploying to projects is the solution or are they testing we know that iscap is for projects and the question is worded in such as way that we’re restricted to package deployment solutions. I really don’t know. It can be read both ways