MB-910 · Question #144
A company uses Dynamics 365 Sales and Dynamics 365 Customer Service apps. Technicians doing repair work should not have access to customer orders and invoices. You need to limit the technicians…
The correct answer is C. Role-based security. To prevent technicians from accessing specific sensitive data like customer orders and invoices in Dynamics 365, the most effective security feature is role-based security.
Question
Options
- AEnvironment-level security
- BData loss prevention policy
- CRole-based security
- DRow-level security
How the community answered
(29 responses)- A14% (4)
- B7% (2)
- C76% (22)
- D3% (1)
Why each option
To prevent technicians from accessing specific sensitive data like customer orders and invoices in Dynamics 365, the most effective security feature is role-based security.
Environment-level security controls access to an entire Dynamics 365 environment but does not offer granular control over specific record types within applications for users who have environment access.
Data loss prevention (DLP) policies are designed to prevent sensitive data from being shared or exfiltrated outside the organization, not for controlling internal user access to specific record types within Dynamics 365 applications.
Role-based security in Dynamics 365 allows administrators to define security roles with precise privileges and access levels for different record types (entities). By creating a security role for technicians that specifically omits read or write privileges for the 'Order' and 'Invoice' entities, their access to customer orders and invoices can be effectively restricted.
Row-level security restricts access to individual records (rows) of data, typically based on ownership or business unit, but it is not the primary method for restricting access to entire entity types (like all orders or invoices) for a group of users.
Concept tested: Dynamics 365 Role-based security
Source: https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges
Topics
Community Discussion
No community discussion yet for this question.