70-463 · Question #88
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 A. Set the Sensitive property of the parameters to True. In the SSIS catalog (Project Deployment Model), marking a parameter's Sensitive property as True tells the catalog to encrypt that value using the catalog's master key. Sensitive parameter values are never stored or transmitted in plain text by the catalog. Option B…
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 sales transaction data. 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
- ASet the Sensitive property of the parameters to True.
- BSet the ProtectionLevel property of the package to EncryptSensitiveWithUserKey.
- CChange the parameters to package parameters.
- DChange the project to the Legacy Deployment model.
How the community answered
(32 responses)- A94% (30)
- B3% (1)
- C3% (1)
Explanation
In the SSIS catalog (Project Deployment Model), marking a parameter's Sensitive property as True tells the catalog to encrypt that value using the catalog's master key. Sensitive parameter values are never stored or transmitted in plain text by the catalog. Option B (EncryptSensitiveWithUserKey) is a package-level ProtectionLevel setting used for file-based storage-it does not apply when the package is stored in the catalog, which manages its own encryption. Option C (changing to package parameters) changes the scope but not the encryption behavior. Option D (Legacy Deployment Model) removes catalog-based encryption entirely and is a step backward.
Topics
Community Discussion
No community discussion yet for this question.