Free FIELD-SERVICE-CONSULTANT Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

Service Resources are records that represent the people or equipment that perform field service

tasks[53]. Permission Set Licenses are licenses that grant users access to specific features such as

Field Service Dispatcher Console or Field Service Mobile App[54]. Creating one service resource and

assigning the relevant permission set license would allow an employee at Universal Containers to

perform both dispatcher and technician roles using one record and one license. Creating two skills

records and assigning them to service resources record would not affect their roles or access to

features. Skills are records that define specific abilities or qualifications that service resources

have[55]. Creating two service resources and assigning them to the employee would create duplicate

records and require two licenses for one employee. Creating one service resource and assigning the

technician and dispatcher role would not work because roles are not fields on the service resource

object.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_permission_set_licenses_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm&type=5

A Service Appointment can be shared by clicking Sharing on the record if manual sharing is enabled

in Field Service settings[51]. Auto-generated scheduled Service Appointments will be shared with

resources if automatic sharing is enabled in Field Service settings[52]. The Service Appointment’s

parent record can be shared with the assigned resource, but this would not affect the sharing of the

Service Appointment itself. Making the dispatcher the assigned resource on the Service

Appointments would not make sense if they are not performing field service tasks. Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_sharing_manual.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_sharing_automatic.htm&type=5

This option should be recommended to meet this requirement, as it allows creating a service

resource that represents a group of technicians who work together on the same service

appointment.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_crew_management.htm&type=5

The In Jeopardy field on the Service Appointment is a checkbox that indicates whether a service

appointment is at risk of late completion based on travel time and service duration calculations.

Technicians can update this field using the Field Service Mobile App to alert dispatchers and

managers of potential issues. Posting to the Service Appointment Chatter feed, changing the Status

field on the Service Appointment, or adjusting the Scheduled End field on the Service Appointment

would not indicate that a service appointment is in jeopardy, but would communicate other

information

such

as

comments,

progress,

or

rescheduling.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_overview.htm&type=5

Drip Feed Dispatching is a feature that allows dispatching groups of service appointments to

technicians at regular intervals instead of all at once[56]. Enabling Drip Feed Dispatching in Field

Service Settings allows turning on this feature for all service territories[57]. Setting the Number of

Services to Drip Feed on the Service Territory allows specifying how many service appointments

should be dispatched at a time for each service territory[58]. Setting the Service Appointment to

Dispatch in Field Service Settings would not affect how many service appointments are dispatched at

a time. Enabling Sharing of Dispatched Service Appointments would not affect how many service

appointments

are

dispatched

at

a

time.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_enable.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_configure.htm&type=5

Reshuffle is an action within the Gantt that allows rescheduling multiple service appointments at

once based on predefined criteria such as emergency priority, travel time, or skills[209]. Reshuffle

would allow Universal Containers to dispatch emergency work identified throughout the day that

needs to be completed before lower-priority work by running a reshuffle action that prioritizes

emergency work and assigns it to the best available resources[210]. Defining a Global Optimization

job to run hourly would not allow Universal Containers to dispatch emergency work identified

throughout the day that needs to be completed before lower-priority work. Global Optimization is a

feature that allows rescheduling multiple service appointments at once based on predefined criteria

such as emergency priority, travel time, or skills[211]. Running a Global Optimization job hourly

would not be responsive enough for emergency work identified throughout the day. Creating a

custom Gantt action to call an Apex class to reschedule appointments would not be necessary for

Universal Containers to dispatch emergency work identified throughout the day that needs to be

completed before lower-priority work. Custom Gantt actions are actions within the Gantt that can be

customized using Apex code to perform specific tasks such as sending notifications or updating

fields[212]. Creating a custom Gantt action would require additional development and maintenance

and would not leverage the existing Reshuffle action. Writing a batch Apex class to unschedule low

priority work orders would not allow Universal Containers to dispatch emergency work identified

throughout the day that needs to be completed before lower-priority work. Batch Apex is a way of

processing large volumes of data asynchronously using Apex code[213]. Writing a batch Apex class

would require additional development and maintenance and would not leverage the existing

Reshuffle

action.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_gantt_reshuffle_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_gantt_reshuffle_run.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_optimization_global_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_gantt_custom_actions_overview.htm&type=5

https://developer.salesforce.com/docs/atlas.enus.apexcode.meta/apexcode/apex_batch_interface.htm

Service Territory Location is a junction object that links Service Territory and Location objects[236].

Related Lists are components on page layouts that show records that are related to a record through

a lookup or master-detail relationship[237]. Adding the Service Territory Location Related List on the

Service Territory page layout and adding the Service Territory Location Related List on the Location

page layout would allow Universal Containers to show how Locations are associated to Territories by

displaying a list of Service Territory Locations on each record[238]. Creating the Service Territory

Location as a Service Territory lookup field or creating the Service Territory Location as a Location

lookup field would not work because they are not valid fields on either object. Reference:

https://developer.salesforce.com/docs/atlas.enus.api.meta/api/sforce_api_objects_serviceterritorylocation.htm

https://help.salesforce.com/s/articleView?id=sf.customize_related_lists.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_service_territory_locations_overview.htm&type=

5

The asset relationships object is used to track when equipment has been swapped out by creating

parent-child relationships between assets. Adding the related asset related list to the asset page

allows viewing and creating asset relationships from an asset record. Adding the field history tracking

related list to the asset page would track field changes on an asset, but not asset relationships.

Adding the product request related list to the asset page would allow requesting products from

inventory

for

an

asset,

but

not

tracking

asset

relationships.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_asset_relationships_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_asset_relationships_create.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.tracking_field_history.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_product_requests.htm&type=5

The Preventative Maintenance Gantt is a view within the Dispatcher Console that shows the

scheduled service appointments for preventive maintenance work orders[217]. The Dispatcher

Console Appointment list is a view within the Dispatcher Console that shows the list of service

appointments with various details such as status, priority, or assigned resource[218]. Filtering is a

feature that allows narrowing down the list of records based on specific criteria such as date, status,

or territory[219]. Using the Preventative Maintenance Gantt and filter the list to show only desired

work orders and using the Dispatcher Console Appointment list and filter the list to show only

desired service appointments would allow Universal Containers’ Managers to monitor Preventative

Maintenance work orders using the Dispatcher Console by showing them the preventive

maintenance service appointments on a Gantt chart or a list view and allowing them to apply filters

to see only the relevant records[220]. Using the Dispatcher Console Map and filter the list to show

only desired service appointments would not allow Universal Containers’ Managers to monitor

Preventative Maintenance work orders using the Dispatcher Console. The Dispatcher Console Map is

a view within the Dispatcher Console that shows the locations of service appointments and resources

on a map[221]. Using the Dispatcher Work Order Polygon and filter the list to show only desired

service appointments would not work because there is no such feature as Dispatcher Work Order

Polygon.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_gantt_preventive_maintenance_overview.htm&t

ype=5

https://help.salesforce.com/s/articleView?id=sf.fs_gantt_appointment_list_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filter_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_gantt_preventive_maintenance_view.htm&type=

5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_map_overview.htm&type=5

Enabling the sharing features in the Field Service settings in the Setup menu allows sharing

dispatched service appointments with assigned resources regardless of the private record access

model in sales, support, and field service organizations[50]. Creating a user territory for the

technicians’ primary and secondary territories would not ensure that they have access to the service

appointments dispatched to them. Creating a process to change the owner of the service

appointment to the assigned technician would not work if multiple resources are assigned to the

same service appointment. Configuring a sharing rule to share dispatched service appointments with

the assigned resource would not work if multiple resources are assigned to different crews or teams.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_sharing_overview.htm&type=5

A custom Price Book allows different prices for the same products in different markets. A standard

Price Book has the same prices for all markets. Pricing rules are not available for Field Service

Lightning.

Reference:

https://help.salesforce.com/s/articleView?id=sf.pricebook_custom.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.pricebook_standard.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_pricing.htm&type=5

User Territories are records that associate users with service territories for sharing purposes[90].

Creating a new user territory associated with the Service Territory and dispatcher would allow giving

access to all relevant Midwest records by linking them with their corresponding service territory[91].

Configuring and running the User Territory Sharing Job in Field Service Settings would allow updating

sharing rules based on user territories automatically at regular intervals such as daily or weekly[92].

Assigning a new user territory and adding each of the assigned service resources would not give

access to all relevant Midwest records

A custom lightning component that displays work order progress can be created using Lightning Web

Components or Aura Components and deployed to technicians through the Field Service Mobile App

using Mobile App Extensions. Adding the work order line items related list to the work order page

layout would not show the work progress on the work order line-item card in the Field Service

Mobile App. Creating a custom visual force page or a report chart would not be compatible with the

Field

Service

Mobile

App

user

interface.

Reference:

https://developer.salesforce.com/docs/component-library/documentation/en/lwc

https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/

https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_extensions.htm&type=5

To provide access to the Salesforce Field Service Mobile App, the user’s profile must have the Field

Service Mobile permission enabled. Updating Public Group membership, assigning a Field Service

Mobile License to the user, or modifying the user record would not grant access to the mobile app.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_mobile_app_permissions.htm&type=5

This option allows creating a record to request products from another inventory location and adding

product

request

line

items

for

each

product

requested.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_product_requests_overview.htm&type=5

This option ensures that the service territory member’s operating hours are aligned with the service

territory’s

time

zone,

and

avoids

scheduling

conflicts

or

gaps.

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_operating_hours.htm&type=5

Permission Sets are records that grant users access to specific features or apps such as Salesforce

Field Service[214]. Scheduling licenses are records that grant users access to scheduling features such

as Dispatcher Console or Optimization[215]. Creating Permission Sets and assigning the Salesforce

Field Service Resource Permission Set and Scheduling license to each Technician would allow

Universal Containers’ Technicians to update their own appointments’ status using the Dispatcher

console Gantt chart by granting them access to Salesforce Field Service mobile app features such as

updating status and granting them access to scheduling features such as viewing Gantt chart[216].

Creating Permission Sets and assigning the Salesforce Field Service Scheduling and Mobile

Permission Sets to the Resource profile would not allow Technicians

Street Level Routing is a feature that calculates travel time between service appointments based on

actual road distance and traffic conditions[131]. Default Travel Speed is a setting that defines the

average speed of resources when traveling between service appointments[132]. Using Street Level

Routing and Default Travel Speed would allow improving travel time accuracy by taking into account

real-time road conditions and resource speed. Minimum Grade, Default Operating Hour would not

affect travel time accuracy. Minimum Grade is a setting that defines the minimum skill level required

for resources to be matched with service appointments[133]. Default Operating Hour is a record that

defines the default working hours for resources[134]. Estimated Travel Time, Minimize Travel would

not affect travel time accuracy. Estimated Travel Time is a field on the service appointment object

that shows the expected travel time for the assigned resource[135]. Minimize Travel is an

optimization

criterion

that

prioritizes

reducing

travel

time

when

scheduling

service

appointments[136]. Travel Speed Unit, Actual Travel Time would not affect travel time accuracy.

Travel Speed Unit is a setting that defines the unit of measurement for travel speed such as miles per

hour or kilometers per hour[137]. Actual Travel Time is a field on the service appointment object that

shows

the

actual

travel

time

recorded

by

the

resource[138].

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_street_level_routing_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_default_travel_speed.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_minimum_grade.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_default_operating_hours_overview.htm&type=5

https://developer.salesforce.com/docs/atlas.enus.api.meta/api/sforce_api_objects_serviceappointment_estimatedtraveltime.htm

https://help.salesforce.com/s/articleView?id=sf.fs_scheduling_policies_optimization_criteria.htm&t

ype=5

https://help.salesforce.com/s/articleView?id=sf.fs_travel_speed_unit.htm&type=5

https://developer.salesforce.com/docs/atlas.enus.api.meta/api/sforce_api_objects_serviceappointment_actualtraveltime.htm

Crew Management is a feature that allows creating and managing crews of multiple service

resources who share the same service appointments[163]. The Preferred Resource service objective

is ignored for active Crew Members because it only applies to individual resources and not

crews[164]. Capacity-based scheduling is not supported for Service Crews because crews do not have

capacity limits and can be assigned unlimited service appointments[165]. A service resource can be a

member of multiple crews and can switch between them depending on their availability and

skills[166]. Salesforce Field Service does not consider the Recommended Crew Size when assigning

appointments because it only considers the Required Crew Size which indicates the minimum

number

of

crew

members

needed

for

a

service

appointment[167].

Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_create_edit_delete.htm&type=5

https://developer.salesforce.com/docs/atlas.enus.api.meta/api/sforce_api_objects_serviceappointment_requiredcrewsize.htm

Service Appointments are records that track the date, time, duration, and assigned resource for a

work order or work order line item[117]. Creating a new Service Appointment for each site visit

would allow Universal Containers to track when Technicians need to visit a customer site multiple

times to resolve an issue by creating different service appointments for the same work order and

capturing notes and status updates for each service appointment. Creating a new Child Work Order

for each site visit would create unnecessary records and complexity. Child Work Orders are work

orders that are related to another work order as part of a hierarchy[118]. Creating a new Product

Consumed for each site visit would not track the site visits. Products Consumed are records that track

the products or parts that are used or installed during a service appointment[119]. Creating a new

Work Order Line Item for each site visit would not track the site visits. Work Order Line Items are

records that track specific tasks or products related to a work order[120]. Reference:

https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_work_orders.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_products_consumed_overview.htm&type=5

https://help.salesforce.com/s/articleView?id=sf.fs_work_order_line_items.htm&type=5