DRAG DROP
You are developing a SQL Server Integration Services (SSIS) package that is ready for
deployment to a production server. The package contains sensitive information secured by
using the EncryptSensitiveWithUserKey package protection level.
You are preparing the package for deployment by the production operations team.
You need to ensure that the production operations team can open and execute the package
without re-entering the sensitive information.
Which three steps should you perform in sequence? (To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.)
Answer: 
Open the package in SSDT
Click the design surface of the Control Flow designer
In the Properties window …
Whoever this ‘admin’ is, he’s definitely not testing out his options before picking them!! Without much ado, Cao is right.
It’s a bit inconsistent to me. As per
https://msdn.microsoft.com/en-us/library/ms141747%28v=sql.110%29.aspx
Encrypt sensitive with password: Uses a password to encrypt only the values of sensitive properties in the package. DPAPI is used for this encryption. Sensitive data is saved as a part of the package, but that data is encrypted by using a password that the current user supplies when the package is created or exported. To open the package in SSIS Designer, the user must provide the package password. If the password is not provided, the package opens without the sensitive data and the current user must provide new values for sensitive data. If the user tries to execute the package without providing the password, package execution fails.
It clearly says that a different user HAS to provide the password to run the package.
The question clearly says: ‘You need to ensure that the production operations team can open and execute the package
WITHOUT re-entering the sensitive information.’
So to execute the package the new user still needs to provide a password.
Agree with cao
+1
This second step, clicking the design surface of the control flow, is stupid. You can just go to the properties window and set the property values. Clicking on the control flow doesn’t do anything. You can also right click the control flow and select properties. I mean, I don’t see another likely third step, but can it really be something as stupid as click the design surface of the control flow? This falls under the category of this is stupid because Microsoft is stupid. Cognos friends, learn Cognos, it’s way easier.
CAO Is right