Microsoft
MB-280 · Question #160
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. You enable column security on "Salesperson Commission" and "Commission Rate %" in the Opportunity table. Then, you create column security profiles for sales representative and sales manager, adding correct users to each and adding appropriate field permissions. In Dynamics 365…
Configure the security model
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result these questions will not appear in the review screen. Your organization uses Dynamics 365 Sales to manage opportunities and track sales performance. Each Opportunity record includes sensitive fields for "Salesperson Commission"' and "Commission Rate %."' You need to protect compensation data and prevent internal conflicts. The solution needs to allow sales managers to view and edit commission-related fields, while ensuring that sales representatives CANNOT see or modify data in these columns using any UI components. Solution: You implement a business rule to hide the commission fields from users who do NOT have the Sales Manager role. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(29 responses)- A28% (8)
- B72% (21)
Explanation
- You enable column security on "Salesperson Commission" and "Commission Rate %" in the Opportunity table. Then, you create column security profiles for sales representative and sales manager, adding correct users to each and adding appropriate field permissions. In Dynamics 365 Sales, Security Roles control access to entire records (like Opportunities), while Column-Level Security Profiles (Field Security Profiles) provide granular control over specific sensitive fields within those records, allowing different users to see or edit different data points on the same Opportunity. You use roles for broad access and profiles for fine-tuning sensitive data access (e.g., restricting revenue fields). * You create role-based security roles to restrict access to the Opportunity table for sales * You implement a business rule to hide the commission fields from users who do NOT have the Sales Manager role. Hiding fields is not secure enough. * You update column-level audit settings on the "Salesperson Commission" and "Commission Rate %" columns on the Opportunity table. Auditing does not help with field security.
Topics
#field-level security#opportunity#sensitive fields#security roles
Community Discussion
No community discussion yet for this question.