PL-500 · Question #3
Case Study 1: Contoso Pharmaceuticals Background: Contoso Pharmaceuticals distributes specialty pharmaceuticals, ingredients, and raw materials throughout North America. The company has 33 offices and
The correct answer is A. Clear the Create and Delete permissions. Set the Read permission and Write permission values B. Select the Finance role, select Custom Entities and navigate to the table. D. In Microsoft Power Platform admin center, navigate to the Security roles section.. This question tests configuring a Dataverse security role to grant Finance clerks read and write access to a custom table without create or delete permissions.
Question
Options
- AClear the Create and Delete permissions. Set the Read permission and Write permission values
- BSelect the Finance role, select Custom Entities and navigate to the table.
- CIn Microsoft Power Platform admin center, navigate to the Users section.
- DIn Microsoft Power Platform admin center, navigate to the Security roles section.
- EClear the Create and Delete permissions. Set the Read permission and Write permission values
- FSelect the Finance role select Core Records, and then navigate to the table.
How the community answered
(41 responses)- A83% (34)
- C2% (1)
- E5% (2)
- F10% (4)
Why each option
This question tests configuring a Dataverse security role to grant Finance clerks read and write access to a custom table without create or delete permissions.
Clearing Create and Delete permissions while retaining Read and Write precisely scopes the Finance role to view and edit records without allowing data destruction or new record creation, matching the least-privilege requirement for clerks.
Custom tables created for the solution appear under the Custom Entities category in the security role editor, so navigating there is the correct path to find and configure the target table.
Navigating to the Users section only manages user assignments to roles, not the permission definitions within a role itself.
Security roles are managed under the Security roles section of the Power Platform admin center environment settings, which is the authoritative location for role configuration.
This is a duplicate of choice A and does not introduce a distinct configuration step; the correct ordering of steps requires navigating to the role and entity first.
Core Records contains standard Dataverse system tables such as Account and Contact, not custom application tables, so navigating there would not expose the target table.
Concept tested: Dataverse security role custom entity permissions
Source: https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges
Topics
Community Discussion
No community discussion yet for this question.