You are developing automation solutions that process sensitive employee data for a company. You plan to implement the sensitive variables feature in Power Automate for desktop. What are three…

Variables marked as sensitive can still be fully used and manipulated (referenced, assigned, operated on) within the desktop flow itself; the sensitivity primarily affects their visibility in logs and designer UIs.

This statement is incorrect because the core function of sensitive variables is to *prevent* their values from being visible within desktop flow logs in the Power Automate portal, enhancing security.

A key purpose of marking a variable as sensitive is to prevent its actual value from being logged in the Power Automate portal, ensuring that sensitive data is not inadvertently exposed in execution logs.

Any variable, regardless of its data type (text, number, boolean, etc.), can be marked as sensitive to protect its value from appearing in logs or being easily viewed in the designer.

This statement is incorrect as the sensitive variable feature is not limited to password variables; it can be applied to any variable containing data that needs to be protected from logging or casual viewing.