MB-240 study plan

Configure work order types, priorities, statuses and substatuses so each status maps to a step in the work order lifecycle you can name from memory.

Build incident types that bundle required service tasks, products and services, then attach them to work orders and verify the lines auto-populate.

Create the customer hierarchy: account, functional location, customer asset, and a child asset, and link each work order to the right asset record.

Trace a work order from creation through scheduled, in progress, completed and closed, recording which fields and settings change at each step.

Configure customer assets with warranty dates, parent-child relationships and subcomponents, then test what changes on a work order when an asset is under warranty.

Set up agreements and entitlements that generate recurring work orders and that apply a discount or free service line under defined conditions.

Configure bookable resource types, resource roles and characteristics, and add at least three resources with skills, territory and hourly rate defined.

Create organizational units and territories that match a two-city service area, and assign resources to them.

Walk through Field Service settings and change at least ten options (geo-coding, booking, time zone, resource scheduling) while writing the effect each change has on scheduling behavior.

Configure security roles and field security so a technician can read and update assigned work orders but cannot create price lists or delete customer assets.

Set up crews, facilities and equipment as bookable resources and confirm each appears correctly as a schedulable candidate.

Configure the schedule board settings that belong to app configuration, including board views, resource filters and requirement filters.

Configure schedule board tabs and views for two different dispatcher personas, one focused on territory and one on resource type.

Build requirement groups with multiple resource requirements and explain when a requirement group is required instead of a single requirement.

Perform move bookings, split bookings, crew bookings and substitute-resource bookings, and document the effect of each on the original work order.

Set up and run Resource Scheduling Optimization on a small set of requirements, then review the booking results against manual scheduling.

Configure scheduling parameters such as fulfillment preference, promise windows and booking duration rules, then test which work orders get blocked by each.

Set up the Field Service mobile app project, including offline profile, entities stored offline, sync settings and conflict resolution behavior.

Configure mobile app features: barcode scanning, photo capture, geolocation and push notifications, then document which require extra tenant configuration.

Build an inspection attached to a work order, complete it in the mobile app, and verify the answers flow back into the work order record.

Configure warehouses and product inventory, then record an inventory adjustment, a transfer between warehouses and consumption of a product on a work order.

Create a purchase order, receive the products, and process a return for unused product back into stock using the built-in inventory module.

Configure the default warehouse, inventory settings and unit groups that govern how product quantities appear on work order product lines.

Build a Power Automate flow that triggers on work order status change and posts a message to Teams, and a Power Apps canvas app screen for a technician checklist.

Extend a model-driven Field Service app with a custom table, form changes and role-based access, then verify a technician sees only the new components intended for them.

Build a Power BI report that shows booked versus completed work orders by territory and technician, and explain which table and relationship supplies each measure.

Re-test two Domain 2 and Domain 4 weak spots identified by earlier quizzes, and rewrite the notes for any item you still miss.

Configure one business process flow or business rule that enforces a required field before a work order can move to completed.

Complete two timed full-length practice sets, then classify every missed question by domain and root cause (unknown setting, misread scenario, sequencing error).

Rebuild from scratch, in under 45 minutes, a working configuration covering one incident type, one resource with characteristics, one territory and one warehouse.

Recite the work order lifecycle, the scheduling constraint order and the inventory transaction types from memory, checking each against the product documentation.