70-463 · Question #142
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…
The correct answer is D. ispac. The .ispac file (Integration Services Project Deployment Archive) is the single deployment artifact produced by the Project Deployment Model. It bundles all SSIS packages, project parameters, connection managers, and dependencies into one versioned binary file. This makes…
Question
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?
Options
- Adtsx
- BSSISdeploymentmanifest
- Cmsi
- Dispac
How the community answered
(60 responses)- A2% (1)
- B3% (2)
- D95% (57)
Explanation
The .ispac file (Integration Services Project Deployment Archive) is the single deployment artifact produced by the Project Deployment Model. It bundles all SSIS packages, project parameters, connection managers, and dependencies into one versioned binary file. This makes handoff to junior IT personnel safe and repeatable: the exact validated build is deployed - no risk of version mismatch or missing dependency. A .dtsx file is a single raw package XML file (no bundled dependencies). A .SSISDeploymentManifest is the older Package Deployment Model artifact, which requires manual tracking of individual files. An .msi requires a custom Windows Installer project to build and is not a native SSIS deployment format.
Topics
Community Discussion
No community discussion yet for this question.