70-463 · Question #44
You are developing a project that contains multiple SQL Server Integration Services (SSIS) packages. The packages will be deployed to the SSIS catalog. One of the steps in each package accesses an…
The correct answer is B. Set the Sensitive property of the parameters to True. In the SSIS catalog Project Deployment Model, setting a parameter's Sensitive property to True causes the catalog to encrypt the value at rest and mask it from display.
Question
You are developing a project that contains multiple SQL Server Integration Services (SSIS) packages. The packages will be deployed to the SSIS catalog. One of the steps in each package accesses an FTP site to download data files. You create project parameters to store the username and password that are used to access the FTP site. You need to ensure that the username and password values are encrypted when they are deployed. What should you do?
Options
- AConvert the parameters to package parameters.
- BSet the Sensitive property of the parameters to True.
- CSet the ProtectionLevel property of the package to EncryptSensitiveWithPassword.
- DConvert the project to the Legacy Deployment model.
How the community answered
(42 responses)- B95% (40)
- C2% (1)
- D2% (1)
Why each option
In the SSIS catalog Project Deployment Model, setting a parameter's Sensitive property to True causes the catalog to encrypt the value at rest and mask it from display.
Converting project parameters to package parameters changes their scope but does not add any encryption; the Sensitive property still needs to be set to True to enable encryption.
When a project parameter has its Sensitive property set to True in the SSIS catalog, the Integration Services catalog automatically encrypts the stored value using the catalog's master key and does not display it in plain text in catalog views or the SSMS GUI. This is the designed mechanism for protecting credentials such as usernames and passwords within the Project Deployment Model, requiring no additional configuration beyond the property setting.
EncryptSensitiveWithPassword is a ProtectionLevel setting used in the Package Deployment (file-based) model to encrypt packages on disk with a password, not applicable when deploying to the SSIS catalog.
Converting to the Legacy Deployment model moves away from the catalog entirely, losing catalog-based encryption features and requiring password-based file encryption instead.
Concept tested: SSIS catalog parameter encryption using Sensitive property
Source: https://learn.microsoft.com/en-us/sql/integration-services/catalog/catalog-properties-ssisdb-database
Topics
Community Discussion
No community discussion yet for this question.