Salesforce AP-209 Practice Exam Questions & Answers

Resource Preferences are supported on Work Order Line Items, which makes the parent/child Work Order pattern fully usable for jobs that require specific resources with specialized skills.

Option C is correct. Resource Preferences can be added directly to the Work Order Line Item, with type 'Required' or 'Preferred', referencing the Service Resource(s) qualified for the specialized work. The scheduling engine respects those preferences when picking candidates for the WOLI's Service Appointment.

Option A is incorrect because Resource Preferences are supported in Complex Work scenarios, including WOLI-based hierarchies.

Option B is incorrect because Resource Priority ranks all resources globally; it doesn't target specific resources for a specific Work Order Line Item.

Option D is incorrect because Resource Preferences are supported on WOLI out of the box and do not require redesigning the data model.

Work Rules are hard constraints that filter candidates in or out, while Service Objectives are soft constraints that rank the remaining candidates. The 40-mile radius is a strict eligibility rule, while preferring contractors over internal employees is a preference.

Option D is correct. A Work Rule (such as Maximum Travel From Home with a Relevance Group for contractors) enforces the 40-mile radius as a hard filter --- contractors beyond that distance are excluded from the candidate list. A Service Objective (such as a Resource Preference or Resource Priority objective) is the correct mechanism to rank contractors above internal employees while still allowing internal employees to be considered when no contractor is available.

Option A is incorrect because a Service Objective cannot enforce the maximum travel as a hard rule; it would only score it.

Option B is incorrect because using a Work Rule for the contractor preference would exclude internal employees, violating requirement #1.

Option C is incorrect because the roles of the rule types are reversed --- travel limit needs to be a Work Rule and preference needs to be a Service Objective.

Global Optimization will not move appointments that are pinned by status, pinned by checkbox, or otherwise constrained by their own scheduling parameters such as an Arrival Window the customer already agreed to.

Option A is correct. Once an Arrival Window is defined on a Service Appointment, the optimizer treats the start time as fixed within that window. If most appointments already have tight Arrival Windows, the optimizer has very little room to move them.

Option B is correct. Appointments in a 'Pinned' status (configured under Field Service Settings Optimization Pinned Statuses) are excluded from optimization moves entirely.

Option D is correct. The 'Pinned' checkbox on the Service Appointment locks the appointment to its scheduled time, regardless of status. Optimization will not move pinned appointments.

Option C is incorrect because if appointments are scheduled in violation of Work Rules, optimization would typically reschedule them to a compliant slot, not leave them in place.

Option E is incorrect because high priority makes appointments more important to schedule, not less likely to move; the optimizer is free to relocate high-priority work.

The goal is to fit high-priority work into a schedule already filled with low-priority work.

Option B is correct. The system must know that the Repair jobs are more important than the Maintenance jobs. This is handled by the Scheduling Priority field (used in the optimization logic to decide which job to drop if there is a conflict) or the Priority field mapped to Service Objectives.

Option C is correct. Global Optimization is the best tool here. It will look at the entire week, see the high-priority unscheduled jobs, and the low-priority scheduled jobs. It will then un-schedule or move the maintenance jobs to make room for the urgent repairs.

Option D is correct. For Optimization to work, the existing maintenance appointments must not be Pinned. If they are pinned, the optimizer treats them as immovable rock, and it won't be able to free up the time needed for the repairs.

Option A (Manual assignment) is inefficient and risky (could double-book). Option E (Resource Schedule Optimization) optimizes one person at a time; Global Optimization is better suited for balancing the load across the whole territory.

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.

This option follows the standard Salesforce Field Service data model and best practices for the 'Lead-to-Cash-to-Service' lifecycle.

Option C is correct.

Assets: Standard automation (or CPQ) converts Opportunity Line Items into Asset records.

Warranties: Standard Asset Warranty or Entitlement records track the 90-day coverage.

Maintenance: If a recurring service contract is sold, the correct objects are Service Contract (the agreement) and Maintenance Plan (the schedule/generation engine). The specific assets covered are linked via Maintenance Assets.

Option A is manual and error-prone.

Option B recommends a custom object ('Capital Equipment') when the standard Asset object exists specifically for this purpose.

Option D puts lists on the Account, losing the granularity of which specific asset is covered.

Offline capabilities are a critical feature of the Field Service mobile app.

Option E is correct: The fundamental behavior of the app is to 'Prime' (download for offline use) the inventory associated with the Service Resource. This ensures that when a technician is in a basement with no signal, they can still view their van stock and consume parts (create Product Consumed records).

Option B is correct: Salesforce Field Service supports Multi-Location Inventory (e.g., a technician has a Van location and a Garage location). The app is capable of priming these additional locations so the tech can transfer stock between them. However, consultants must be aware of data volume limits (priming thousands of parts can slow down sync times), so configuration settings restrict how far back or how many items are synced.

Option D is incorrect because the app specifically allows for the consumption of parts while offline; the transactions sync back to the server once connectivity is restored.