How should the Service Request–Qualification relationship be updated?

AB-410 Last updated

Short answer

Set the relationship from Service Request to Qualification as 1:N with cascade behavior Cascade All, so reassigning the parent also transfers all related Qualification records.

Question

HOTSPOT 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 resolve the issue reported by substitute employees after they are assigned service requests. How should you update the relationship? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Exhibit: How should the Service Request–Qualification relationship be updated?

Key Takeaways

The item tests Dataverse relationship cardinality plus cascading behavior on the Assign event; the trap is choosing a parent-restricting option such as Cascade None or Cascade User, which leaves substitutes without access to child Qualification rows.

This AB-410 case study hotspot asks how the Service Request to Qualification relationship must be changed so substitute users can see all related qualification records after reassignment. The correct configuration is a 1:N (one-to-many) relationship from Service Request to Qualification whose cascade (assign) behavior is set to Cascade All.

Common mistake: Learners pick a non-cascading or owner-scoped cascade option (Cascade None, Cascade Active, or Cascade Owner), reasoning that security should be tight. That fails the scenario because ownership of the parent Service Request changes to the substitute while the child Qualification records retain the original owner, so the substitute still cannot open them.

Expert Analysis

Why the Answer Is Correct

The scenario describes a classic parent-to-child ownership gap: when a primary user goes on vacation, the parent Service Request is reassigned to a substitute, but the child Qualification records keep the old owner, so "substitute employees are unable to see all the qualifications related to their service requests." In Dataverse, Service Request to Qualification is inherently a one-to-many relationship — one Service Request has one or many Qualification records — so the first selection must be 1:N with Service Request as the parent. Setting the Assign cascade behavior to Cascade All propagates the parent's ownership change to every related Qualification record, immediately transferring visibility and access rights to the substitute while preserving the requirement that Qualification records stay linked to a single Service Request.

Why Other Candidate Answers Are Wrong

Choosing N:1 (or M:N) reverses the parent-child roles and contradicts the stated data model, where a Service Request can have one or many Qualification rows — a many-to-one or many-to-many structure cannot support cascading ownership at all. Cascade None leaves the children untouched, which is precisely the reported defect being asked to fix. Cascade Active and Cascade Owner restrict or scope the propagation so that not all related Qualification records are handed to the substitute, and Cascade User/Cascade User-Owned would break the requirement that only the assigned QV team member processes the qualifications. Any option that does not propagate the full assign action leaves the substitute without the child records the case study demands they be able to see.

Community Comment Notes

The single community comment states the configuration plainly: "1. Service request 1:N Qualification 2. Cascade All," which matches the Dataverse behavior described in Microsoft's relationship documentation. There were no votes recorded for this item, so the comment carries no majority weight and stands only as corroboration of the technical answer. Readers should still verify the reasoning against the parent-child ownership model rather than relying on a lone anonymous post.

Official Reference

Exam Strategy

When a hotspot asks about a relationship, first identify the parent table (the one that owns the scenario) and set the cardinality accordingly, then pick the cascade option that directly satisfies the stated business defect. In this case the defect is lost visibility after reassignment, which maps exactly to Cascade All on the Assign event.

Frequently Asked Questions

Why can't substitute users see Qualification records after they are assigned a Service Request?

Because only the parent Service Request was reassigned; without a cascading assign behavior, the child Qualification records keep the original owner's access and remain hidden from the substitute.

Which relationship type should connect Service Request and Qualification in Dataverse?

A 1:N (one-to-many) relationship, with Service Request as the parent and Qualification as the child, since one Service Request can have many Qualification records.

More AB-410 FAQ →

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

  1. exam_upskill 👍 1
    1. Service request 1:N Qualification 2. Cascade All

Reader comments & corrections

No reader corrections 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.

← Back to AB-410 Study Guide