You have a classic Dataverse workflow that runs on create of the Order entity. The workflow performs a series of updates to the Order and related records. You are experiencing performance issues because the workflow is running synchronously and blocking the create operation. You need to reduce the impact on the user experience while still ensuring the workflow completes. What should you do?

Use a child workflow to perform the updates, but keep the parent workflow in 'Real-time' mode.

Change the workflow's execution mode to 'Background' instead of 'Real-time'.

Keep the workflow in 'Real-time' mode but reduce the number of steps.

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

A classic Dataverse workflow fails to run. Which of the following is a common first step to diagnose the issue?

Disable and re-enable the workflow

Check the System Job record for the workflow

Check the workflow's owner permissions

Rebuild the workflow from scratch

A classic Dataverse workflow that runs on create of the Contact entity is failing with the error: 'The workflow could not be started because the process is not activated.' You have verified that the workflow is activated. What is the most likely cause of this error?

The workflow is a child workflow that is not activated.

The workflow is set to run on demand and cannot be triggered automatically.

The workflow is using a real-time execution mode that is not supported for the entity.

The workflow's scope is set to 'User' and the triggering user does not have permission to run workflows.

Your organization uses a classic Dataverse workflow on the Account entity. When an Account is created, the workflow should send an email to the primary contact and also create a follow-up task assigned to the Account's owner. You have already configured the email step and the task creation step. However, the email should only be sent if the primary contact's email address is not blank. What is the most efficient way to implement this requirement within the workflow?

Add a condition after the email step that checks if the email was sent successfully, and create the task only if it was.

Create a separate workflow for the email and another for the task, both triggered on create.

Add a condition before the email step that checks if the primary contact has an email address, and place the email step inside the true branch.

Configure the email step to use a 'Send Email' action and set the recipient to the primary contact, but leave the email address blank.

What is the benefit of setting a classic Dataverse workflow to run in the background (asynchronously)?

It ensures the workflow runs immediately

It allows the workflow to run on a schedule

It reduces the impact on the user's experience

It guarantees the workflow will run faster

Microsoft Certified:Power Platform Functional Consultant Associate

Domain 3Objective 3

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

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 11–15

11expert · hard
You have a classic Dataverse workflow that runs on create of the Order entity. The workflow performs a series of updates to the Order and related records. You are experiencing performance issues because the workflow is running synchronously and blocking the create operation. You need to reduce the impact on the user experience while still ensuring the workflow completes. What should you do?
Select an answer first
12foundation · easy
A classic Dataverse workflow fails to run. Which of the following is a common first step to diagnose the issue?
Select an answer first
13expert · hard
A classic Dataverse workflow that runs on create of the Contact entity is failing with the error: 'The workflow could not be started because the process is not activated.' You have verified that the workflow is activated. What is the most likely cause of this error?
Select an answer first
14application · medium
Your organization uses a classic Dataverse workflow on the Account entity. When an Account is created, the workflow should send an email to the primary contact and also create a follow-up task assigned to the Account's owner. You have already configured the email step and the task creation step. However, the email should only be sent if the primary contact's email address is not blank. What is the most efficient way to implement this requirement within the workflow?
Select an answer first
15foundation · easy
What is the benefit of setting a classic Dataverse workflow to run in the background (asynchronously)?
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 3)

Questions 11–15

A classic Dataverse workflow fails to run. Which of the following is a common first step to diagnose the issue?

A classic Dataverse workflow that runs on create of the Contact entity is failing with the error: 'The workflow could not be started because the process is not activated.' You have verified that the workflow is activated. What is the most likely cause of this error?

What is the benefit of setting a classic Dataverse workflow to run in the background (asynchronously)?

Keep studying — Create and manage logic and process automation