PL-500 Sample Questions Answers

To configure permissions for the Purchase order quantity flow, you should assign the run-only user permission to the finance clerk. This will allow them to run the flow without being able to edit or share it1. The other permissions are not suitable for this scenario because:

Co-owner permission would give the finance clerk full access to edit, share, and delete the flow, which is not necessary or desirable1.

Owner permission would transfer the ownership of the flow to the finance clerk, which would remove your access and control over it1.

User permission would not allow the finance clerk to run the flow at all, only to view it1.

To implement security to resolve the invoice data issue, you need to perform three actions:

In Microsoft Power Platform admin center, navigate to the Security roles section. This is where you can manage the security roles for your environment and assign them to users or teams.

Select the Finance role, select Custom Entities and navigate to the table. This is where you can configure the access level for each entity in your environment based on your security role.

Clear the Create and Delete permissions. Set the Read permission and Write permission values to Business unit. This will restrict users with this role from creating or deleting records in this table, but allow them to read or write records within their business unit.

To resolve the fulfillment status flow issue, you need to perform three actions:

Ensure that all users are signed out from the target machine. This will prevent any interference or interruption from other users who might be logged in to the same machine where the desktop flow is running1.

Use different local Windows accounts for all machines. This will ensure that each machine has a unique identity and credentials for running desktop flows1.

Ensure that the flow is not using elevated privileges. This will avoid any security risks or errors that might occur when running desktop flows with administrator rights1.

To configure a flow for processing invoices that arrive in an email, you need to use three elements: document type, AI model, and form type.

Document type specifies what kind of document you want to process, such as invoices, receipts, or business cards.

AI model determines how the document data will be extracted and analyzed, such as using a prebuilt model or a custom model.

Form type defines how the extracted data will be mapped to a table in Dataverse, such as using a standard form or a custom form.

Edit the cloud flow.

Modify the Run a flow built with Power Automate for desktop action.

Set the priority value based on the volume for an order.

To implement a solution to manage the priority of incoming orders, you need to perform three actions in sequence:

Edit the cloud flow that triggers the desktop flow. This is where you can define the logic for setting the priority value based on the volume for an order1.

Modify the Run a flow built with Power Automate for desktop action in the cloud flow. This is where you can pass the priority value as a parameter to the desktop flow1.

Set the priority value based on the volume for an order in the desktop flow. This is where you can use the priority value as a dynamic content to determine how the desktop flow will run on the target machine1.

To ensure that the solution uses the correct accounts payable mailbox, you need to perform three actions:

Set the current value for the accounts payable mailbox in the environment. This will update the value of the environment variable that stores the email address of the accounts payable mailbox1.

Turn off and then turn on the cloud flows. This will refresh the cloud flows and make them use the updated value of the environment variable1.

Use one environment variable for both the cloud flows and the canvas app. This will ensure consistency and avoid duplication of data across different components of your solution1.

According to the scenario, the SMSApp data entry issue occurred after a DLP policy change that excluded the development environment from its scope. This means that any desktop flow that uses connectors in the development environment will be blocked by the DLP policy1. Therefore, the root cause of the issue is option D.

According to the scenario, the RailStatusUpdater flow sometimes fails because of network issues that prevent it from running a desktop flow on a machine. To resolve this issue, you can use one of these two methods:

Put the desktop flow action into a Do until loop that runs until the desktop flow is successful. This way, the cloud flow will retry running the desktop flow until it succeeds or reaches a maximum number of attempts.

Create a duplicate action for the desktop flow and configure the duplicate action to run if the first desktop flow action fails. This way, the cloud flow will have a second chance to run the desktop flow if the first attempt fails.

According to the scenario, the capacity planning flow fails when the gateway is offline. To avoid this issue, you can create a gateway cluster that consists of two or more gateways that share the same configuration and data sources. This way, if one gateway is offline, another gateway in the cluster can handle the requests and ensure high availability for your flow.

According to the scenario, you want to package all your automations into a single solution that can be easily deployed across environments. To do this, you need to add existing components to the solution, such as cloud flows, desktop flows, connections, and custom connectors. This way, you can bundle all your related resources into one package and export or import it as needed.

According to the scenario, PipelineManager1 is an owner of the RailStatusUpdater cloud flow. As an owner, PipelineManager1 can perform various actions on the flow, such as modifying or deleting it, viewing its run history, and adding or removing other owners. However, PipelineManager1 cannot override the DLP policy, modify the owner’s connection credentials, or set the cloud flow priority, as these actions require higher permissions or roles.

According to the scenario, the DataCollector flow sometimes fails because some fields on web pages are missing or have different attributes than expected. To resolve this issue, you can use one of these two methods:

Add an If web page contains action before each Populate text field on a web page action to determine whether a field exists on the web page and write data only when true. This way, you can avoid errors caused by missing fields.

Modify selectors for each Populate text field on a web page action to ensure that field attributes are mapped correctly and match those on web pages. This way, you can avoid errors caused by mismatched attributes.

According to the scenario, you want to run the desktop flow actions in unattended mode when the cloud flow is triggered by a schedule, and in attended mode when the cloud flow is triggered manually. To achieve this, you can create an environment variable that stores the run mode value (attended or unattended) and use it as an input for each desktop flow action. This way, you can change the run mode value dynamically without having to manually update each action.

 User 1: Share as owner

User 2: Share as co-owner

User 3: Share as run only user

According to the scenario, you want to share the MaintenanceScheduler cloud flow with three users who have different roles and permissions. To do this, you can use the following sharing methods:

Share as owner: This method allows you to add another user as an owner of the cloud flow, who can view, edit, run, and manage the flow. You can use this method to share the cloud flow with User 1, who is a senior maintenance manager and needs full access to the flow.

Share as co-owner: This method allows you to add a SharePoint list as a co-owner of the cloud flow, so that anyone who has edit access to the list also has edit access to the flow. You can use this method to share the cloud flow with User 2, who is a maintenance manager and needs to edit the flow. You can add the SharePoint list that User 2 has access to as a co-owner of the flow.

Share as run only user: This method allows you to grant run-only permissions to another user for the cloud flow, who can only run the flow manually or view its run history. You can use this method to share the cloud flow with User 3, who is a maintenance technician and needs to run the flow on demand.

No, Yes, No

According to the scenario, you are unable to save ProdManager because it uses a connection reference that is missing from ProductionMonitor. To resolve this issue, you can use the Connection References page to add the missing embedded connection references to ProductionMonitor. This way, you can ensure that both cloud flows use the same connection reference and avoid errors.

Adding the current user as a co-owner of ProductionMonitor will not resolve the issue, because co-owners cannot modify the connections or connection references used by a cloud flow. Changing the value of the Run only users setting for ProductionMonitor will also not resolve the issue, because this setting only affects how run-only users can access connections when they run a cloud flow manually.

According to the scenario, you want to configure the desktop action to run on any available machine in a machine group and to time out after 20 minutes if no machine is available. To do this, you need to select machine settings in Power Automate for desktop and choose a machine group as the target device for your desktop action. Then, you need to select the Timeout property and update the duration to PT20M, which stands for 20 minutes in ISO 8601 format. You do not need to launch Power Automate for desktop or navigate to Desktop flow action settings in the cloud flow, as these steps are not relevant for configuring the desktop action. You also do not need to select C as an answer, as P20M is not a valid ISO 8601 duration format.

Scenario A: Handle the error within the On block error or within the action. Explanation: For desktop flows, you can use the On block error option to handle errors for a group of actions or a single action within the block4. Alternatively, you can use the Configure run after option to handle errors for a single action only2.

Scenario B: Handle the error within the action only. Explanation: For desktop flows, you can use the Configure run after option to handle errors for a single action only2. This option allows you to specify what actions should run after a failure, a timeout, or a skip2. You can use this option to retry the action or perform some other logic.

Scenario C: Configure run after Explanation: For cloud flows, you can use the Configure run after option to handle errors for a single action only2. This option allows you to specify what actions should run after a failure, a timeout, or a skip2. You can use this option to update a variable or perform some other logic.