Salesforce AP-209 Dumps - Pass Advanced Field Service Accredited Professional Exam in 2026

Operating Hours model the working schedule, while Skills model what kind of work a resource is qualified to perform. Combining the two correctly meets both the availability and the work-type filter.

Option B is correct. Separate Operating Hours definitions allow you to model the different working hours and time zones used by internal vs. third-party resources. Using Skills to restrict the contractor resources to maintenance work is the standard way to enforce the type of work they should perform, by tagging the relevant Work Types (or Work Orders) with a 'Maintenance' skill that only the contractors hold.

Option A is incorrect because 'Designated Work' Time Slots are normally used to reserve specific blocks of time for a specific category of work --- they are not designed to restrict a resource exclusively to maintenance across all its working hours.

Option C is incorrect because using only Shifts on top of a single Operating Hours record adds unnecessary complexity when the schedules differ structurally; separate Operating Hours definitions are cleaner.

Option D is incorrect for the same reason, and because it does not include any mechanism to restrict the contractors to maintenance work only.

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.

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.

Priming is the process of caching data on the device so that the technician can work offline. Priming has limits, can be tuned, and must be combined with scoped list views to keep the device fast and accurate.

Option B is correct. Not every object and record is primed by default. The implementation team must map out which related records (Account, Contact, Asset, Knowledge, etc.) need to be available offline and configure priming or briefcase rules accordingly.

Option D is correct. A very low Schedule Update Frequency Time forces the device to sync constantly, draining battery and consuming bandwidth even when the technician is offline or on a poor connection. The frequency must be tuned to balance freshness against device and network impact.

Option E is correct. Scoping list views to the technician's own appointments (e.g., the next 7 days, my assignments) keeps the offline data set small and relevant, which improves performance and reduces sync time.

Option A is incorrect because the SFS Mobile App syncs automatically when connectivity is restored; the technician does not need to manually trigger a Data Sync.

Option C is incorrect because Product and Pricebook access offline is governed by priming and inventory configuration, not by whether the technician has reviewed them on the desktop.

This scenario involves two distinct types of work (Installation vs. Training) with different durations and likely different skill requirements, but they are part of the same customer order.

Option C is correct.

Data Model: Using Work Order Line Items (WOLIs) is the best practice here. You create one WOLI for the 'Installation' (linked to a Work Type that allows Multi-Day) and a separate WOLI for 'Training' (linked to a different Work Type). This allows you to track the status and skills for each part separately.

Dependency: Using Complex Work (specifically a 'Start After Finish' dependency) ensures the Training appointment cannot be scheduled until the Installation is complete.

Option A puts both Appointments on the same Work Order parent. While possible, it makes it harder to report on 'Training' vs 'Install' costs separately and limits the ability to use different Work Types for each appointment automatically.

Option B relies on manual updates or custom automation ('When scheduled, update...'), whereas Complex Work (Option C) handles the logic natively during optimization.