Salesforce Field-Service-Consultant Salesforce Certified Field Service Consultant (SP25) Exam Practice Test

These two conditions would make the optimizer run slower and leave many Service Appointments unscheduled, as it would have to evaluate too many possible scenarios and combinations. &type=5

This feature shouldbe used to reduce travel time and increase technician productivity by automatically scheduling service appointments based on predefined criteria and objectives, such as minimizing travel distance or maximizing utilization. &type=5

Soft Boundaries and Customer First are two default scheduling policies that meet the requirement of committing preferred resources to accounts and providing prompt service. Soft Boundaries prioritize resources that are assigned to the same account or service territory as the service appointment. Customer First prioritize resources that have the highest customer satisfaction rating.

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 listof 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 thatshows 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. References: &type=5 &type=5 &type=5 & &type=5

This option allows creating a record to request products from another inventory location and adding product request lineitems for each product requested. &type=5

This option allows viewing the asset relationships on the Asset object, where the primary asset is the parent asset and the related assets are the child assets. &type=5

This option allows visualizing the planned travel route for a technician on a map, based on the street-level directions and traffic conditions. &type=5

This option allows generating a report in the customer’s language by selecting the language from a picklist field on the work order record. &type=5

Match Boolean is an optimization criterion that prioritizes matching service appointments with resources based on boolean fields such as certifications or preferences[139]. Using Match Boolean in the Scheduling Policy would allow Universal Containers to ensure that Service Appointments are only assigned to Active Resources bycreating a boolean field on the service resource object such as Active Resource and setting it to true or false depending on their status. Match Fields is an optimization criterion that prioritizes matching service appointments with resources based on fields such as skills or territories[140]. Preferred Resources is an optimization criterion that prioritizes assigning service appointments to resources who have previously completed similar work orders or who are preferred by customers[141]. Required Resources is an optimization criterion that prioritizes assigning service appointments to resources who are explicitly required by customers or dispatchers[142]. References: & &type=5 & &type=5

Assets are records that represent products or equipment that customers have purchased or installed[174]. Related Assets are records that track the relationships between assets such as parent-child or swap[175]. Product Requests are records that track the products or parts that are requested, transferred, or returned for a service appointment[176]. Adding the Related Asset related list to the Asset Page and configuring the Product Request object would allow Universal Containers to track the Asset lifecycle when equipment has been swapped out by creating related asset records forswapped assets and creating product request records for transferring or returning assets[177]. Adding the field history tracking related list to the Asset Page would not track the Asset lifecycle when equipment has been swapped out. Field history trackingis a feature that allows tracking changes to specific fields on an object over time[178]. Configuring the Asset Relationship object would not track the Asset lifecycle when equipment has been swapped out. Asset Relationship is an object that defines the types of relationships between assets such as parent-child or swap[179].References: &type=5 &type=5 &type=5 &type=5 &

Lightning Components are reusable units of user interface that can be customized and embedded in different pages or apps[180]. Work Order Line Items are records that track specific tasks or products related to a work order[181]. Creating a custom Lightning Component that displays Work Order progress and deploying it to Technicians through the Salesforce Field Service mobile app would allow Universal Containers’ Technicians to view work progress through the Work Order Line Item card in the Salesforce Field Service mobile app by creating a component that shows the status or completion percentage of work order line items and adding it to the work order line item card layout in the mobile app settings[182]. Creating a custom Visualforce page and adding an external link in the Salesforce Field Service mobile app to view the page in the mobile browser would not allow Technicians to view work progress through the Work Order Line Item cardin the Salesforce Field Service mobile app. Visualforce pages are web pages that can display custom user interface using HTML, CSS, JavaScript, and Apex[183]. Creating a Report Chart that summarizes Work Order Line Items and adding a link to the Service Appointment layout would not allow Technicians to view work progress through the Work Order Line Item card in the Salesforce Field Service mobile app. Report Charts are visual representations of report data that can be added to different pages or layouts[184]. Adding the Work Order Line Items related list to the Work Order page layout and assigning the layout to the Technician’s profile would not allow Technicians to view work progress through the Work Order Line Item card in the Salesforce Field Service mobile app. Related lists are lists of records that are directly related to another record and can be added to different page layouts[185]. References: &type=5 &type=5 & &type=5

This option allows creating a service resource that represents a group oftechnicians who work together on the same service appointment. &type=5

Soft Boundariesand Customer First are two default scheduling policies that meet the requirement of committing preferred resources to accounts and providing prompt service. Soft Boundaries prioritize resources that are assigned to the same account or service territory asthe service appointment. Customer First prioritize resources that have the highest customer satisfaction rating.

Generation Horizon is a setting that defines how far in advance work orders should be generated from maintenance plans[126]. Defining a generation horizon of 14 days would allow Universal Containers to automatically generate Work Orders 14days before the next suggested maintenance date by creating work orders from maintenance plans within 14 days of their scheduled date[127]. Defining a generation timeframe of 14 days would not automatically generate Work Orders 14 days before the next suggested maintenance date. Generation Timeframe is a setting that defines how often work orders should be generated from maintenance plans[128]. Configuring Auto-generate Work Orders to True would not automatically generate Work Orders 14 days before the next suggested maintenance date. Auto-generate Work Orders is a setting that enables or disables the automatic generation of work orders from maintenance plans[129]. Defining a generation horizon of 20,160 minutes would not automatically generate Work Orders14 days before the next suggested maintenance date. Generation Horizon is measured in days, not minutes[130]. References: &type=5 &type=5 &type=5 & &type=5

Earliest Start Permitted is a field on the Service Appointment object that defines the earliest date and time that a service appointment can start[222]. Due Date is a field on the Service Appointment object that defines the latest date and time that a service appointment must be completed by[223]. Using Earliest Start Permitted and Due Date fields on Service Appointments would help ensure that they are completed within the agreed upon Service Level Agreement (SLA) with Universal Containers’ customers by setting the boundaries for when a service appointment can start and finish according to the SLA terms[224]. Actual Start andActual End are fields on the Service Appointment object that capture the actual date and time that a service appointment started and ended[225]. Using Actual Start and Actual End fields on Service Appointments would not help ensure that they are completedwithin the agreed upon SLA with Universal Containers’ customers because they are recorded after the service appointment is performed and do not enforce any SLA terms. Arrival Window Start and Arrival Window End are fields on the Service Appointment objectthat define the expected date and time range that a resource will arrive at a service appointment[226]. Using Arrival Window Start and Arrival Window End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers’ customers because they only indicate when a resource will arrive and do not enforce any SLA terms. Scheduled Start and Scheduled End are fields on the Service Appointment object that define the planned date and time range thata service appointment will take place[227]. Using Scheduled Start and Scheduled End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers’ customers because they only indicate whena service appointment is scheduled and do not enforce any SLA terms. References: &type=5

This option allows capturing multiple signatures on a service report by creating different signature types (such as customer approval or technician verification) and adding themto the service report template. &type=5

This option allows handling unplanned service during times of severe weather by creating a policy that overrides the existing scheduling policy and using a wizard to reschedule service appointments based on the emergency policy. &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. References: &type=5 & &type=5

Inventory is used to track product quantities in different locations such as warehouses or vans. Products Consumed are used to report when parts are used by technicians during service appointments and adjust inventory levels accordingly. Mobile Locations are used to track inventory in technicians’ vans or trucks using geolocation data from their mobile devices. Warehouse Locations are used to track inventory in fixed locations such as warehouses or depots using address data from their records. Products Required are used to request products from inventory for a service appointment, butdo not ensure that technicians report when parts are used. References: &type=5 & &type=5

This option allows tracking the required work for each machine separately, and scheduling a service appointment for each work order line item. &type=5

Drip feed is a feature that automatically dispatches service appointments to resources based on predefined criteria and time intervals. By enabling drip feed, the system can dispatch one service appointment per technician at a time, and adjust their schedule accordingly.

Work Types are templates that define the duration, skills, and products required for a work orderor work order line item. By creating Work Types for Install, Break-fix, and Inspections, Universal Containers can standardize creation of Work Orders with the correct skills and estimated time to completion[34]. Entitlement Templates are templates that define the terms of support for customers such as number of cases allowed or response time[35]. Entitlements are records that specify customers’ support terms based on their contracts or warranties[36]. Work Order Record Types are record types that allow creating different page layouts and picklist values for different types of work orders[37]. References: &type=5 &type=5 & &type=5

Thisoption allows updating the service crew to meet the skill requirements by adding service resources to the crew using a drag-and-drop interface. &type=5

This licensing will be required for the Field Service Schedule Optimization user, as it allows accessing Salesforce features and functionality such as optimization jobs and settings. &type=5

Field Service Lightning Admin Permissions are required to set up new territories, define new schedule policies, and control settings onthe Gantt chart. These permissions allow users to access and modify field service settings and objects.

A quick action is used tocreate a record from another record with predefined field values. By defining a quick action to create a new service appointment from an existing one, the technician can easily create an additional visit to complete unfinished work.

Drip feed dispatching is a feature that allows dispatching service appointments gradually throughout the daybased on a drip feed rate defined for each service territory or resource. If other scheduled jobs are dispatching appointments and exceeding the drip feed value, then the drip feed dispatching will not trigger as expected. The appointment status going fromScheduled to Completed or being Canceled, Completed, or Cannot Complete does not affect drip feed dispatching, as these are valid status transitions for dispatched appointments. The default drip feed setting does not override the drip feed rate on a service territory, but provides a fallback value if no rate is specified on the territory or resource level. References: &type=5 & &type=5

The technician would use a Return Order to create a return for the unused circuitboard. The Return Order would specify the quantity of the product being returned, the reason for the return, and the shipping address. The technician would then use a Product Receipt to record the receipt of the returned product. The Product Receipt wouldspecify the quantity of the product received, the condition of the product, and the location of the product.

The other two options are incorrect because they are not used to return products. A Work Order is used to track the work that needs to be done on aproduct or service. A Product Transfer is used to move products from one location to another.

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 accessto 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. References: &type=5 & &type=5

Products required and skill requirements are two fields that should be included when creating a work order to increase first-time fix rates. Products required are used to specify the products that are needed for the work order, andskill requirements are used to specify the level of expertise that is needed for the work order. By including these fields, the system can ensure that the technician has the right parts and skills to complete the work order.

Resource Availability Rules are rules that define when resources are available for service appointments based on their working hours, absences, breaks, travel time,etc.[77]. Using the Resource Availability Rule would allow configuring the Scheduling Policy to ensure a 30-minutelunch break that begins every day after 1 PM by setting up criteria such as break duration equals 30 minutes and break start time after 1 PM[78]. Creating a recurring Service Appointment would not ensure a 30-minute lunch break that begins every day after 1 PM. Recurring Service Appointments are service appointments that repeat at regular intervals such as daily, weekly, or monthly[79]. Using appropriate Resource Operating Hours would not ensure a 30-minute lunch break that begins every day after 1 PM. Resource Operating Hours are records that define when resources are available for work based on their time zones, business hours, holidays, etc.[80]. Creating Resource Absences every day would not ensure a 30-minute lunch break that begins every day after 1 PM. Resource Absences are records that mark resources as unavailable for work for specific time periods due to sickness, vacation, or other reasons[81]. References: &type=5 &type=5 &type=5 & &type=5

This option allows tracking each door lock as a unique product item with its own serial number and inventory location. &type=5

These two applications allow viewing all of the absence records at once, as they support displaying related lists on objects such as service resources or service territories. &type=5

A relevance group is used to filter resources based on a custom field value. By creating a relevancegroup on the work rule to filter based on the tier number, the system can prioritize resources with higher seniority for a service appointment.

This option allows tracking the time spent on each step of the work order line item and associating it with the time sheet entry record. &type=5

Maintenance Plans are records that define the recurring service schedule for an asset or a product such as quarterly, monthly, or weekly[59]. Configuring a Maintenance Plan would allow creating quarterlyservice appointments for one of the products sold by Universal Containers automatically based on predefined criteria such as start date, end date, or generation method[60]. Defining a repeating Work Type would not create quarterly service appointments automatically. Work Types are templates that define the duration, skills, and products required for a work order or work order line item[61]. Implementing Path for Work Orders would not create quarterly service appointments automatically. Path is a feature that displays key fields and guidance for each stage of a work order process[62]. Building a Process for Service Appointments would not create quarterly service appointments automatically. Processes are automated workflows that execute actions based on specified criteria such as updating fields, sending emails, or creating tasks[63]. &type=5 &type=5 &type=5 id=sf.path_overview.htm& &type=5

A work rule is used to define scheduling constraints and preferences for service appointments. The Match Territory work rule is used to ensure that service appointments are dispatched to resources from the same serviceterritory only.

These two objects are required when configuring an optimization job, as they define the scope and the criteria for the optimization process. &type=5

This feature should be configured to meet this requirement, as it allows creating a group of service resources that can perform periodic maintenance on complex products together. &type=5

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]. References: &type=5 &type=5 &type=5 id=sf.fs_service_crews_create_edit_delete.htm&

These three considerations should be taken into account when implementing service level agreements for work orders, as they affect how milestones are created and applied to work orders. &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

The book appointment action is used to schedule a service appointment based on service objectives and resource availability. Theaction displays a list of potential time slots with service objective scores for each slot. The higher the score, the better the slot meets the service objectives.

Polygons are geographic areas that define service territories for scheduling and optimization purposes. The Polygon Assignment Policy determines which polygon in a service territory hierarchy is used to assign service appointments to service resources based on their location or skills. Setting it to the Lowest Level ensures that service appointments are assigned based on the polygon of the child service territory in the hierarchy1. Setting it to the Highest Level would use the polygon of the parent service territory in the hierarchy1. TheTerritory Assignment Policy determines which territory in a hierarchy is used to filter available resources for scheduling. It does not affect polygon assignment. & &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 listto 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 relatedlist to the asset page would allow requesting products from inventory for an asset, but not tracking asset relationships. References: &type=5 &type=5 & &type=5

Drip feed is a feature that automatically dispatches service appointments to resources based on predefined criteria and time intervals. By using dripfeed, the system can handle same-day service appointments and adjust the technician’s schedule accordingly.

Multi-day service appointments are used when jobs can take longer than the available resources hours in a day or require consecutive days of work and can span over weekends. Jobs that need to be performed at the same site on the same day of the week or require multiple stages of workperformed by different resources can be handled by single-day service appointments with appropriate scheduling policies and optimization rules. &type=5