AP-209 Dumps with Practice Exam Questions Answers

Optimization Insights is the dedicated Field Service feature that captures per-run metrics such as travel time saved, utilization, gap minimization, and unscheduled work, making it the standard way to evaluate Global Optimization quality.

Option B is correct. Enabling Optimization Insights records the before/after metrics for each optimization request — travel minutes, scheduled vs. unscheduled count, average gap, and other KPIs. The data is available on the Optimization Request object and can be reported on directly in Salesforce.

Option A is incorrect because the SFS Dashboard package is an older, less precise tool that does not capture per-run optimization data.

Option C is incorrect because the Dispatcher Console is an operational view, not an analytics surface.

Option D is incorrect because subscribing to an Analytics App is unnecessary overhead when a built-in feature exists.

This question addresses the limits of Skills (Work Rules) vs. Extended Match (Custom Criteria).

Option B is correct. This offers the most efficient hybrid approach 9 .

Skills: Use standard Skills for the "Service Type" (e.g., "Repair," "Install"). This is simple and low-volume.

Extended Match: Use the Extended Match Work Rule to handle the "Product" matching. Instead of creating thousands of skills (e.g., "Repair-ModelX," "Repair-ModelY"), you create a custom object or field logic that matches the Asset's Product to a list of Products Supported on the Resource's record. Extended Match is designed exactly for this "Pattern Matching" without polluting the Skills table.

Option C is incorrect because creating a unique skill for every combination (100+ per resource) leads to "Skill Explosion." This bloats the data model and degrades optimization performance 10 .

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 addresses the "Shift vs. Operating Hours" architecture.

Option B is correct. When a schedule has no consistent weekly pattern , using standard Operating Hours (which repeat Mon-Sun indefinitely) is inefficient. The best practice is to assign the Service Territory Member (the resource) a "Shell" Operating Hours record that has zero time slots (No Availability).

You then use Shifts to define the specific working times for specific dates (e.g., "Nov 1st: 9am-2pm").

Because the base Operating Hours are empty, the Scheduling Engine looks only at the Shifts to determine availability. This avoids the conflict of having to "subtract" time from a standard day or constantly update the base record.

Asset replacement and history in Salesforce are tracked using the Asset Relationship object.

Options A and B are correct. The Asset Relationship object links two assets together (e.g., Old Asset - > New Asset) with a relationship type like "Replacement" or "Upgrade." On the Asset page layout, this related list (often labeled "Asset Relationships" or "Related Assets") allows you to see the history in both directions:

Forward: See the new asset that replaced this asset (Option A).

Backward: See the old asset that this asset replaced (Option B).

Options C and D are incorrect. "Primary Assets" is typically a concept associated with Service Contracts (covering the main asset) or Entitlements, not the history of physical swaps/upgrades between asset records.

(Note: The provided PDF source likely contains an error marking D as correct. "Primary Assets" is not the standard location for replacement history.)