Sampling 10% of Qualification Rows with an Autonumber and Cloud Flow
Short answer
C Create an autonumber column on the Qualification table and have the Power Automate flow assign qualification rows to the QV queue when the number cleanly divides by 10.
Question
This is a case study. Case studies are not timed separately from other exam sections. You can use as much exam time as you would like to complete each case study. However, there might be additional case studies or other exam sections. Manage your time to ensure that you can complete all the exam sections in the time provided. Pay attention to the Exam Progress at the top of the screen so you have sufficient time to complete any exam sections that follow this case study. To answer the case study questions, you will need to reference information that is provided in the case. Case studies and associated questions might contain exhibits or other resources that provide more information about the scenario described in the case. Information provided in an individual question does not apply to the other questions in the case study. A Review Screen will appear at the end of this case study. From the Review Screen, you can review and change your answers before you move to the next exam section. After you leave this case study, you will NOT be able to return to it. To start the case study To display the first question in this case study, select the “Next” button. To the left of the question, a menu provides links to information such as business requirements, the existing environment, and problem statements. Please read through all this information before answering any questions. When you are ready to answer a question, select the “Question” button to return to the question. Background ADatum Corporation provides verification and investigation services that are used by insurance companies, law firms, and other organizations in the public sector. Services include verifying an individual’s background, qualifications, and specific scenarios that require onsite visits. The thorough work ADatum Corporation performs results in highly accurate cases with minimal critical information missing. Because of these high-quality results, ADatum Corporation is quickly proving itself as one of the best in the industry. In recent months, business has significantly increased, with most new business coming from high-profile companies and individuals. Management has decided to create a new qualification verification (QV) role to help ensure that clients get the most accurate results. This role examines completed work to ensure that nothing is missed. Current environment Data storage and retention • All information sent by clients for services is stored in Microsoft Dataverse with a model-driven app as the interface. • Clients enter their data in a website, which then uses a service account to create the records in the Dataverse database. • Team members currently have full access to all Service Request records. Service requests • The Service Request table includes header information about the individual or organization that is the subject of verification. • New Service Request records are assigned to a queue. All potential users who will be performing the verifications have access to these records. • A service request is assigned to a single user who will ensure that all qualifications are verified. This single user is the only one able to process Qualification records related to their own service requests. • Many required tasks when performing verification services are currently done by using manual processes. • To keep up with demand, ADatum Corporation identifies several processes that can be replaced by using Power flows to hire fewer new staff and keep costs down. Qualification verification • The qualification table contains details about an individual school degree, professional qualifications, and other qualifications that must be verified. • A service request can have one or more Qualification records associated with it. • Record status is pending verification until the initial team member finishes, at which point the member changes the status to Complete. • When all qualification records related to a service request are verified either by manual or automated processes, the results are made available to ADatum Corporation’s client. • In the rare event that results are questioned, a new service request is created and verified independently of the previous work that took place. • To complete a service request, users perform the following actions: o Send a templated email by using Microsoft Outlook to the client after all qualifications for a service request are checked. o Change the service request status to Completed. Currently, service requests do not indicate when all Qualification records are addressed. Microsoft Power Platform environment • The following environments exist: development, testing, user acceptance testing (UAT), and production. • Managed solutions are used to move customizations from the development environment to other higher-level environments. These solutions are created and maintained by the power users and provided to internal IT for deployment when they are ready. • Two managed solutions, Verification Process Automation and Onsite Visit, share several components. • All customizations to Power Platform components are performed by several power users who have received training and are certified as subject matter experts. • Power users have been granted the System Administrator security role in the development environment. • Corporate policy prohibits power users from writing code due to lack of a formal code review process. • Internal IT will not be able to supply any development resources for this project due to a lack of staff. This means that any customizations and automation created for this project must be low-code/no-code for the power users to implement them. • Customizations created by power users are deployed by internal IT. Requirements Process automation ADatum Corporation plans to establish a new QV department to verify completed work so that the quality of work is maintained. The new process for verifying professional qualifications must automate the following: • Enter data and navigate the authority’s website. The authority website UI changes frequently because the company constantly improves the user experience. • Search page contents for a specified value to determine validity. • Update the corresponding Qualification record in Dataverse. The new process for completing a service request must automate the following: • Set the Service Request record status to Complete when work on all Qualification records is finished. • Send an email to the client with the results when the service request is completed. The email must list each qualification as either Valid or Not Valid, depending on the verification. Qualification verification • Service request results will not be released to clients until all related Qualification records are set to a Complete status. • To check work done by a wide array of users, 10 percent of Qualification records must be double checked. • Qualification records must be automatically assigned to a queue. • Qualification records must be flagged with a new status field named Assigned to ensure that records are rechecked. • Ensure that only QV team members can change the status from Assigned to In Progress to Complete. • Record the name of the QV team member who performed the work and the date completed. Governance and security • All components required for the verification process must be included in a new solution. • Corporate security requires that deployments to non-development environments must be automated using service accounts. • User security and data access must also be consistent across environments, except for the elevated access of the power users in the development environment. • The Onsite Visit managed solution has a table that is not in the Verification Process Automation managed solution. This table must be upgraded prior to the go-live date without the other shared components. • A VP of sales requires a test environment to demonstrate to potential clients the security policies that are included in their initial offering. Issues • More employees than are required can access individual client information and continue to have access after a service request is completed. • When users go on vacation, all their outstanding Service Request records are assigned to a substitute employee. The substitute employees are unable to see all the qualifications related to their service requests. • Currently, testing the new QV functionality outside the development environment is not possible due to corporate security policies requiring the same security role across all environments. • Internal IT reports that the solution import to the test environment failed because of missing dependencies related to the flow for completing service requests. You need to assign 10 percent of the Qualification rows to the QV queue through table configuration by using a Power Automate flow. What should you do?
Key Takeaways
The question tests how to implement a 10 percent sampling rule with Dataverse table configuration and a cloud flow; the trap is assuming you need random-number generation or a roll-up/formula column on the parent Service Request table.
ADatum needs to randomly sample 10 percent of Qualification records for double-checking by the QV team using table configuration plus a Power Automate flow. The correct approach is an autonumber column on the Qualification table, with the flow assigning any row whose number cleanly divides by 10 — giving a deterministic one-in-ten sample.
Common mistake: Option D is the popular wrong pick: a Dataverse rollup column can only aggregate (count, sum, min, max, avg) over a related table — it cannot generate a random number, and the randomness is unnecessary because the autonumber sequence itself provides the spread across rows.
Expert Analysis
Why the Answer Is Correct
Option C creates an autonumber column directly on the Qualification table, so every qualification row receives a sequential identifier. A Power Automate flow (or a condition evaluated on that column) can then flag and route to the QV queue any row whose autonumber cleanly divides by 10 — statistically distributing roughly 10 percent of rows across the whole table, independent of which Service Request they belong to. This satisfies the requirement to "assign 10 percent of the Qualification rows to the QV queue through table configuration," because the autonumber is a native Dataverse column property (table configuration) and the assignment is executed by a flow. It also keeps the solution low-code/no-code, which corporate policy requires since power users cannot write code.Why the Other Options Are Wrong
Options A, B, and D all place the sampling logic on the Service Request table, but the requirement is to sample Qualification rows, not service requests. In A, a Service Request autonumber divided by 10 would select entire service requests for double-checking, not a 10 percent sample of their qualification rows. In B, a formula column that "generates a random number" is not a realistic Dataverse configuration — calculated/formula columns cannot call a random function, and evaluating against the Service Request row does not sample the qualification rows. In D, rollup columns only aggregate related records (count, sum, min, max, average) on a schedule; they cannot generate random numbers, so the described configuration is not possible in Dataverse.Community Comment Notes
A lone community comment argues for option D, reasoning that a rollup column counts qualification rows and a random number is generated and compared to 10 percent of that value. That configuration is technically impossible: rollup columns support only count/sum/min/max/average aggregations, with no random-number capability, and the sampling must occur on the Qualification table rather than on the Service Request header. The autonumber approach in option C is the standard answer for this ADatum case study and is fully implementable with native table configuration plus a cloud flow.Official Reference
Exam Strategy
When a question says the sampling or decision must be done "through table configuration," look for a native Dataverse column property (autonumber, rollup, calculated/formula) rather than a flow-generated value. Then verify the column sits on the table being sampled — here the Qualification table, not the Service Request header.
Frequently Asked Questions
Why can't a rollup column on the Service Request table be used for 10 percent sampling?
Rollup columns only aggregate related records using count, sum, min, max, or average — they cannot generate a random number, and the sampling must target Qualification rows, not service request headers.
Why does an autonumber that divides by 10 give a 10 percent sample?
Sequential autonumbers distribute evenly across the table, so exactly one in every ten values is divisible by 10, producing a consistent 10 percent sample of Qualification rows for QV double-checking.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded.
From public community threads 1
-
exam_upskill 👍 1 Answered DD. Create a roll-up column on the Service Request table that is the count of qualification rows and generates a random number between zero and the number from the new column. Configure the Power Automate flow to assign each qualification row if the number generated is 10 percent or less of the value of the new column.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.