Universal Containers offer repair services for customers' capital equipment. Sometimes, a customer may ask a repair technician to take a look at another piece of equipment while they're on-site.
How can Universal Containers give the field worker the flexibility to extend the time on site and track that they performed service on another piece of equipment?
Answer : D
This requires a balance of data accuracy (tracking the asset) and schedule accuracy (updating the duration).
Option D is correct because it uses Field Service Mobile Flows, which is the best practice for guiding technicians through complex processes.
Data: Creating a Work Order Line Item (WOLI) is the correct data model to track work done on a specific (secondary) Asset under the main Work Order.
Schedule: The flow can update the current Service Appointment's Duration and Scheduled End to reflect the reality that the tech will be there longer.
Automation: Triggering a 'Scheduling Recipe' (now typically handled via Flows/Optimization services) ensures that if the appointment runs long, subsequent appointments for the day are automatically shifted (Reshuffled) to prevent overlapping/late arrivals.
Options A and C fail to update the schedule duration, meaning the tech will likely be late to their next job without the dispatcher knowing. Option B creates a second appointment, which is administratively heavy for 'just looking at' another asset during the same visit.
Universal Containers has family-friendly Scheduling Policies and wants to allow Service Resources to miss work for 'Family Time'. The Resource Absence functionality can be configured to meet this requirement.
Which three statements are true about Resource Absence? (Choose 3 options)
Answer : B, D, E
Resource Absence is a flexible object that supports custom values, but it has specific behavior on the SFS Mobile App and in the scheduling engine that admins must understand.
Option B is correct. The SFS Mobile App creates Resource Absence records using the default record type. To ensure those absences are honored by Auto-Schedule and Global Optimization, the 'Non-Availability' record type must be the default --- otherwise the engine ignores them.
Option D is correct. The standard 'Type' picklist on Resource Absence includes Vacation, Meeting, Training, and Medical out of the box. Admins can add custom values, but these are the seeded options.
Option E is correct. The SFS Mobile App's Profile tab includes an Absences section where Service Resources can view and create their own absences, which feeds directly into the Gantt and the optimizer.
Option A is incorrect because custom Type values do show on the Gantt; absences appear as colored bars on the resource row regardless of the Type value used.
Option C is incorrect because the optimizer considers all Resource Absence records with a Non-Availability record type, regardless of whether the Type value is standard or custom.
Universal Container's object model uses a Work Order / Work Order Line Item (parent/child) relationship. Several jobs will have required resources with special skills to execute.
How would an admin configure this?
Answer : C
Resource Preferences are supported on Work Order Line Items, which makes the parent/child Work Order pattern fully usable for jobs that require specific resources with specialized skills.
Option C is correct. Resource Preferences can be added directly to the Work Order Line Item, with type 'Required' or 'Preferred', referencing the Service Resource(s) qualified for the specialized work. The scheduling engine respects those preferences when picking candidates for the WOLI's Service Appointment.
Option A is incorrect because Resource Preferences are supported in Complex Work scenarios, including WOLI-based hierarchies.
Option B is incorrect because Resource Priority ranks all resources globally; it doesn't target specific resources for a specific Work Order Line Item.
Option D is incorrect because Resource Preferences are supported on WOLI out of the box and do not require redesigning the data model.
Dispatchers want a visual representation of when Service Appointments are getting closer to their due date on the 'Dispatcher Console'.
How can this requirement be solved?
Answer : A
The Dispatcher Console exposes the Gantt Palette feature, which lets admins color-code appointments based on field values. This produces immediate visual cues for dispatchers without leaving the Gantt.
Option A is correct. Gantt Palette rules let an admin paint appointments in different colors based on field-level criteria --- for example, red when Due Date is within 24 hours, amber within 3 days, green otherwise. The visual is exactly the kind of glance-and-go indicator the dispatchers asked for.
Option B is incorrect because a daily email report does not give an in-context visual on the Gantt.
Option C is incorrect because hover-to-read requires dispatchers to actively check each appointment, defeating the purpose of a visual indicator.
Option D is incorrect because a column in the list shows the value but does not produce a visual representation that scales across many appointments at once.
A customer provides services for a variety of products, and the capability for resources to perform services is often machine-specific. The customer explains that there are about 100 combinations of services and products that a single resource may support, and is concerned about performance.
Which configuration option should a consultant recommend?
Answer : B
This question addresses the limits of Skills (Work Rules) vs. Extended Match (Custom Criteria).
Option B is correct. This offers the most efficient hybrid approach9.
Skills: Use standard Skills for the 'Service Type' (e.g., 'Repair,' 'Install'). This is simple and low-volume.
Extended Match: Use the Extended Match Work Rule to handle the 'Product' matching. Instead of creating thousands of skills (e.g., 'Repair-ModelX,' 'Repair-ModelY'), you create a custom object or field logic that matches the Asset's Product to a list of Products Supported on the Resource's record. Extended Match is designed exactly for this 'Pattern Matching' without polluting the Skills table.
Option C is incorrect because creating a unique skill for every combination (100+ per resource) leads to 'Skill Explosion.' This bloats the data model and degrades optimization performance10.
A customer doesn't want contractors to be considered in optimization runs.
How can a consultant implement this requirement?
Answer : D
To exclude a specific subset of resources from being scheduled by the optimization engine, you use a Hard Constraint Work Rule.
Option D is correct. The Match Boolean Work Rule is designed to filter resources based on a checkbox (Boolean) field.
You would create a custom checkbox on the Service Resource object (e.g., Is_Contractor__c).
You configure the Match Boolean rule in the Scheduling Policy to enforce that Is_Contractor__c must be False.
When optimization runs, any resource where Is_Contractor__c = True fails the rule and is completely ignored/excluded from the schedule calculation.
Option A (Count Rule) limits volume, it doesn't exclude.
Options B and C (Match Field/Extended Match) match properties between the Job and the Resource (e.g., Skill or Location matching), which is not the same as a blanket exclusion of a resource type.
A customer shares with the consulting partner that the dispatchers, mobile resources and planners are very frustrated with the fact that the old Field Service system and processes are being replaced. They keep on saying that they won't be using the new system and that they are tired from all the changes within the company.
What should a consultant recommend in this case?
Answer : C
Change management is one of the biggest risks on any Field Service implementation. When end-users are openly resistant, the consultant must adjust scope and approach rather than push more technology on top of the unrest.
Option C is correct. Investing in training reduces fear of the unknown and gives users confidence with the new tool. Phasing the rollout to a single Business Unit or Service Territory limits blast radius, lets the team build success stories, and turns early adopters into advocates for the broader rollout. This is a textbook change-management response.
Option A is incorrect because adding more new functionality (the Mobile App) to a team that is already overwhelmed will increase resistance, not reduce it.
Option B is incorrect because outsourcing the work does not address the user adoption problem and may further demoralize the existing staff.
Option D is incorrect because adding more automation does not solve cultural resistance; users need to understand and trust the system before automation will be embraced.