How Should You Auto-Create Evaluation Records for a Prospect?

Answer Correct answer: B — Use a cloud flow to automatically create the evaluation record for the prospect without any custom code.

This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question. Background - Bellows College is a post-secondary school that wants to start a football team. The college uses Microsoft Power Platform to manage its recruiting efforts. The registration team and assistants use model-driven apps. The coaches use canvas apps on their mobile devices. Prospects are considered underage if they are younger than 18 years old at the time of registration. Current environment - Environment - • Custom code is not allowed in the system. • Server-side synchronization is configured for emails, appointments, contacts, and tasks. • The database and file storage of Dataverse must be minimized to keep costs low. Contact table - • Birthdate is a custom date and time field. • Age at Registration is a calculated field that displays the age of the prospect at the time of registration. • Current Age is a calculated field that displays the age of the prospect based on the current date and time. Evaluation table - • The Evaluation table is a custom table used to track evaluation criteria. • Evaluation records cannot be manually created. • Users must not be able to continue until an evaluation record is created automatically for the prospect. Consent table - • The consent forms completed by the parents are stored as records in the Consent table. • Occasionally, a parent cannot complete the consent online and a paper copy must be printed. The signed copy must be scanned and stored with the consent record. Team website - • The team website is created by using Power Pages. • A starter layout template was used to create the site. • The site consists of five pages: o Home: A page open to everyone to view the announcements from the team. o Schedule: A page open to everyone to view the tryout and game schedule. o Evaluations: A page that displays tracking from the evaluation table. Prospects are able to view their own information only. o Forms: A page that displays the consent form. o Contact Us: A page for anyone to submit questions and comments. • Two web roles for authenticated users are created: Primary Contact User and Prospect User. o All primary contacts and prospects are assigned to their respective roles. Requirements - Registration - • Parents and prospects are created as contacts and must be linked. • The registration team must be able to rapidly create prospects without navigating away from the Parents form. Only the First Name, Last Name, and Birthdate fields should be displayed for the team. • Assistants must be able to update prospect information and add teams that the prospect has previously played on to a subgrid. Parental consent - • When a prospect is underage, a Primary Contact field will appear. The field must be populated before the prospect record can be saved. • A view named Underage Prospects that lists all underaged prospects is required. • The Underage Prospects view must run once a week without requiring modifications to display correct information. • A consent email must meet the following requirements: o be sent to the primary contact of each new underage prospect o contain a link to the team website o be automatically sent weekly and tracked to the contact record in Dataverse o include the current date using the full month name, date, and year Evaluations - • Coaches rate prospects each day on a scale of 1-10 in three categories: endurance, coordination, and skill. • The total of the three categories is displayed at the bottom of the form. If the total for the day is greater than 25, the number should appear green. You need to create the evaluation record for a prospect. What should you use?

  1. a classic Dataverse workflow
  2. a cloud flow Correct Answer
  3. a plug-in
  4. a quick create form

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

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.

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.

Community Discussion (3 comments)

Evan123123 👍 14 Selected: 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 👍 5
was on test May 14 2024 went with cloud flow Scored 866
3gle 👍 2 Selected: A
I 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.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

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

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?

Classic workflows are legacy, and Power Automate cloud flows are the recommended no-code automation for Dataverse; cloud flows also integrate more easily with the coaches' canvas apps.

Why is a plug-in wrong for creating the Evaluation record?

Plug-ins are compiled C# code, and the case study states custom code is not allowed. They also cannot be created without a developer deployment.

Why is a quick create form not the answer?

The Evaluation table explicitly states records cannot be manually created, and a quick create form only supports manual entry by a user.

Related Analysis

← Back to PL-200 Study Guide