Drag and Drop Question You are implementing Dynamics 365 Sales at a new organization. All users will be using the Sales Hub app. You need to assign the appropriate out-of-the-box security roles…

The correct answer is Salesperson; Sales team member; Sales manager. Dynamics 365 Sales: Security Role Assignment (Least Privilege) Context This question tests your knowledge of Dynamics 365 Sales out-of-the-box (OOB) security roles and the principle of least access - give each user only the minimum permissions required for their job function…

Configure the security model

Question

Drag and Drop Question You are implementing Dynamics 365 Sales at a new organization. All users will be using the Sales Hub app. You need to assign the appropriate out-of-the-box security roles. Using the principle of least access, which roles should you assign? To answer, move the appropriate roles to the correct users. Each role may be used once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:

Exhibit

Answer Area

Drag items

SalespersonSales managerSales team memberVice president of sales

Correct arrangement

Salesperson
Sales team member
Sales manager

Explanation

Dynamics 365 Sales: Security Role Assignment (Least Privilege)

Context

This question tests your knowledge of Dynamics 365 Sales out-of-the-box (OOB) security roles and the principle of least access - give each user only the minimum permissions required for their job function.

The three user positions map to three progressively capable roles:

Role-by-Role Breakdown

Position 1 → Salesperson

The Salesperson role grants full CRUD access to core sales entities (leads, opportunities, contacts, accounts, activities) scoped to the user's own records. This is the baseline role for anyone actively running a sales cycle.

Why this placement: A standard sales rep needs to create and manage their own pipeline - no more, no less. Assigning Sales Manager here would grant unnecessary access to other users' records, violating least privilege.

Position 2 → Sales team member

This is the most restricted of the sales roles. It allows users to view shared records and perform limited actions, but cannot own or manage the full sales process. Designed for peripheral team members (e.g., someone logging support calls or viewing shared contacts).

Why this placement: This user has a support/limited role and doesn't need to own leads or opportunities. Assigning Salesperson would over-provision them.

Common misconception: Many assume "team member" is just a slightly restricted Salesperson. It's significantly more limited - it's closer to read + light interaction than full sales ownership.

Position 3 → Sales manager

The Sales Manager role extends the Salesperson role with team-level access - visibility into records owned by subordinates, approval capabilities, and team dashboards.

Why this placement: A manager needs to view and act on their team's records, but doesn't need org-wide access. Assigning VP of Sales here would be over-provisioning.

Why "Vice President of Sales" Is Not Used

The VP of Sales role has organization-wide record access and broad administrative rights. Under least privilege, you only assign it if the user genuinely needs visibility across all teams. Since no such user is described in this scenario, it's excluded.

Quick Reference

User Type	Role Assigned	Key Reason
Standard sales rep	Salesperson	Owns their pipeline
Support/peripheral member	Sales team member	View + limited interaction only
Team lead/manager	Sales manager	Team record access, no org-wide scope
(No VP-level user)	VP of Sales - not used	Would over-provision

The core exam trap: Candidates often assign Sales Manager to everyone "just to be safe," or use VP of Sales for the manager. Both violate least privilege.

Topics

#security roles#least privilege#Sales Hub#role assignment

Community Discussion

No community discussion yet for this question.

Full MB-280 Practice