You recently observed a developer using the SecureString variable type in their workflow.
What is a UiPath best practice relative to the use of SecureString?
You recently observed a developer using the SecureString variable type in their workflow.
What is a UiPath best practice relative to the use of SecureString?
The SecureString variable type is designed to securely handle sensitive information such as passwords. To maximize security, UiPath best practices recommend that the scope of a SecureString variable should be limited to the scope where it is created. This minimizes the risk of exposing sensitive information by reducing the region of the workflow where the variable is accessible.
The SecureString type should not be used for any purpose other than the intended. Scope of these variables should be very limited, ideally in the same scope where they were created.
B is recommended for security purposes as well. You do not use it other specific purpose.
Ans : B
SecureString variable scope should be limited to the scope where it is created.