nerdexam
Microsoft

PL-500 · Question #130

You are developing a Power Automate desktop flow to process new employee documentation. The flow has a variable for confidential bank account numbers. Users are able to view bank account numbers…

The correct answer is B. Mark the variable as sensitive. In Power Automate desktop flows, marking a variable as sensitive hides its value from the variable panel and run logs, preventing confidential data from being exposed during testing.

Develop automations

Question

You are developing a Power Automate desktop flow to process new employee documentation. The flow has a variable for confidential bank account numbers. Users are able to view bank account numbers while the flow is tested. You need to ensure the bank account numbers are not visible in the flow. What should you do?

Options

  • ATurn on Secure Inputs in a cloud flow.
  • BMark the variable as sensitive.
  • CChange the external name.
  • DMark variables produced as disabled.

How the community answered

(41 responses)
  • A
    5% (2)
  • B
    93% (38)
  • C
    2% (1)

Why each option

In Power Automate desktop flows, marking a variable as sensitive hides its value from the variable panel and run logs, preventing confidential data from being exposed during testing.

ATurn on Secure Inputs in a cloud flow.

Secure Inputs is a setting available on cloud flow actions that masks action input data in run history, but it is not a feature of Power Automate desktop flow variables.

BMark the variable as sensitive.Correct

Marking a variable as sensitive in Power Automate desktop causes the runtime to mask the variable's value in the flow designer, variable viewer, and run log output, ensuring bank account numbers and other confidential data cannot be seen by users monitoring or testing the flow.

CChange the external name.

Changing a variable's external name only alters the display label shown to the user and has no effect on masking or hiding the variable's actual value.

DMark variables produced as disabled.

Marking variables produced as disabled suppresses the output capture of a specific action step but does not secure or mask the value of a named variable used elsewhere in the flow.

Concept tested: Power Automate desktop sensitive variable data masking

Source: https://learn.microsoft.com/en-us/power-automate/desktop-flows/manage-variables

Topics

#Power Automate Desktop#Sensitive Data#Variable Management#Flow Security

Community Discussion

No community discussion yet for this question.

Full PL-500 Practice