Browse Certification Practice Tests by Exam Family

Microsoft MB-240 Cheat Sheet: Field Service

Review the Microsoft Dynamics 365 Field Service Functional Consultant (MB-240) scope, work orders, scheduling, resources, assets, inventory, mobile work, service delivery, and configuration traps before practicing.

MB-240 focuses on field-service execution: turning service demand into work orders, bookings, resources, inventory, mobile execution, asset history, and operational follow-through.

Use this with practice. Review the Field Service checkpoints, then return to the MB-240 page for sample questions and update tracking.

Open MB-240 practice page Compare Dynamics 365 routes

Exam snapshot

FieldDetail
IssuerMicrosoft
Certification laneDynamics 365 Field Service Functional Consultant
Exam codeMB-240
Main scopeWork orders, incidents, scheduling, resources, assets, inventory, mobile work, agreements, and service operations
IT Mastery statusSample questions available

Field Service map

AreaWhat to knowCommon trap
Work ordersIncidents, tasks, products, services, bookings, status, and closureTreating the work order as only a calendar appointment
SchedulingResource requirements, territories, skills, availability, and optimizationBooking the nearest technician without checking skills or parts
Assets and agreementsCustomer assets, service history, recurring work, and contract termsLosing asset context between visits
InventoryWarehouses, parts, truck stock, consumption, returns, and replenishmentScheduling work when required parts are unavailable
Mobile workTechnician access, offline behavior, forms, notes, and completion dataDesigning only for dispatchers and ignoring technicians

Must-know distinctions

DistinctionHow to decide
Case vs work orderA case tracks the service issue; a work order manages field execution.
Incident type vs service taskIncident types template common work; service tasks are specific steps.
Resource vs bookingA resource can perform work; a booking assigns work to a time slot.
Customer asset vs productAssets are installed or owned items; products are catalog or inventory items.
Agreement vs one-time work orderAgreements generate or govern recurring service work.

High-yield checklist

  • Capture the field problem in a work order with the right incident type.
  • Match bookings to skills, territory, availability, and parts.
  • Maintain customer asset history for repeat service.
  • Track inventory consumption and technician stock.
  • Design mobile flows around technician reality.
  • Use agreements for recurring service patterns.
  • Report on schedule performance, first-time fix, and backlog.

Common traps

  • Scheduling before confirming resource and inventory requirements.
  • Ignoring mobile/offline technician needs.
  • Using one generic incident type for all work.
  • Confusing service case handling with field execution.
  • Closing work without capturing parts, labor, and outcome details.

Practice strategy

For MB-240 misses, ask whether the issue is work-order design, scheduling, resource fit, asset history, inventory, mobile execution, or agreement handling. Strong answers improve dispatch reliability and service traceability.

Revised on Monday, May 25, 2026