AP-209 Exam Dumps - Salesforce Accredited Professional Certification Questions and Answers

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).

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.

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 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.

The requirement is specifically to free up white space on the Gantt when a tech finishes early.

Option D is correct. The Gantt chart visual blocks are drawn based on Scheduled Start and Scheduled End. If a tech finishes a 2-hour job in 30 minutes, the Gantt bar will remain 2 hours long unless the Scheduled End is updated. By using a Mobile Flow to update both the Actuals (for reporting) and the Scheduled (for the Gantt), the bar shrinks, revealing 1.5 hours of open availability for the dispatcher to utilize.

Option C is the "Purist" data view (don't change scheduled), but it fails the specific business requirement of allowing new work to be added immediately.

Option A suggests creating custom fields for the original times, which is a valid part of the solution (to keep a history), but Option D describes the core functional mechanism (Flow updating the standard fields) required to achieve the Gantt behavior. The "Offline" warning in A is true but D is the more direct configuration answer.

The Field Service Mobile Settings configuration controls the behavior of the mobile app (branding, location tracking, flows, etc.).

Option D is correct. To apply different settings to different groups of users, you must create multiple Field Service Mobile Settings records. You assign these settings records to specific User Profiles .

You would create one settings record with "Collect Service Resource Geolocation History" enabled (for the tracked users).

You would create a second settings record with it disabled (for the untracked users).

You then map the relevant Profiles to the appropriate Settings record.

Options A, B, and C imply global settings or non-existent tabs ("Mobile App Configuration" tab where you select users/profiles directly doesn't exist in the global settings in this manner; it is done via the specific Mobile Settings object assignments).

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.

To stop a resource from receiving work, you must mark them as inactive and ensure the scheduling engine respects that status.

Option C is correct: Deactivating the Service Resource (unchecking the "Active" checkbox on the record) is the standard way to "fire" or terminate a resource. It preserves history but flags them as no longer working 7 .

Option A is correct: You must ensure your Scheduling Policy includes the Active Resources Work Rule 8 . This rule explicitly tells the optimization engine: "Do not assign appointments to any resource where Active = False." Without this rule, the engine might still technically assign work to an inactive record if no other constraints block it.

Option B (Delete) is bad practice (data loss).

Option D (Excluded Resources) is for specific job-by-job exclusions (e.g., "Don't send Bob to this specific customer"), not for global termination.

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.

To exclude a specific subset of resources from being scheduled by the optimization engine, you use a Hard Constraint Work Rule.

Option D is correct. The Match Boolean Work Rule is designed to filter resources based on a checkbox (Boolean) field.

You would create a custom checkbox on the Service Resource object (e.g., Is_Contractor__c).

You configure the Match Boolean rule in the Scheduling Policy to enforce that Is_Contractor__c must be False.

When optimization runs, any resource where Is_Contractor__c = True fails the rule and is completely ignored/excluded from the schedule calculation.

Option A (Count Rule) limits volume, it doesn't exclude.

Options B and C (Match Field/Extended Match) match properties between the Job and the Resource (e.g., Skill or Location matching), which is not the same as a blanket exclusion of a resource type.