AP-209 Exam Dumps - Advanced Field Service Accredited Professional

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.

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.

To send push notifications to the Field Service mobile app based on specific criteria, you need both the configuration and the automation.

Option B is correct: You must first enable and configure Custom Notifications for the Field Service Connected App. This ensures the mobile device is capable of receiving and displaying the specific notification type.

Option D is correct: You need an automation trigger (Record-Triggered Flow) to detect the specific business condition: The Service Appointment Status changes to 'Dispatched' AND the Priority (or Work Type) is 'Emergency'. The flow then executes the "Send Custom Notification" action targeting the Assigned Resource user.

Option A and C refer to "Jeopardy," which is a different feature used to warn dispatchers about impending SLA violations, not to notify technicians of new work.

This question addresses the trade-off between Customer Experience and Schedule Optimization.

Reducing the arrival window (e.g., from 4 hours to 2 hours) is a common strategy to improve customer service. Customers prefer shorter wait times and more precise appointments. However, a consultant must identify the technical impact of this business decision.

Option B is correct because it acknowledges the benefit (customer experience) while correctly identifying the risk. Smaller arrival windows serve as tighter constraints on the scheduling engine (Optimization). The engine has less "wiggle room" to shuffle appointments, which can lead to lower overall utilization or higher travel times.

Option C is incorrect because reducing the window decreases (restricts) flexibility for optimization, it does not increase it.

Options A and D suggest increasing the window to 8 hours. While this is great for the optimization engine (maximum flexibility), it is generally considered a poor customer experience to ask a prospect to wait all day (8 hours), contradicting the business goal of being "more competitive."