Care Staff Security Role Privileges in Contoso Model-Driven App
Short answer
Contact: no Create, Organization Read, no Write. Dog: no Create, Organization Read, Organization Write. Resident: no Create, Organization Read, no Write.
Question
DRAG DROP 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 Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs. The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created. The model-driven app uses Dataverse with out-of-the-box functionality when possible. Dataverse is set up with the following configuration: • The solution prefix “cs” is used for all new components. • Only the root business unit is used. • All tables are stored in Dataverse and do not require rapid scaling. • Exchange server-side sync is not configured. Adopters • Adopter information is stored in a Contact table. • Contacts are considered to be duplicates if they have the same email address and last name. • Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting. • The email reminders must not be tracked in the system. Dogs • Dog information is stored in a Dog table, which is organization owned. • Breed, size, and weight are fields in the table. Dog residency • A Resident table tracks the stay of each dog. • Each resident record has a lookup for the dog and its food. • The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount. • A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances. • A formula column named Deposit is automatically populated with 20% of the adoption fee. • A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created. Exercise and feedings • Exercise for the dogs is tracked in an Exercise table. • Feedings are tracked in a Feeding table. • Exercise and feeding records appear in a resident record timeline. Care staff • The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago. • The staff must be able to update the weight of a dog on the resident record. • The staff report that the buttons are too small on the touch screen they use to log exercise and feeding. • The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information. Administrative staff • Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact. • When an adopter wants to adopt a dog, the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen: o Commitment:
- Obtain adopter signature in a commitment document.
- Collect deposit.
- Document spay or neutering date.
- Perform spay or neutering.
- Document pickup date.
- Collect full payment.
- Verify dog is picked up.
Key Takeaways
The question tests Dataverse security role privilege assignment per table — the trap is granting Write on Contact (staff must not modify adopters) or overlooking that weight lives on the Dog table, requiring Write there despite updates being initiated from the Resident form.
For Contoso Suites' care staff security role, the Contact table needs Organization-level Read only (view adopters without editing), the Dog table needs Organization-level Read and Write (update the weight field), and the Resident table needs Organization-level Read only (view stays without editing).
Common mistake: Giving care staff Write access to the Contact table because they interact with adopter records, or failing to grant Write on the Dog table even though the weight field is updated from the Resident record form.
Expert Analysis
Why the Answer Is Correct
The care staff must view adopter information on upcoming meetings but cannot update it, so the Contact table receives Organization-level Read only with no Create or Write privileges. The Dog table holds the weight field that staff must update from the Resident record, so it requires Organization-level Read plus Organization-level Write privileges. The Resident table itself only needs Organization-level Read so staff can see resident details, audit food changes, and log exercise/feeding without modifying the core resident record. This least-privilege model satisfies every stated requirement without granting unnecessary access.
Why Other Candidate Answers Are Wrong
Granting Write on Contact would violate the explicit requirement that staff cannot update adopter information. Omitting Write on Dog would prevent the weight update because weight is a column on the Dog table even though the update is initiated from the Resident form. Granting Create on Resident would conflict with the case rule that resident records are generated only when a dog record is created. Organization-level Write on Contact or Resident gives far more privilege than any care staff requirement demands.
Community Comment Notes
A community member summarized the correct pattern as "1. None - Organization - None 2. None - Organization - None 3. None - Organization - Organization," matching the least-privilege assignment of Organization Read across all three tables with Organization Write only on Dog. This aligns with the case requirement to update the weight field stored on the Dog table while keeping Contact and Resident read-only for care staff. No other comments contradicted or refined this approach.
Official Reference
Exam Strategy
Map each staff requirement to a specific table and privilege before dragging: "view adopters" = Contact Read, "update weight" = Dog Write, "view resident details" = Resident Read. Always default to the least privilege that satisfies the requirement — never add Write or Create unless the scenario explicitly says the role must modify or add records.
Frequently Asked Questions
Why do care staff need Write on the Dog table if they update weight from the Resident record?
The weight field is stored as a column on the Dog table, not the Resident table. Updating it from a Resident form still requires Write privileges on Dog in the security role.
Why must the care staff Contact table privileges be Read-only?
The case requires staff to view adopter information for upcoming meetings but explicitly prohibits them from updating adopter data, so Write on Contact is excluded.
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 👍 11. None - Organization - None 2. None - Organization - None 3. None - Organization - Organization
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.