How Should ADatum Restrict Service Request Data Access?

AB-410 Last updated

Short answer

Select: (1) Assign the Service Request records to a service account and add the team member doing the verification by using an access team; (2) Assign the records to the QV team when the service request is completed.

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 address the unnecessary data access. Which security changes should you make? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Exhibit: How Should ADatum Restrict Service Request Data Access?

Key Takeaways

The test is whether you recognize that owner-team/service-account ownership plus access teams enforce least privilege, while the trap is relying on security roles or queues, which do not follow a single assigned verifier or revoke access at completion.

This ADatum case study hotspot asks which Dataverse security changes remove excess access to client data on Service Request and Qualification records. The answer is to move ownership away from broadly privileged users, grant record-level access through access teams, and reassign records to the QV team when the service request is completed.

Common mistake: The most common wrong approach is to tighten security by editing security roles or queue membership. Roles are environment-wide and queues grant access to all potential verifiers, so both keep giving more employees ongoing access to individual client information — exactly the reported issue.

Expert Analysis

Why the Answer Is Correct

The Service Request should not be owned by an individual with broad Dataverse access; ownership should sit with a service account (or an owner team acting as a passive owner), and the single team member performing the verification should be granted record-level access by adding them through an access team (access team template on the Service Request/Qualification tables). Access team membership is granted per record, so only the assigned verifier can see and process the related Qualification records, which matches the requirement that a single user processes qualifications for their own service requests. When the work is finished, the record is reassigned to the QV team, so the individual's access ends automatically — resolving the complaint that access continues after a service request is completed. The same pattern also fixes the vacation issue, because the substitute can simply be added to the access team for the specific records, inheriting visibility of all related Qualification rows.

Why Other Candidate Answers Are Wrong

Using security roles alone cannot work here because roles apply to every record of a table across the environment; the case explicitly states that Team members currently have full access to all Service Request records and that more employees than required can access client data. Using queues is also wrong for individual confidentiality: the case says all potential users performing verifications have access to queue-assigned records, so a queue grants group visibility rather than per-record least privilege. Business units or sharing with an organization-wide team reproduce the same over-exposure, and anything requiring plug-in code is invalid anyway because corporate policy prohibits power users from writing code and internal IT supplies no development resources. Owner-team assignment without access teams would leave nobody specifically authorized, which breaks the single-verifier requirement.

Community Comment Notes

A learner summarized the hotspot in two selections: "1. Assign records to a service account and add the team member doing the verification by using an access team" and "2. Assign records to the QV tam when the service request is completed." That matches the least-privilege design Microsoft documents for Dataverse access teams, where record ownership stays with a passive owner and access is granted and revoked per record as work is handed off.

Official Reference

Exam Strategy

In hotspot security items, look for least-privilege combinations: a passive owner (service account or owner team) plus per-record access teams, and a hand-off of ownership at process completion. Avoid any choice based on security roles, business units, or queues when the scenario describes access that must be limited to one assigned user and must end when work is done.

Frequently Asked Questions

Why not just restrict access with a Dataverse security role for the ADatum case study?

Security roles apply environment-wide to every record of a table, so a role cannot limit a record to its one assigned verifier. Access teams grant record-level permissions that can be added and removed per Service Request.

How do access teams fix the substitute employee problem when a verifier is on vacation?

Because access is granted per record, the substitute is simply added to the access team for the affected Service Requests and gains visibility of all related Qualification records without broadening anyone else's access.

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 👍 2
    1. Assign records to a service account and add the team member doing the verification by using an access team. 2. Assign records to the QV tam when the service request is completed.

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