MB-910 Describe Dynamics 365 Field Service Practice Question
A global field service company needs to enforce that technicians only see work orders assigned to them, while dispatchers see all work orders. What is the best approach in Dynamics 365 Field Service?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure security roles and field security profiles to restrict work order visibility based on assigned resource.
Security roles and field security profiles in Dynamics 365 Field Service enable role-based access control to restrict work order visibility. Technicians can be given a security role that limits their view to work orders where they are the assigned resource, while dispatchers have a role that allows viewing all work orders. Option A is wrong because business units organize by territory but do not automatically filter by assignment. Option B is wrong because the scheduling board is a scheduling tool, not a security mechanism. Option D is wrong because manual sharing is for per-record access and is not scalable for role-based visibility.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create separate business units for each territory.
Why it's wrong here
Separate business units organize by territory but do not automatically restrict work order visibility based on assigned resource without additional configuration.
- ✗
Customize the scheduling board to hide unassigned work orders.
Why it's wrong here
The scheduling board is a visualization and scheduling tool; hiding unassigned work orders does not enforce security—it only changes the view.
- ✓
Configure security roles and field security profiles to restrict work order visibility based on assigned resource.
Why this is correct
Security roles and field security profiles provide granular control over record access, allowing you to set default visibility of work orders based on the user's role and the resource assigned.
- ✗
Use manual sharing to grant access to individual work orders.
Why it's wrong here
Manual sharing grants access to individual records but is not a scalable or role-based approach for enforcing visibility rules.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
About these practice questions
One of 941 original MB-910 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MB-910 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the MB-910 exam.