A developer is creating an automation project which creates a temporary password in the company’s system for new employees. To protect this sensitive information from being logged during the execution of the automation at the Verbose level, how can the developer avoid logging any variable and argument values in both Orchestrator and Studio?
To prevent sensitive information from being logged during the execution of the automation at the Verbose level, the developer should check the Private property on the activities that reference the variables or arguments. This ensures that the values of those variables or arguments are not logged in both Orchestrator and Studio logs, enhancing the security and confidentiality of sensitive data.
Ans : D
correct ans is option C. Checking the "Private" property on activities, primarily affects the local Studio logs and may not prevent sensitive data from being logged in Orchestrator logs. Hence option D is incorrect
It has to be D. The Isolated property is not used for the purposes of hiding sensitive information. It is used isolate faulty workflows from the main workflow. https://docs.uipath.com/activities/other/latest/workflow/invoke-workflow-file
I think it seems more like B, sorry again guys
Check the Private property on the activities that contain sensitive information.