Overview
Manage the Field Service mobile app was weighted at 5–10% of MB-240. It has two halves. The first is using the app to deliver work: updating booking statuses, completing service tasks, adding follow-up work orders, capturing signatures and images, producing the technician service report, servicing customer assets including IoT-connected devices, performing ad hoc inspections, working offline, entering time and launching Remote Assist or Guides.
The second half is setting the app up: assigning security roles, customizing forms, views, pages and navigation in the Field Service Mobile app module, enabling location tracking and geofencing, configuring the mobile offline profile, online mode and synchronization, push notifications, barcode scanning, installation and service report configuration. The current app is a model-driven Power Apps mobile app, so most customization uses the same tools as any model-driven app.
How it's tested
Mobile questions tend to be short and practical. Some describe a technician task, such as capturing proof of completion, and ask for the feature. Others describe a symptom, like records missing when the device is offline, and ask which configuration controls it. Tie each answer back to the offline profile, security role or app module.
-
Feature for a field task
A technician needs to capture a signature, photo, barcode, time or inspection result, and you choose the built-in mobile capability.
-
Offline data gaps
Data is missing or stale on a device, and you identify the offline profile table, filter or sync interval to change.
-
App configuration
Forms, navigation, notifications or location tracking must change, and you pick the app module, Power Automate flow or setting involved.
Technicians in rural areas report that customer asset history is blank once they lose signal, although bookings and work orders load fine. Bookings already sync, so the app and security role work. The likely gap is the mobile offline profile, which does not include the customer asset table or filters it too narrowly. Adding the table with a filter tied to the technician's bookings fixes it without changing forms.
Functional groups 2
Official functional groups from the Microsoft outline, in outline order.
4.1 Deliver work orders by using the mobile appCompleting work orders, servicing assets, inspections, offline work, time entry and launching related apps.
- What it means
- This group covers what a technician does in the app: completing work orders with tasks, booking statuses, follow-up work orders, signatures, images and technician reports; servicing customer assets including IoT devices; performing inspections, including ad hoc ones; working offline; entering time; and opening Remote Assist and Guides.
- What to understand
- The booking is the technician's entry point; changing its status from Traveling to In Progress to Completed drives the work order. Service tasks record percent complete and can contain inspections. Follow-up work orders capture extra work found on site. The service report combines tasks, products, services and a customer signature into a document. IoT alerts from connected assets can surface as work. Time entries can be created from booking status changes or entered manually.
- How it shows up
- Expect a question on capturing customer sign-off or recording additional work found on site.
- Common confusion
- A follow-up work order is a new job; adding lines to the current one changes what this visit bills.
4.2 Set up the mobile appSecurity roles, customization, location tracking, offline profiles, notifications, barcodes, installation and service reports.
- What it means
- This group covers configuring the app for an organization: security roles, forms, views, pages and navigation, location tracking and geofencing, the mobile offline profile with online mode and synchronization, push notifications, barcode scanning, app installation and the technician service report.
- What to understand
- Technicians typically need the Field Service - Resource role and access to the Field Service Mobile app module. The offline profile lists which tables and filtered rows download to the device, and sync intervals control freshness. Location tracking shares technician position with dispatch, and geofencing raises events when a technician enters or leaves a site. Push notifications are usually sent with Power Automate. Barcode scanning uses a control on product fields.
- How it shows up
- Look for missing offline data or a notification requirement and choose the profile or flow.
- Common confusion
- The offline profile governs data on the device; security roles govern what a user can access at all.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Field Service Mobile app module
The model-driven app technicians use.
- Remember
- Customized like any model-driven app.
- Tested as
- Customization questions.
- Trap
- Editing the dispatcher app instead.
-
Mobile offline profile
Defines tables and rows downloaded to the device.
- Remember
- Filters should follow the technician's bookings.
- Tested as
- Offline data questions.
- Trap
- Adding every row of every table.
-
Booking status on mobile
Technician-set status that drives the work order.
- Remember
- Traveling, In Progress and Completed are key values.
- Tested as
- Status flow questions.
- Trap
- Expecting technicians to edit work order status.
-
Follow-up work order
New job created from the current visit.
- Remember
- Keeps the original job's scope intact.
- Tested as
- Extra work scenarios.
- Trap
- Adding unrelated lines to the current work order.
-
Technician service report
Document combining work done and signature.
- Remember
- Configurable and generated from the booking.
- Tested as
- Proof of completion questions.
- Trap
- Building a custom PDF flow.
-
Location tracking
Shares technician position with the organization.
- Remember
- Must be enabled and permitted on the device.
- Tested as
- Dispatcher visibility scenarios.
- Trap
- Assuming it works without device permission.
-
Geofencing
Events when a technician enters or leaves a site.
- Remember
- Can prompt or automate status changes.
- Tested as
- Arrival automation questions.
- Trap
- Confusing it with territory.
-
Push notifications
Alerts sent to the mobile app.
- Remember
- Commonly triggered by Power Automate.
- Tested as
- New booking alert scenarios.
- Trap
- Expecting email to reach offline devices.
-
Barcode scanning
Device camera reads product barcodes.
- Remember
- Enabled on a product or text field control.
- Tested as
- Inventory and asset lookups.
- Trap
- Requiring separate scanner hardware.
-
Connected Field Service and IoT
Device alerts that can create work orders.
- Remember
- Assets link to IoT devices.
- Tested as
- Proactive maintenance scenarios.
- Trap
- Expecting the app to read devices directly.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Offline profile vs. security role vs. app module
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Offline profile | Data downloaded to the device | Controls availability without a connection | Using it to grant permissions |
| Security role | Privileges on tables | Controls what a user can do at all | Expecting it to sync data offline |
| App module | The app's tables, forms and navigation | Controls what appears in the app | Editing the wrong app |
Location tracking vs. geofencing
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Location tracking | Periodic technician position | Shows where the technician is | Assuming it triggers status changes |
| Geofencing | Boundary around a service location | Raises enter and exit events | Treating it as continuous tracking |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Security role for offline data
- What candidates pick
- Add privileges to the technician role so assets appear offline.
- Why it looks right
- Missing data looks like an access issue.
- Why it's wrong
- If records load online, access is fine; the offline profile decides which rows sync to the device.
Clue to watch for Data is visible only when connected.
-
Email for urgent alerts
- What candidates pick
- Send an email when a booking is created.
- Why it looks right
- Email is familiar and easy.
- Why it's wrong
- Push notifications, typically from Power Automate, reach the app directly and can open the record.
Clue to watch for The technician must be alerted on the device.
-
Edit work order status on mobile
- What candidates pick
- Have technicians change the work order system status.
- Why it looks right
- The work order is what matters.
- Why it's wrong
- Technicians update booking status, which rolls up correctly and keeps multi-booking jobs consistent.
Clue to watch for The technician arrives, starts or finishes a visit.
-
Custom signature solution
- What candidates pick
- Build a canvas app to capture signatures.
- Why it looks right
- Custom apps are flexible.
- Why it's wrong
- The mobile app supports signatures and the technician service report out of the box.
Clue to watch for Proof of completion with customer sign-off is required.
-
Sync everything offline
- What candidates pick
- Add all rows of all tables to the offline profile.
- Why it looks right
- Nothing will be missing.
- Why it's wrong
- Large profiles slow sync and use storage; filters should limit data to what each technician needs.
Clue to watch for Sync is slow or devices run out of space.
Answer framework
For Domain 4 mobile scenarios, decide what kind of problem it is before choosing a feature.
- Decide whether the scenario is about what a technician does on site or how the app is configured for everyone.
- For on-site tasks, use built-in features first: booking statuses, service tasks, inspections, signatures, images, follow-ups and service reports.
- For data missing on the device, check the mobile offline profile tables, filters and sync interval before touching security roles or field-level permissions.
- For forms, views and navigation, change the Field Service Mobile app module and its forms rather than the dispatcher app.
- For alerts, position and arrival automation, choose push notifications through Power Automate, location tracking or geofencing as fits, and confirm the technician's device allows location access.
Practice question
Want more like this? The MB-240 practice test has questions for every domain.
Checklist
0 of 12
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Install the Field Service mobile app on a phone or use it in a browser against your trial, and sign in as a user with the Field Service - Resource role. Work a booking from start to finish: set Traveling, In Progress and Completed, complete service tasks, add a used product, create a follow-up work order, capture a signature and image, and generate the service report. Then put the device in airplane mode and note which records remain available.
Next, switch to configuration. Open the mobile offline profile, inspect its tables and filters, and add one table with a filter tied to bookings. Customize the mobile work order form, add a navigation item, and confirm the change on the device after sync. Read the documentation for location tracking, geofencing, push notifications through Power Automate and barcode scanning, focusing on what each one does and its prerequisites.
Because the domain is light in weight, aim for clear distinctions rather than depth. Make sure you can separate offline profile, security role and app module problems immediately, since that single distinction answers many mobile questions.
FAQ
How much of MB-240 was Manage the Field Service mobile app?
Manage the Field Service mobile app was 5–10% of the exam in the final outline, one of three smaller domains.
What controls which data is available offline?
The mobile offline profile lists the tables and filtered rows that download to the device. Security roles still decide whether the user can access those records at all.
How does a technician capture customer sign-off?
The mobile app supports signatures directly, and the technician service report combines tasks, products, services and the signature into one document.
Should technicians change work order status?
They should update booking status instead. Booking statuses map to Field Service statuses that roll up to the work order consistently.
How are push notifications usually sent?
Typically with a Power Automate flow that triggers on an event, such as a new booking, and sends a notification to the Field Service mobile app.
Is the Field Service mobile app a separate product?
The current app is a model-driven Power Apps mobile app, so forms, views and navigation are customized with standard Power Apps tools in the Field Service Mobile app module.
Other CRM & Business Applications certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- HubSpot Inbound Marketing Certification Study guide
- Salesforce Certified Platform Developer I Study guide
- Google Ads Search Certification Study guide
- ServiceNow Certified System Administrator Study guide
- Salesforce Certified Platform Administrator Study guide
- ServiceNow Certified Application Developer Study guide
Test your Domain 4 knowledge
You have covered mobile work completion, offline profiles, location features, notifications and service reports. Test whether you can match each technician need to the right feature.
Keep going
- Training Training Built on your Weak areas
- Practice test Questions by domain, with explanations
- Mock exam Full length, timed like the real exam
- Readiness test Find your weakest domain in minutes
- Cheat sheet Key terms and formulas on one page
- Ask the MB-240 AI tutor Get any concept explained your way