Field-Service-Consultant Exam Questions

Explanation:

Frequency is a field on the Maintenance Plan object that defines how often work orders should be generated from maintenance plans such as daily, weekly, or monthly[228]. Generation Timeframe is a field on the Maintenance Plan object that defines how many work orders should be generated from maintenance plans at a time such as 1, 2, or 12[229]. Auto-generate work orders is a field on the Maintenance Plan object that enables or disables the automatic generation of work orders from maintenance plans[230]. Setting Frequency to 1 Month; Generation Timeframe of 12; uncheck Auto-generate work orders would allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit by creating maintenance plans that generate one work order per month for 12 months but do not generate them automatically until the customer calls[231]. Setting Frequency to 1 Month; Generation Timeframe of 1; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for one month and generate them automatically without waiting for customer calls.

Setting Frequency to 1 Month; Generation Timeframe of 12; check Auto-generate work orders would not allow Universal Containers to offer customers a Maintenance Plan that provides 12 monthly checkups where the customer will call to schedule each visit. It would create maintenance plans that generate one work order per month for 12 months and generate them automatically without waiting for customer calls. Setting Frequency to 1 Month; Generation Timeframe of 1; uncheck Auto-generate work orders would not allow Universal Container

Explanation:

This option allows creating a record to request products from another inventory location and adding product request line items for each product requested.

References:

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

Explanation:

Creating a new Service Appointment on the original Work Order is the best option because it will allow Universal Containers to track the work that was done on the initial visit and the work that needs to be done on the return visit. Rescheduling the Service Appointment for the new date is also a good option because it will allow Universal Containers to track the date and time of the return visit.

The other two options are not as good because they will not allow Universal Containers to track the work that was done on the initial visit. Creating a new Work Order and Service Appointment would create a new record for the return visit, which would not be linked to the original Work Order. Rescheduling the Work Order for the new date would reschedule the entire Work Order, including the initial visit, which would not be accurate.

Explanation:

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]. References:

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&t ype=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&type=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

Explanation:

Service Territories are used to group resources and service appointments based on geographic areas or other criteria. The recommended limit for service appointments per territory per day is 500 for optimal performance and user experience.

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

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

Explanation:

This option reflects the sharing rules for Service Appointments, which grant access to the assigned resources, the owner of the record, and the members of the service territory associated with the record.

References:

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

Explanation:

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.

References:

https://developer.salesforce.com/docs/componentlibrary/documentation/en/lwc

https://developer.salesforce.com/docs/atlas.enus.lightning.meta/lightning/

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

Explanation:

To perform multi-staged jobs, where the second job can only begin after completion of the first job, two service appointments can be created and linked by setting the Related Service Appointment field on the second service appointment to point to the first one, and setting the Time Dependency field to After Previous. Creating one service appointment with the total duration of the two jobs and assigning two resources would not ensure that the second job starts after the first one. Creating two service appointments and scheduling them to the same resource or creating one service appointment and scheduling it to two different resources would not create a dependency between the jobs.

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

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

Explanation:

Drip Feed Dispatching is a feature that allows dispatching groups of service appointments to technicians at regular intervals instead of all at once[121]. Enabling Drip-feed to dispatch the next appointments would allow Northern Trail Outfitters to improve overall responsiveness to customers by providing the greatest schedule flexibility and allowing technicians to adjust their schedules based on real-time conditions[122]. Shuffling daily work manually via the Gantt would not provide the greatest schedule flexibility. The Gantt is a tool that allows dispatchers to view and manage service appointments on a timeline[123]. Leveraging Resource Schedule Optimization would not provide the greatest schedule flexibility.

Resource Schedule Optimization is a feature that allows optimizing service appointments based on predefined criteria such as travel time or priority[124]. Configuring the Auto Dispatch scheduled job would not provide the greatest schedule flexibility. Auto Dispatch is a feature that allows automatically assigning service appointments to resources based on predefined criteria such as skills or availability[125].

References:

https://help.salesforce.com/s/articleView?id=sf.fs_drip_feed_dispatching_overview.htm&typ e=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_gantt_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_resource_schedule_optimization_overvie w.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fs_auto_dispatch_overview.htm&type=5

Explanation:

These two configurations allow adding a new status to the existing status flow for Service Appointments, and defining which statuses can transition to or from the new status. References: https://help.salesforce.com/s/articleView?id=sf.fs_status_transitions.htm&type=5