Free Field-Service-Consultant Practice Test Questions (2026)

Explanation:

This question tests your understanding of the separation between operational permissions and configuration permissions in Field Service Lightning. While dispatchers need the Dispatcher License and Permissions to perform their daily job (viewing the Gantt, scheduling appointments, managing resources), the activities described here go beyond day-to-day operations into system configuration.

Let's analyze the dispatchers' described tasks:
Set up new territories: This involves creating and modifying Service Territory and User Territory records, which are setup objects.
Define new schedule policies: Creating and modifying Scheduling Policies and Scheduling Policy Sets is a configuration activity that changes how the scheduling engine behaves.
Control settings on the Gantt chart: This likely refers to configuring Gantt filters, columns, and settings (like the Gantt Settings tab), which are saved configurations that affect the dispatcher console's behavior for all users.
These tasks are administrative functions, not standard dispatching. The Field Service Lightning Admin Permissions permission set is specifically designed to grant this elevated access to configure and customize the Field Service application without needing the full System Administrator profile.

Why the other options are incorrect:
A. Field Service Lightning Mobile License: This license is for mobile technicians, not dispatchers. It grants access to the Field Service Mobile app, not to setup objects or configuration menus.
C. Field Service Lightning Scheduling License: This is a distractor. There is no standard Salesforce license named "Field Service Lightning Scheduling License." The role-based licenses are Dispatcher, Resource, Mobile, and Admin.
D. Field Service Lightning Standard Permissions: This is not a standard, recognized permission set for elevated access. The Field Service Lightning Dispatcher Permissions set provides the baseline access to perform dispatch tasks. The described tasks (territory setup, policy creation) require permissions beyond that standard set, which are contained in the Admin Permissions set.

Reference:
Salesforce Help: "Field Service Lightning Permission Set Licenses and Permission Sets" – This documentation clarifies the purpose of each permission set. The Field Service Admin Permissions set grants users the ability to "customize field service settings and configurations." This explicitly includes permissions to manage Service Territories, Skills, and Scheduling Policies – the exact tasks listed in the question.
The key principle is licensing vs. permissions: The FSL Dispatcher License allows a user to log in and access the FSL app. The FSL Dispatcher Permissions set lets them use the operational tools (Gantt, schedule). The FSL Admin Permissions set is an additional permission set that grants the higher privileges needed to modify the application's configuration. For a dispatcher to also act as a configurator, they need both the Dispatcher Permissions and the Admin Permissions assigned.

Explanation:

Universal Containers wants to standardize the creation of Work Orders because historically they have been created with incorrect skills and estimated completion times. The best way to enforce consistency in Field Service Lightning is to use Work Types.
Work Types are templates that define the standard information for Work Orders, including:
- Required skills (to ensure only qualified technicians are scheduled).
- Estimated duration (to provide accurate scheduling and resource planning).
- Parts or products typically needed.
- Description and other default values.
When a Work Order is created from a Work Type, all of this information is automatically populated, ensuring accuracy and standardization across the organization.
✅ This directly addresses the problem of incorrect skills and estimated times.

Why the other options are incorrect:
Option A (Entitlement Templates):
Used to define entitlement processes for customer support cases.
Not related to Work Order creation or skills/time standardization.
❌ Not correct.
Option B (Entitlements):
Define what services customers are entitled to (e.g., response times, support levels).
Useful for SLA tracking but not for standardizing Work Order creation.
❌ Not correct.
Option D (Work Order Record Types):
Record Types can differentiate categories of Work Orders (e.g., Installation vs. Maintenance).
They do not enforce skills or estimated time defaults.
❌ Not correct.

Reference:
Salesforce Help: Work Types
Salesforce Help: Work Orders Overview

Exam Tip:
When the requirement is about standardizing Work Orders with correct skills and estimated time, the answer is always Work Types.
Entitlements = SLAs
Record Types = categorization
Work Types = templates for standardization

Explanation:

In Salesforce Field Service Lightning, multi-day work refers to Service Appointments (or jobs) that span multiple days, typically because the estimated duration exceeds a single workday or shift (e.g., a 20-hour job with technicians working 8-hour shifts).
The scheduled timeframe (start and end dates/times) of a multi-day appointment is influenced by several factors. The two key considerations from the options are:

A. Assigned Resource:
The specific technician (Service Resource) assigned directly impacts the timeframe because their shift hours (defined in Service Resource or Crew records) determine how many hours per day can be allocated to the job. Different resources may have different shift patterns (e.g., 8-hour vs. 10-hour days, weekends off), so assigning a different resource can change when the multi-day job starts and ends.

D. Break Duration:
Breaks (lunch, rest, etc.) configured in the Operating Hours (via Travel Time, Break Time settings) or Shift Patterns reduce the available working time per day. Longer or additional breaks extend the overall timeframe needed to complete the total duration across multiple days.

The other options do not directly impact the multi-day scheduled timeframe:
B. Homebase Travel:
Travel to/from the home base or first/last appointment affects travel time calculation but does not alter the core timeframe of the multi-day work itself.
C. Resource Skill Level:
Skill level can influence eligibility or scheduling score (via Match Skills rule) but does not affect the duration or daily allocation of hours in multi-day scheduling.

Reference:
Salesforce Help: Multi-Day Service Appointments
Scheduling Factors for Multi-Day Work (shift hours, operating hours including breaks determine spread across days).

Explanation:

This question tests your understanding of modeling multiple, distinct site visits for the same underlying issue using a single Work Order. The requirement is to track these separate visits as part of the same overall job record.

Why Service Appointments are the correct object:
Single Work Order, Multiple Visits: The Work Order represents the overall customer issue or job request. It is the parent container. The Service Appointment object represents a scheduled time slot for a resource to perform work. A single Work Order can have multiple related Service Appointments.

Tracking Visits: Each physical site visit corresponds to a distinct time the technician is scheduled to be on-site. Therefore, each visit should be represented by its own Service Appointment (with its own Scheduled Start/End, Status, and actuals). This allows you to track the history: "Visit 1 on Jan 10 - Diagnosis, Visit 2 on Jan 15 - Repair."

Unified Tracking: Linking all these appointments to the same Work Order keeps the history, notes, asset information, and required parts consolidated under one job record, while clearly showing the multi-visit timeline.

Why the other options are incorrect:
B. Create a new Child Work Order for each site visit: This creates separate, distinct job records. While possible, it overcomplicates the data model for what is fundamentally a single issue tracked under one ticket. It breaks the unified view and reporting on the single issue.

C. Create a new Product Consumed for each site visit: Product Consumed records are for tracking parts used, not site visits. You could consume parts during each visit, but the act of creating a Product Consumed record does not, by itself, create a trackable record of a site visit (with time, date, status). It's a detail of a visit, not the visit itself.

D. Create a new Work Order Line Item for each site visit: Work Order Line Items represent different tasks or components of work (e.g., "Diagnose issue," "Replace pump," "Test system"). They are best used to break down the scope of work, not to track separate calendar visits. A single line item (like "Replace pump") might require multiple site visits to complete. Using WOLIs for visits conflates task definition with scheduling history.

Reference:
Salesforce Help: "Link a Service Appointment to a Work Order" – The documentation establishes the one-to-many relationship: "You can create multiple service appointments for a single work order."

Real-World Practice:
The standard data model for this scenario is:
One Work Order (Customer Issue: "Machine X not working")
Multiple Service Appointments linked to that Work Order (Visit 1: Diagnostic, Visit 2: Part Installation, Visit 3: Follow-up Test)
Work Order Line Items can define the tasks involved, and each Service Appointment can be associated with the relevant WOLI(s).
This model perfectly fulfills the requirement to track multiple site visits under a single job ticket.

Explanation:

A. Service Appointment Generation Method = One Service Appointment per Work Order:
The user requirement specifically states that the inspection "should be completed within a single visit." By setting this to "One Service Appointment per Work Order," the system generates only one appointment for the parent Work Order, regardless of how many assets (WOLIs) are attached to it.
This prevents the dispatcher's Gantt chart from being cluttered with multiple appointments for the same location and ensures the technician has one continuous block of time to inspect all assets.

C. Work Order Generation Method = One Work Order Line Item per Asset:
This setting ensures that when the Maintenance Plan runs, it creates one parent Work Order for the entire site visit and then creates a separate Work Order Line Item (WOLI) for every Asset covered by the plan.
This is the best practice for "multi-asset" inspections because it allows the technician to see a checklist of every machine on-site under a single job, tracking the status and notes for each asset independently.

🔴 Incorrect Answers:

B. Work Order Generation Method = One Work Order per Asset:
If this were selected, the system would create multiple separate Work Orders for a single site visit (one for each machine). This makes it significantly harder to manage the "single visit" requirement, as the technician would have to open and close multiple high-level records instead of a single list.
D. Service Appointment Generation Method = One Service Appointment per Work Order Line Item:
This is the opposite of what is required. This setting would generate a separate Service Appointment (visit) for every single asset. If a customer has 10 assets, the technician would see 10 different appointments. This contradicts the requirement to complete the work in a "single visit."

📖 References:
Salesforce Help: Work Order Generation Methods in Maintenance Plans
Salesforce Help: Maintenance Plan Fields
Trailhead: Create Maintenance Plans

Explanation:

Reasoning:
Unique Identification: Each door lock has a unique 20-digit code that must be tracked individually.
Standard Field Requirements: In Salesforce Field Service, if you need to enter a specific serial number on a Product Item record, the Quantity On Hand for that record must be 1. Because each lock has its own unique 20-digit code, tracking them as separate Product Items ensures that each unique serial number is associated with a single unit of inventory.
Serialized Inventory Management: While newer "Serialized Product" objects exist for high-volume serialization, the standard practice for tracking discrete, high-value unique units (like specialized door locks) in a technician's van is to create individual Product Item records where each record represents exactly one unique physical unit.

Why other options are incorrect:

Option A & B: Storing serial numbers in a related list or notes section does not leverage the standard inventory management engine, making it difficult to "consume" a specific lock during a service appointment or maintain accurate stock levels.
Option D: Simply entering a quantity (e.g., "5") on a single Product Item record would track the locks as bulk stock, which does not allow for the tracking of individual 20-digit codes required by the business.

Explanation:

Why this is correct:
In the call-center flow, the Case is the customer-reported issue. If it requires on-site work, you convert that into field work by creating a Work Order (the work to be performed). To actually schedule and send a technician, you then create a Service Appointment (the schedulable/dispatchable visit on the Gantt). Finally, you dispatch the Service Appointment to the technician.

Correct object roles:
Case = customer issue intake / support tracking
Work Order = field work record (what needs doing)
Service Appointment = scheduled visit (what gets dispatched)

Why the other options aren’t correct:

A puts Service Appointment before Work Order (normally the appointment is tied to the WO and represents the visit for that work).
B attempts to “dispatch work order” (dispatching is done on Service Appointments, not Work Orders).
D starts with a Service Appointment before the Case/Work Order context exists, which is backwards for a call-center intake process.

Explanation:

This question tests your knowledge of the specific "In Jeopardy" feature designed for proactive risk management in Field Service. The requirement is for technicians to indicate when appointments are at risk of late completion—a proactive flag, not a status update after the fact.

Why the "In Jeopardy" field is the correct solution:
Purpose-Built Field: The "In Jeopardy" checkbox field on the Service Appointment object is specifically designed to manually or automatically flag appointments that are at risk of missing their due date. This allows for early intervention.
Mobile Accessibility: Technicians can easily toggle this checkbox directly from the Service Appointment details in the Field Service Mobile app. It's a simple, one-tap action to raise a warning.
Visibility & Alerts: When flagged, the appointment can be highlighted in the Dispatcher Console (Gantt chart), and Chatter or other alerts can be configured to notify dispatchers or managers, enabling them to proactively reassign, reschedule, or provide support.

Why the other options are incorrect:
A. Post to the Service Appointment Chatter feed: While possible, this is an informal and unstructured method. It relies on people monitoring the feed and doesn't provide a systematic way to filter, report on, or automatically act upon at-risk appointments. The "In Jeopardy" field is the standard, reportable flag for this purpose.
B. Change the Status field on the Service Appointment: The Status field (e.g., Scheduled, Dispatched, In Progress, Completed) reflects the current stage of the appointment, not a prediction or risk about its future completion. Changing status doesn't effectively communicate a "risk of being late" warning; it just updates the current state.
C. Adjust the Scheduled End field on the Service Appointment: Technicians should not arbitrarily change the Scheduled End time. This field is typically set by the scheduling engine or dispatcher. Manually adjusting it would distort the schedule and is not the proper method for signaling risk. It's a data edit, not a risk indicator.

Reference:
Salesforce Help: "Service Appointment In Jeopardy Field" – The documentation explains: "Use the In Jeopardy field to indicate a service appointment that might not be finished on time. For example, a field technician can set the In Jeopardy field if a job is taking longer than expected."
This feature is a key component of service delivery management, enabling proactive exception handling rather than reactive reporting of late completions. It is the standard, supported way for mobile technicians to communicate schedule risks.

Explanation:

In Salesforce Field Service, a Service Resource record represents the "capacity" to do work. A single person should only ever have one Service Resource record to avoid scheduling conflicts and data duplication.

Why this is the correct configuration:
The Service Resource Record: By creating one Service Resource record linked to the User, you allow the scheduling engine to see them as a candidate for appointments (Technician role).

Permission Set Licenses (PSLs): To enable dual functionality, you assign multiple Permission Set Licenses to that single User:
- Field Service Dispatcher: Grants access to the Dispatcher Console and Gantt chart.
- Field Service Mobile: Grants access to the mobile app for field work.
- Field Service Scheduling: Required for the resource to be included in scheduling logic.
Unified View: This allows the user to switch between the Desktop (Dispatcher Console) and the Mobile App (Technician view) seamlessly using the same identity.

🔴 Incorrect Answers

B. Create two skills records and assign them to service resources record: Skills define what a resource can do (e.g., "Repair," "Installation"), but they do not define the role or grant access to tools like the Dispatcher Console. Creating a "Dispatcher Skill" would not actually give the user the ability to use the Gantt chart.
C. Create two service resource and assign them to the employee: This is a major technical error. A User should only be linked to one active Service Resource. Having two records for the same person would mean the system might try to schedule the "Technician" resource for one job and the "Dispatcher" resource for another at the same time, creating a "double-booking" scenario that the system cannot automatically resolve.
D. Create one service resource and assign the technician and dispatcher role: While there is a "Resource Type" field on the Service Resource record that includes "Technician" and "Dispatcher," simply selecting a value in a picklist does not grant the necessary functional permissions. The Permission Set Licenses (as mentioned in Option A) are the mandatory mechanism for granting the actual access to the Dispatcher Console and Mobile App.

References:
Salesforce Help: Guidelines for Creating Service Resources
Salesforce Help: Field Service Permission Set Licenses
Trailhead: Field Service Center Basics (Personas & Permissions)

Explanation:

Earliest Start Permitted and Due Date are the key fields used to enforce SLA commitments in Field Service Lightning.
Earliest Start Permitted: Defines the earliest time the appointment can begin, ensuring work doesn’t start before the agreed SLA window.
Due Date: Sets the latest time by which the appointment must be completed, aligning directly with SLA deadlines.
These fields are critical for SLA tracking because they establish the contractual boundaries for when service must be delivered. Dispatchers and optimization engines use them to prioritize and schedule appointments so that SLA violations are avoided.

Other options:
Actual Start/End (A): These are historical fields captured after execution, useful for reporting but not for SLA enforcement.
Arrival Window Start/End (B): These define customer-facing arrival expectations but don’t directly enforce SLA deadlines.
Scheduled Start/End (C): These are system-generated scheduling fields, but they can be adjusted and don’t represent SLA commitments.

Reference:
Salesforce Help: Service Appointment Fields
Trailhead: Field Service Settings and SLAs