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

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.

The Dispatcher Console (Gantt) allows admins to customize which fields are visible in various panels and tooltips using standard Salesforce Field Sets.

A is correct (Resource Absence): You can control what information appears when a dispatcher hovers over a non-availability block (e.g., 'Sick Day,' 'Doctor's Appointment') by editing the field set on the Resource Absence object.

B is correct (Service Appointment): This is the most heavily customized object. You can configure field sets to control the columns in the Appointment List, the text shown on the Gantt bar, and the fields in the tooltip (hover).

C is correct (Service Resource): You can customize the resource list (left-hand side of the Gantt) to show fields like 'Vehicle Type,' 'Skill Level,' or 'Phone Number' by editing the field set on the Service Resource object.

Options D and E: Service Territory and Assigned Resource do not have direct field sets that control the Dispatcher Console layout in the same way the primary transactional objects do.

The Service Territory Member (STM) address defines the Start Location and End Location for the resource's route calculation.

Option C is correct. The requirement states that travel from Home to the Center is 'at the technician's expense' (i.e., off the clock). Therefore, the 'Official Company Route' begins when they arrive at the Service Center.

By setting the STM Address to the Service Center, the optimization engine assumes the technician is at the Service Center at the start of their shift.

The engine will then calculate travel time for: Service Center -> Job 1.

This matches the business requirement.

Option A (Home Address): If you set Home, the engine calculates: Home -> Job 1 (or Home -> Service Center). This would likely include the commute time in the daily schedule utilization, which contradicts the 'at technician's expense' (off-clock) requirement.

When running optimization (Global or In-Day), the engine is allowed to move any appointment that is not 'Pinned.'

Option C is correct. In Salesforce Field Service, you must explicitly define which statuses are considered Pinned (immovable) during optimization. This is configured in Field Service Settings > Optimization > Logic. If the 'In Progress' status is not selected in the 'Pinned Statuses' list, the optimization engine sees that appointment as movable. To improve the schedule, it might unassign the current tech and assign a different one, even though the tech is already on-site.

Ensuring 'In Progress' is 'excluded from optimization logic' (Pinned) forces the engine to schedule around that appointment rather than moving it.

Option B refers to 'Status Transitions,' which controls the lifecycle flow (e.g., New -> Scheduled -> In Progress) but does not control the scheduling engine's permission to move the job.

This question tests the Maintenance Plan generation logic.

Option D is correct. The requirement is Single Visit (One Appointment) for Multiple Assets.

One Work Order Line Item per Asset: This groups all the assets under a single parent Work Order. Each asset gets its own line item (WOLI) for tracking purposes.

One Service Appointment per Work Order: This creates a single appointment for the parent Work Order. The technician arrives once and works through the list of line items (Assets).

Option B ('One Work Order per Asset') would create separate Work Orders (and likely separate Appointments) for every single asset, resulting in multiple visits or a cluttered schedule.

Option C ('One SA per WOLI') would explicitly create a separate appointment for every single asset line item, causing massive double-booking/overlap.