How Should You Auto-Create Evaluation Records for a Prospect?
Short answer
B Use a cloud flow to automatically create the evaluation record for the prospect without any custom code.
Question
Key Takeaways
The question tests picking a no-code automation mechanism when the environment bans custom code; the common trap is choosing a real-time classic workflow or a plug-in for server-side record creation that Power Automate cloud flows handle.
Bellows College requires evaluation records to be created automatically for each prospect in Dataverse while custom code is prohibited. This page establishes that a cloud flow (B) is the correct automation tool, since plug-ins need compiled code, quick create forms expect manual entry, and classic workflows are legacy.
Common mistake: The most common wrong answer is a classic Dataverse workflow (A), because learners assume synchronous real-time behavior is mandatory, but classic workflows are deprecated and Power Automate cloud flows are the recommended no-code automation in PL-200 scenarios.
Expert Analysis
Why the Answer Is Correct
Cloud flows in Power Automate are the standard no-code automation option in Power Platform, and they can be triggered by Dataverse events or invoked directly from a canvas app to create a child Evaluation record for a prospect. The case study explicitly states that custom code is not allowed, which keeps the solution inside the maker toolset that cloud flows support. The Evaluation table notes records cannot be manually created, so the automation must fire without a user opening a create form. Because coaches already use canvas apps on mobile devices, a cloud flow can be called with the Power Apps trigger and return control only after the Evaluation record exists, satisfying the rule that users must not continue until an evaluation record is created. Cloud flows also log run history in Dataverse and require no compiled plug-in assembly.
Why the Other Options Are Wrong
A classic Dataverse workflow technically runs server-side, but classic workflows are legacy and are not the recommended choice in PL-200 scenarios where Power Automate cloud flows provide the same trigger-and-action model with far better canvas-app integration. A plug-in is written in C# and deployed as a compiled assembly, which directly violates the stated constraint that custom code is not allowed in the system. A quick create form is a UI component for manual record entry, and the Evaluation table explicitly states that records cannot be manually created. None of these three options satisfies both the no-code and automatic-creation requirements of this case study.
Community Comment Notes
Evan123123 summarized the elimination logic cleanly: custom code removes a plug-in, automatic creation removes quick create, and "Dataverse workflow may work, but would be difficult to obtain the data the coach has entered in the canvas application," leaving a cloud flow. b304b2c reported sitting the exam in May 2024 and "went with cloud flow" while scoring 866, which supports the cloud-flow verdict. 3gle preferred a real-time classic workflow because users must not continue before the record exists, but admitted "Maybe I am missing something" — the synchronous requirement can still be met by invoking a cloud flow from the canvas app. No commenter who chose another option offered evidence that plug-ins or quick create forms are permitted here.
Official Reference
- https://learn.microsoft.com/en-us/power-automate/overview-cloud
- https://learn.microsoft.com/en-us/power-apps/developer/data-platform/plug-ins
These links open the official vendor documentation in a new tab.
Exam Strategy
When a case study bans custom code and requires automatic record creation, immediately eliminate plug-ins and manual-form options. Then prefer cloud flows over classic workflows, because Microsoft positions Power Automate as the recommended no-code automation for Dataverse and PL-200 answers reflect that.
Frequently Asked Questions
Why can't a classic Dataverse workflow create the Evaluation record?
Why is a plug-in wrong for creating the Evaluation record?
Why is a quick create form not the answer?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 3 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 3
-
Evan123123 👍 14 Answered B- Custom code is off the table, so that removes plug-in as an option. - Requirements state that a record needs to be created automatically and not by a user, this removes quick create as an option - Dataverse workflow may work, but would be difficult to obtain the data the coach has entered in the canvas application. Leaving cloud flow as the only valid solution.
-
b304b2c 👍 5was on test May 14 2024 went with cloud flow Scored 866
-
3gle 👍 2 Answered AI would go with real-time wf as it is mentioned that users must not be able to continue until evaluation is created for a prospect. And I don’t see why it should be an asynch job. As the prospects are in dataverse, it should not be an issue to trigger a wf and create a child evaluation record for that prospect. Maybe I am missing something.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.