You have a classic Dataverse workflow that runs on update of the Account entity. The workflow performs a calculation and then updates the Account's 'Credit Limit' field. The workflow is triggered on every update, even when the fields used in the calculation have not changed. This is causing performance issues. What is the most effective way to improve the workflow's performance?

Change the workflow to run on demand and manually trigger it after each update.

Increase the workflow's timeout value to allow more time for execution.

Use a real-time workflow instead of a background workflow.

Add a condition that checks whether any of the fields used in the calculation are in the 'Fields that changed' list.

You are designing a classic Dataverse workflow that updates a custom entity record and then sends an email to the record owner. You want to ensure that if the email step fails, the workflow still completes successfully and the record update is not rolled back. What should you configure?

Set the workflow's 'On Error' behavior to 'Continue' and place the email step in a separate child workflow.

Use a 'Wait' condition after the email step to pause the workflow until the email is confirmed sent.

Wrap the email step in a condition that checks a flag field, and set the flag to false if the email fails.

Add a condition before the email step to check if the owner has an email address, and only send the email if they do.

A classic Dataverse workflow is running slower than expected. The admin wants to identify which step is taking the most time. What should the admin do?

Enable 'Step Duration' logging on the workflow.

Review the 'Process Session' record and look at the 'Duration' field.

Review the 'Process Logs' related to the Process Session, which include timestamps for each step.

Use the 'Workflow Performance Report' from the Power Platform admin center.

Where can you view the status of a classic Dataverse workflow that has run?

The System Jobs area in the Power Platform admin center

The Solution Explorer's Workflow list

Microsoft Certified:Power Platform Functional Consultant Associate

Domain 3Objective 3

Create and Manage Classic Dataverse Workflows PL-200 Practice Questions (Page 5)

Part of the Create and manage logic and process automation domain, which accounts for 25–30% of the PL-200 exam. Microsoft does not publish an official question count, but from its 100-minute exam (~40–65 total, ~10–20 in this domain), expect 3–5 from this objective — we provide 30 practice questions to prepare you well beyond it. (estimate)

30questions here

6free pages

8concepts

25–30%of the exam

Questions 21–25

21application · medium
You have a classic Dataverse workflow that runs on update of the Account entity. The workflow performs a calculation and then updates the Account's 'Credit Limit' field. The workflow is triggered on every update, even when the fields used in the calculation have not changed. This is causing performance issues. What is the most effective way to improve the workflow's performance?
Select an answer first
22application · medium
You are designing a classic Dataverse workflow that updates a custom entity record and then sends an email to the record owner. You want to ensure that if the email step fails, the workflow still completes successfully and the record update is not rolled back. What should you configure?
Select an answer first
23foundation · easy
Which feature in a classic Dataverse workflow allows you to define a separate set of steps to run when an error occurs?
Select an answer first
24application · medium
A classic Dataverse workflow is running slower than expected. The admin wants to identify which step is taking the most time. What should the admin do?
Select an answer first
25foundation · easy
Where can you view the status of a classic Dataverse workflow that has run?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PL-200

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “PL-200” is a trademark of its owner, used for identification only.

Create and Manage Classic Dataverse Workflows PL-200 Practice Questions (Page 5)

Questions 21–25

You are designing a classic Dataverse workflow that updates a custom entity record and then sends an email to the record owner. You want to ensure that if the email step fails, the workflow still completes successfully and the record update is not rolled back. What should you configure?

Which feature in a classic Dataverse workflow allows you to define a separate set of steps to run when an error occurs?

A classic Dataverse workflow is running slower than expected. The admin wants to identify which step is taking the most time. What should the admin do?

Where can you view the status of a classic Dataverse workflow that has run?

Keep studying — Create and manage logic and process automation