Salesforce AP-209 Practice Exam Questions & Answers (2026)

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.

This question tests your understanding of Salesforce Field Service License types (Dispatcher, Technician, Contractor).

1 Dispatcher: Although not explicitly stated as a user in the text, you always need at least one dispatcher license to manage the schedule. (Typically implied in licensing questions unless '0' is an option).

2 Technicians: Territory A has '2 internal resources'1. Internal mobile workers require the standard Field Service Mobile (Technician) license.

2 Contractors (Capacity-Based): The question states '2 contractors set as capacity-based resources: ABC and XYZ.' 2 These are the 'Bucket' accounts. In Salesforce, even capacity-based container users often consume a license (typically a Contractor or Community Plus login) to access the portal/community where they might view their aggregate schedule.

7 Contractors (Individuals): The question specifies 'ABC... has 3 individual resources and XYZ... has 4 individual resources'3. Even if the scheduling is done at the capacity (bucket) level, if these 7 people need to log in to the app or community to close jobs, they each need a license.

Result: 1 Dispatcher + 2 Technicians (Internal) + 2 Contractors (The Managers/Buckets) + 7 Contractors (The Workers) = Option D.

(Note: Licensing models can be complex. In some strictly capacity-based models, you might not license the 7 individuals if they never log in, but Option D is the most complete answer reflecting a standard model where all participants need system access).

Salesforce Field Service provides a standard object specifically designed to track when an Asset is unavailable, so that availability and reliability KPIs can be reported accurately.

Option D is correct. 'Asset Downtime Periods' is the standard out-of-the-box object that records when an Asset is down, including the start and end time and whether the downtime was planned or unplanned. These records are used to calculate Availability and Reliability metrics, and they integrate with maintenance and service contract reporting.

Option A is incorrect because 'Asset Timelines' is a visualization tool that displays Asset history, not the data store that captures downtime.

Options B and C are incorrect because a custom object or custom fields would duplicate functionality that Salesforce already provides natively, and would not integrate with the standard Availability/Reliability calculations.

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.

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.