A classic Dataverse workflow that runs on create of the Opportunity record is not sending the expected email. You have verified that the workflow is activated and the trigger is correct. You need to determine whether the workflow actually ran and, if so, what happened during execution. What should you do?

Re-run the workflow manually and observe the result.

Open the workflow definition and review the 'Process Session' records.

Check the email activity records to see if an email was created.

Review the audit history of the Opportunity record.

A large enterprise has a classic Dataverse workflow that runs on every update to the 'Opportunity' table. The workflow updates a rollup field on the parent account. The workflow is causing performance degradation during peak hours. The admin is considering converting it to a real-time workflow. What is the best recommendation?

Use a real-time workflow for the update and a background workflow for the rollup calculation.

Convert to a real-time workflow to ensure the rollup is updated immediately.

Disable the workflow and use a calculated field for the rollup.

Keep it as a background workflow but change the trigger to only run on specific fields that affect the rollup.

You are designing a classic Dataverse workflow that runs on update of the Account entity. The workflow should update the 'SLA' field to 'Gold' if the Account's 'Annual Revenue' is greater than $1,000,000, and to 'Silver' if it is between $500,000 and $1,000,000. If the Annual Revenue is below $500,000, the workflow should not update the SLA field. You have added a condition to check if Annual Revenue is greater than $1,000,000. What is the most efficient way to implement the remaining logic?

Use a 'Wait' condition to pause the workflow until the Annual Revenue is confirmed.

Add two separate conditions after the first condition, one for Silver and one for no update.

Use a single condition that checks if Annual Revenue is greater than $500,000 and update SLA to 'Silver' for all accounts above that threshold.

Add a second condition in the false branch to check if Annual Revenue is greater than or equal to $500,000, and update SLA to 'Silver' in that branch.

Which of the following is a recommended technique to improve the performance of a classic Dataverse workflow?

Use the 'Reuse' option to avoid duplicate steps

Use synchronous execution for all workflows

Microsoft Certified:Power Platform Functional Consultant Associate

Domain 3Objective 3

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

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 6–10

6application · medium
A classic Dataverse workflow that runs on create of the Opportunity record is not sending the expected email. You have verified that the workflow is activated and the trigger is correct. You need to determine whether the workflow actually ran and, if so, what happened during execution. What should you do?
Select an answer first
7expert · hard
A large enterprise has a classic Dataverse workflow that runs on every update to the 'Opportunity' table. The workflow updates a rollup field on the parent account. The workflow is causing performance degradation during peak hours. The admin is considering converting it to a real-time workflow. What is the best recommendation?
Select an answer first
8expert · hard
You are designing a classic Dataverse workflow that runs on update of the Account entity. The workflow should update the 'SLA' field to 'Gold' if the Account's 'Annual Revenue' is greater than $1,000,000, and to 'Silver' if it is between $500,000 and $1,000,000. If the Annual Revenue is below $500,000, the workflow should not update the SLA field. You have added a condition to check if Annual Revenue is greater than $1,000,000. What is the most efficient way to implement the remaining logic?
Select an answer first
9foundation · easy
Which of the following provides a detailed log of a classic Dataverse workflow's execution, including each step and its outcome?
Select an answer first
10foundation · easy
Which of the following is a recommended technique to improve the performance of a classic Dataverse workflow?
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 2)

Questions 6–10

Which of the following provides a detailed log of a classic Dataverse workflow's execution, including each step and its outcome?

Which of the following is a recommended technique to improve the performance of a classic Dataverse workflow?

Keep studying — Create and manage logic and process automation