Salesforce AP-209 Exam With Confidence Using Practice Dumps

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.

The requirement is specifically to free up white space on the Gantt when a tech finishes early.

Option D is correct. The Gantt chart visual blocks are drawn based on Scheduled Start and Scheduled End. If a tech finishes a 2-hour job in 30 minutes, the Gantt bar will remain 2 hours long unless the Scheduled End is updated. By using a Mobile Flow to update both the Actuals (for reporting) and the Scheduled (for the Gantt), the bar shrinks, revealing 1.5 hours of open availability for the dispatcher to utilize.

Option C is the "Purist" data view (don't change scheduled), but it fails the specific business requirement of allowing new work to be added immediately.

Option A suggests creating custom fields for the original times, which is a valid part of the solution (to keep a history), but Option D describes the core functional mechanism (Flow updating the standard fields) required to achieve the Gantt behavior. The "Offline" warning in A is true but D is the more direct configuration answer.

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.