ACME Utilities would like to include their Assets (such as 'Cranes' and 'Excavators') in scheduling along with the Service Resources. As there might be a limited number of Assets for a particular job, they want those to be included in the scheduling process so that asset usage can be optimized.
How can this be achieved?
Salesforce Field Service schedules Service Resources, not Assets. To bring physical equipment into the scheduling engine, the equipment must be modeled as a Service Resource so the engine can check its availability, capacity, and skills.
Option D is correct. To include cranes, excavators, or any other equipment in scheduling, ACME must create Service Resource records for them (typically with a 'Resource Type' such as 'Equipment'). These records consume Field Service licenses, and once configured they participate in the candidate evaluation, capacity, and optimization just like a human technician.
Option A is incorrect because there is no 'Use for Scheduling' Boolean on the Asset object; Assets and Service Resources are separate concepts.
Option B is incorrect because a lookup field does not make the Asset part of the scheduling engine --- it is just a reference.
Option C is incorrect because the Dispatcher Console does not expose an 'Include Assets' toggle on the Schedule action.
Universal Containers outsources maintenance work to a third-party contractor who has agreed to provide a total of 20 hours of availability per day between 9:00 AM and 5:00 PM. Universal Containers' internal resources work 8:00 AM to 8:00 PM including overtime.
How should a consultant configure the contractor resources to meet this requirement?
When a contractor company provides aggregate hours rather than a list of named technicians, the correct model is a Capacity-Based Resource so the engine schedules against capacity in hours, not against a specific individual.
Option A is correct. A Capacity-Based Resource lets you express '20 hours per day' as capacity, assign Operating Hours of 9:00 AM--5:00 PM that match the contractor's agreed window, and add the 'maintenance' skill to restrict the type of work routed to them.
Option B is incorrect because preferring contractors is a soft preference; it does not enforce the contractor's distinct hours or capacity.
Option C is incorrect because creating a separate Service Territory does not, by itself, model contractor capacity or restrict the work type assigned.
Option D is incorrect because a Named Resource represents a single person, not a company providing aggregate hours, and the Designated Work approach does not capture the daily capacity cap.
Dispatchers have noticed that every time they run Global Optimization it fails. They have verified that the 'Optimization User' is active.
How can an admin troubleshoot this issue?
When Global Optimization fails, the issue is often related to data quality, scheduling configuration, or constraint validity rather than user permissions. Field Service provides a built-in diagnostic tool to surface such issues.
Option D is correct. The 'Health Check' tool, when run with 'Horizon Based Validations', evaluates the data, Scheduling Policy, Operating Hours, Service Resources and Service Appointments in scope of the optimization run. It surfaces issues such as missing geolocations, invalid time slots, missing skills, and inactive resources, which are common causes of optimization failures.
Option A is incorrect because logging a support ticket should be the last resort, not a first troubleshooting step. The admin should first attempt to identify the root cause using built-in diagnostics.
Option B is incorrect because Permission Sets are required for users who initiate optimization, but the question already confirms that the 'Optimization User' is active. Permission Sets would prevent the optimization from starting, not cause it to fail mid-run.
Option C is incorrect because if Optimization were not enabled, the dispatchers wouldn't be able to invoke it at all.
Universal Containers broadly has two sets of service resources: Internal employees and contractors. They have the following requirements while assigning the Service Appointments to them:
1. Contractors will be working on maintenance work, but internal employees can also handle work if the contractor is unavailable. 2. Contractors to cover only a 40-mile radius around its office.
Which recommendation should a consultant make to meet their requirements?
Work Rules are hard constraints that filter candidates in or out, while Service Objectives are soft constraints that rank the remaining candidates. The 40-mile radius is a strict eligibility rule, while preferring contractors over internal employees is a preference.
Option D is correct. A Work Rule (such as Maximum Travel From Home with a Relevance Group for contractors) enforces the 40-mile radius as a hard filter --- contractors beyond that distance are excluded from the candidate list. A Service Objective (such as a Resource Preference or Resource Priority objective) is the correct mechanism to rank contractors above internal employees while still allowing internal employees to be considered when no contractor is available.
Option A is incorrect because a Service Objective cannot enforce the maximum travel as a hard rule; it would only score it.
Option B is incorrect because using a Work Rule for the contractor preference would exclude internal employees, violating requirement #1.
Option C is incorrect because the roles of the rule types are reversed --- travel limit needs to be a Work Rule and preference needs to be a Service Objective.
Green Energy Solutions decided to start selling maintenance services to their install base of solar panels, in addition to the solar panel itself. GES would like better visibility into the value their maintenance contracts provide to customers by tracking the availability and reliability of their solar panels.
Which calculation is correct?
Salesforce Field Service uses two distinct KPIs for service contracts: Availability and Reliability. The two differ in whether planned downtime (scheduled maintenance) is counted against the asset.
Option C is correct. Availability measures the proportion of expected uptime that the Asset was usable, excluding only unplanned downtime. Planned maintenance is expected and excluded from the calculation, so Availability = (expected uptime - unplanned downtime) / expected uptime.
Option D is partially right in form but mislabeled --- Reliability is the metric that subtracts both planned and unplanned downtime: Reliability = (expected uptime - planned - unplanned downtime) / expected uptime. Mislabeling it as the Availability formula (Option A) is incorrect.
Option A is incorrect because that is the Reliability formula, not Availability.
Option B is incorrect because Asset Uptime is the numerator of these formulas, not a ratio of Availability divided by Reliability.
Crystal Taylor
15 days agoJustin Flores
24 days agoThomas Brown
2 months agoAngela Sanchez
2 months agoMatthew Nguyen
2 months agoAndrew Bailey
3 months agoDeborah Morgan
3 months agoJoshua Baker
3 months agoAnthony Williams
2 months agoRyan White
2 months agoNobuko
4 months agoDevora
4 months agoDaryl
4 months agoMagnolia
4 months agoLazaro
5 months agoLatia
5 months agoCarole
5 months agoPhuong
6 months agoStephen
6 months agoMy
6 months agoErinn
6 months agoHerminia
7 months agoRanee
7 months agoDewitt
7 months agoLouis
7 months agoArlette
7 months ago