PL-500 practice question 1 of 25

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 characteristics of the sensitive variables feature? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

Full set: 173 questions

Domain Develop solutions

Answer options
A: You can reference and manipulate variables that are marked as sense from within desktop flows. Correct answer
B: You can view the value of variables marked as sensitive within desktop flow logs by using the Microsoft Power Platform admin center.
C: Sensitive variables are not visible within desktop flow logs in the Power Automate portal. Correct answer
D: You can mark any variable as sensitive. Correct answer
E: Only variables that are passwords can be marked as sensitive.
Correct Answer:
A. You can reference and manipulate variables that are marked as sense from within desktop flows.; C. Sensitive variables are not visible within desktop flow logs in the Power Automate portal.; D. You can mark any variable as sensitive.
Explanation

The sensitive variables feature in Power Automate for desktop is designed to protect data from being exposed in logs. While these variables can be used and manipulated within the flow's logic just like any other variable, their values are masked in the desktop flow logs available in the Power Automate portal. This protection is flexible and can be applied to any variable type, not just passwords, by enabling the "Mark as sensitive" toggle in the variable's properties pane. This ensures that confidential information, such as employee data, is not inadvertently exposed during monitoring or troubleshooting.

Why Incorrect

B. The primary purpose of marking a variable as sensitive is to prevent its value from being visible in any logs, including those in the Power Platform admin center.
E. The feature is not limited to passwords; any variable containing data deemed sensitive (e.g., PII, financial data) can be marked as such.

References

1. Microsoft Learn. "Manage sensitive variables." Power Automate Documentation.

Supports A: The documentation states, "Sensitive variables can be manipulated like every other variable." This confirms they can be referenced and used within the flow's logic.

Supports C & refutes B: The document explicitly says, "When you enable the sensitive toggle for a variable, its value is masked in the desktop flow logs in the Power Automate portal."

Supports D & refutes E: The documentation states, "You can mark any variable as sensitive in the variable's properties pane," without restricting it to a specific data type like passwords.

2. Microsoft Learn. "Sensitive text in Power Automate for desktop." Power Automate Documentation.

Supports C: This document reinforces the core concept: "When you mark a text as sensitive, its content won't be logged in the run history of the Power Automate portal."

Supports D: The examples and descriptions apply the concept broadly to "sensitive text," not just a specific variable type like passwords, confirming any variable can be marked.

Scroll to Top