Free MB-240 Exam Braindumps
Microsoft Dynamics 365 for Field Service Questions 1–4 (page: 12)

Updated On: 10-Feb-2026
View Related Case Study

DRAG DROP (Drag and Drop is not supported)
You need to create a Preventative Maintenance Agreement that meets Contoso standards and requirements.

Which five steps should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



First create an agreement (steps 1 to 3).
Then set up booking recurrence (steps 4 and 5)

Step 1: Create an agreement with the PM incident selected.
Incidents are used.

Most Contoso customers sign agreements for Preventative Maintenance. Contoso uses templates and incidents to ensure services standards are the same across all regions. Preventative Maintenance agreements include monthly inspection and quarterly cleaning and inspection, with billing occurring quarterly.

Step 2: Add two agreement schedules, one monthly and one quarterly
Two separate schedules.

Step 3: Set agreement to Active.
Create SLAs to define conditions and actions that are applicable when an SLA is applied to an entity. The following steps are involved in creating the SLA:

-Create an SLA.
-Create an SLA item.
-Configure actions for the SLA item.
-Activate the SLA.

Step 4: Set Auto Generate Work Order to Yes
Case study: Setup and create work orders, bookings and invoices for preventative maintenance with work orders automatically created 14 days before PM is due.

Once the agreement has been created, specify how often work orders should be generated.

1. In the Booking Setups section, select +Add Booking Setup record.

2. Fill in your information to create the agreement schedule. Use the handy tooltips as a guide.

Name: Enter the name of the agreement schedule. For example, it could be "Monthly Maintenance." Naming is important because an agreement can have multiple booking recurrences. For instance, the service organization may perform weekly and monthly maintenance as part of the same agreement.
Work order settings
* Auto Generate Work Order: Set to Yes to have this agreement automatically generate work orders.

..details omitted…

3. Booking recurrence
Define a pattern to create work orders based on the agreement.

Select Booking Recurrence in the command bar at the top.

Specify the Recurrence Pattern. For example, every week, every first Monday of the month, or every other Friday.

Etc.

Step 5: Set Invoice Recurrence to Monthly, recur every 3 months.


Reference:

https://learn.microsoft.com/en-us/dynamics365/field-service/set-up-customer-agreements
https://learn.microsoft.com/en-us/dynamics365/customer-service/define-service-level-agreements



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
A dispatcher in Indianapolis, Indiana receives an emergency service call on July 4 and assigns the booking to a third-party contractor, attaching the emergency SLA The contractor receives notification of the work order and travels from his home to the job site, arriving 3.5 hours after the work was assigned.

The contractor works for 2 hours, installing 2 new identical chillers, which need to be added to the customer's annual maintenance agreement. The contractor fills in product usage and notes, gets the client’s signature, and then changes the booking status to Completed.

What do you need to configure to handle this scenario? Put the required steps in the correct order.

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Requirement groups for work orders
For field service scenarios, requirement group templates are designed to work with incident types. An incident type is a way of automatically adding duration, service tasks, products, services, and other attributes to a work order. Adding an incident type to a work order can also automatically add requirement groups. This is achieved by associating a requirement group template to an incident type:

Create a requirement group template.
Associate an incident type to the requirement group template.
Add the incident type to a work order.
Book the work order.

Step 1: Configure a requirement group template.
Create a requirement group template

Step 2: Configure an incident type.

Step 3: Associate the incident type to the requirement group template.

Step 4: Create a work order sub-status called Chiller installation.
Work Order Substatuses are noted on the work order entity and relate to and provide more detail for work order system statuses. Work order substatuses are created custom for each organization.

Incorrect:
* Add the incident type to all Chiller Installation Work orders.
The incident type should be associated with the requirement group template instead.

* Create a priority record.
No need of priority record in this scenario.


Reference:

https://learn.microsoft.com/en-us/dynamics365/common-scheduler/multi-resource-scheduling-requirement-groups
https://learn.microsoft.com/en-us/dynamics365/field-service/work-order-status-booking-status



View Related Case Study

Contoso. Ltd. has asked that you create several Work Order Types to meet their Requirements and Planned Changes.

Of the many work order types requested, which three should you create? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

  1. Inspection
  2. Returns
  3. Preventative Maintenance
  4. Installation
  5. Agreement

Answer(s): A,C,D

Explanation:

A: Preventative Maintenance agreements include monthly inspection and quarterly cleaning and inspection, with billing occurring quarterly.

C: Setup and create work orders, bookings and invoices for preventative maintenance with work orders automatically created 14 days before PM is due.

D: Contoso's field service technicians respond to all installation work orders with two human resources.

Incorrect:
Not B: Returns not mentioned in the scenario.

Not E: Agreement is not a Work order type.

Note: A work order type in Dynamics 365 Field Service helps you categorize and build different types of work orders, such as installation, preventative maintenance, repair, sales, quote, and so on. When you create a work order type, it also helps separate work order information into views, reports, and dashboards on the schedule board.


Reference:

https://learn.microsoft.com/en-us/dynamics365/field-service/create-work-order-types



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
A dispatcher in Indianapolis, Indiana receives an emergency service call on July 4 and assigns the booking to a third-party contractor, attaching the emergency SLA The contractor receives notification of the work order and travels from his home to the job site, arriving 3.5 hours after the work was assigned.

The contractor works for 2 hours, installing 2 new identical chillers, which need to be added to the customer's annual maintenance agreement. The contractor fills in product usage and notes, gets the client s signature, and then changes the booking status to Completed.

A back office employee needs to look at the work order to ensure accuracy, then change the status to Posted.

When performing a quality check, what will the back office employee expect to see as a result of this service call? To answer, drag the appropriate record type to the correct statement. Each record type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.

NOTE: Each correct match is worth one point.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Invoice
Charges on the invoice.

Box 2: Customer asset
Customer assets let you keep track of equipment that you're responsible for inspecting, maintaining, and repairing. At their simplest, customer assets note which products are located at each customer location. But they can also track service history of all past and present work orders for each asset. And if you're using Connected Field Service, you can connect customer assets to sensors that monitor the asset's health and trigger IoT alerts and work orders as needed.

Box 3: Work Order / Booking
Work order inventory
Adding products to work orders and using them affects inventory.

For example, adding a product as estimated and allocated (Line Status set to Estimated, Allocated and Yes) reserves a portion of inventory from the specified warehouse, though it doesn’t actually deduct it.

If a work order product is used during a work order (Line Status set to Used), the inventory at the related warehouse is deducted by the work order product quantity. Typically, the warehouse listed on a work order product is the technician's truck.

Box 4: Invoice
Charges on the invoice.

Box 5: Work Order / Booking
Work Order are associated with SLAs.


Reference:

https://learn.microsoft.com/en-us/dynamics365/field-service/configure-set-up-customer-assets
https://learn.microsoft.com/en-us/dynamics365/field-service/inventory-purchasing-returns-overview



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
During requirement and design discussions, Litware, Inc. Subject Matter Experts (SMEs) discuss a specific scenario.

A customer purchases an HVAC system along with a 1-year service contract and a 3-year extended warranty. After 9 months, the system shuts down and the customer cannot get it started back up. The customer calls into Litware, Inc. to inform them the system is down and he needs a service technician to come out to fix the unit.

The SMEs want to know which functionality within Dynamics 365 Field Service can handle the scenario.

Which configuration steps should you take in each of the categories listed? To answer, drag the appropriate configuration to the correct category in the answer area. Each element may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.

NOTE: Each correct match is worth one point.

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Work Order Type
A work order type in Dynamics 365 Field Service helps you categorize and build different types of work orders, such as installation, preventative maintenance, repair, sales, quote, and so on. When you create a work order type, it also helps separate work order information into views, reports, and dashboards on the schedule board.

Box 2: Incident Type
Incident types in Microsoft Dynamics 365 Field Service act as templates that allow users to quickly create work orders for these common types of jobs. You can also use incident types to define specific work order issues and recommended resolutions.

Incident types prepopulate the detail of the work order, which you can manually edit as needed.

Organizations benefit from using incident types because they codify issues, procedures, and resolutions, and help standardize processes across geographies and business lines. Incident types ensure that all field technicians perform the same actions to resolve work orders. Moreover, if better procedures are discovered, the incident type will be updated and implemented across the entire organization.

Using incident types will help you save time while creating work orders. Without using incident types, the customer service reps or dispatchers who are creating work orders would have to manually add details.

Box 3: Booking Alert
Booking alerts in Dynamics 365 Field Service
While managing resources and scheduling, dispatchers must be aware of important updates and status changes to ensure accurate schedules and timely job completion. For example, a dispatcher needs to know if a field technician is running late or that prerequisites for a job have not been met so that they can take appropriate actions. Beyond scheduling, dispatchers may also need to ensure billing and customer satisfaction concerns are handled.

Box 4: Booking Rule
Booking rules in Field Service allow a system administrator to create warning or error messages that users see when creating or editing a resource booking record, based on custom conditions. For example, a booking rule could be created to warn a user when they attempt to book a work order to a resource on the schedule board that doesn't have the skills required for the job.

Booking rules are custom JavaScript methods that will be executed prior to the bookable resource booking record being created or edited. The JavaScript method can accept a parameter that will contain information for the Bookable Resource Booking record being created and must return a JavaScript object with the required properties.

Incorrect:
* Resource Scheduling Optimization
Resource Scheduling Optimization automatically schedules jobs to the people, equipment, and facilities best equipped to complete them. Schedule work orders for field technicians or cases for customer service reps. You can cover other scenarios too, depending on how you use Dynamics 365 Field Service, Customer Service, and Project Service Automation.

Resource Scheduling Optimization is a more advanced form of scheduling for field service organizations. While the schedule board and the schedule assistant help dispatchers schedule a single job, this add-in can schedule multiple jobs at once. It maximizes resource utilization and minimizes travel time. Resource Scheduling Optimization considers the requirements of the job and the unique attributes of the resources.


Reference:

https://learn.microsoft.com/en-us/dynamics365/field-service/create-work-order-types
https://learn.microsoft.com/en-us/training/modules/incident-types/1-introduction
https://learn.microsoft.com/en-us/dynamics365/field-service/set-up-booking-rules
https://learn.microsoft.com/en-us/dynamics365/field-service/booking-alert



Viewing page 12 of 35
Viewing questions 56 - 60 out of 343 questions


Post your Comments and Discuss Microsoft MB-240 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!