AP-209 Advanced Field Service Accredited Professional Questions and Answers

To filter resources based on strict criteria (like security clearance), you use Work Rules (Hard Constraints).

Option B is correct (Match Boolean):This is a simple, effective method for binary requirements. You place a checkbox on the Service Appointment (e.g., "Requires Security Badge") and a corresponding checkbox on the Service Resource (e.g., "Has Security Badge"). TheMatch BooleanWork Rule enforces that if the Appointment is checked, the Resourcemustalso be checked.

Option E is correct (Extended Match):If the requirement is more complex (e.g., matching a specifictypeorlevelof badge), theExtended MatchWork Rule is best. It allows you to match a field on the Service Appointment (or Work Order) to a related list or field on the Service Resource. For example, matching the "Badge Type" required by the Government Account to the "Badge Type" held by the Resource.

Note: While Skills (Option C) are also commonly used for this, the question specifically points toward Work Rule configurations (Boolean/Extended) often used for strict compliance attributes.

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 theDispatcher Consolelayout in the same way the primary transactional objects do.

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 travelfromHometothe 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 theService Center, the optimization engine assumes the technician isat the Service Centerat 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.

To tier resources generally (not per customer), you use the Resource Priority Service Objective.

Option C is correct.TheResource Priorityobjective works on a scoring scale where aHigher Valueindicates aHigher Priority. The optimization engine attempts to assign the appointment to the resource that yields the highest overall schedule score.

By assigning Full-Time = 10, Contractors = 9, and Part-Time = 8, the engine will "score" the Full-Time option highest, followed by the Contractor.

Option Duses the inverse logic (1, 2, 3). If deployed, the engine would favor the Part-Time employees (Score 3) over the Full-Time employees (Score 1), which is the opposite of the requirement.

Options A and Brefer toPreferred Resource, which is typically defined on theAccountorWork Orderlevel (e.g., "Bob is preferred for Customer X"). It is not efficient for ranking entiregroupsof employees globally.

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 configureCustom Notificationsfor 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'ANDthe 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 warndispatchersabout impending SLA violations, not to notify technicians of new work.

The requirement is to schedule two distinct resources (a Human and a Vehicle) for the same job at the same time.

Option C is correct.

Vehicle as Service Resource:You must model the vehicle as a Service Resource (Type: Asset) to track its availability on the Gantt and prevent double-booking.

Complex Work (Same Start):To ensure the vehicle and the technician are booked together, you use Complex Work dependencies. "Same Start" ensures that the vehicle appointment and the technician appointment are scheduled to begin simultaneously.

Options A and Dare incorrect becauseProductsare not scheduled. Consuming a product does not check if the vehicle is available at that specific time, potentially leading to double-booking the van.

Option Bis incorrect because "Immediately Follow" implies a sequence (Technician finishes -> Vehicle starts), which is not how a shared ride/equipment scenario works.

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

Option A is correct:You must ensure yourScheduling Policyincludes theActive ResourcesWork Rule8. 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 specificjob-by-jobexclusions (e.g., "Don't send Bob to this specific customer"), not for global termination.

The key here is that it is a Third-Party Contractor and a Temporary engagement.

Option C is correct.

Capacity Based:Contractors are typically modeled as "Capacity Based Resources" (buckets of work) rather than named individuals, as you usually don't track their specific travel or breaks—you just know they can take "X hours of work per day."

Giving Capacity:You would define the capacityonlyfor the specific 3-week period. Once the capacity records end, the scheduling engine will naturally stop assigning work to them.

Options B and D (Deleting):It is never a best practice to delete a Service Resource record after use. You need the record to remain in the system to preserve theAudit Trailand historical data of the Work Orders they completed. You simply deactivate them or stop giving them capacity.

To model international workforces in Salesforce Field Service, specific objects handle geography, time, and exceptions.

Option B is correct.

Service Territories:Used to define the geographical areas (Countries/Regions). Crucially, theTime Zoneis defined on the Service Territory record.

Operating Hours:Used to define the "Permitted Working Hours" (e.g., Mon-Fri, 9-5). These are assigned to the Service Territory or Service Territory Member.

Resource Absences:Used to model time off, such as public holidays or sick days, where the resource is unavailable. (Note: Holidays can also be linked directly to Operating Hours, but Resource Absences are the distinct records created on the Gantt).

Option A is incorrect because "Business Hours" is a Service Cloud (Support) object used for Case Entitlements, not Field Service scheduling. "Resource Capacity" is used for contractors (Capacity-Based Scheduling), not for defining standard working hours.

This issue arises because Salesforce Field Service calculates availability by combining Operating Hours AND Shifts. If a user has Operating Hours of 9-5, they are fundamentally "Available" during that time. A Shift is typically used to add or extend availability (or define it if using specific settings), but standard Operating Hours often take precedence as the "Base."

Option A is correct.To have a resource's availability definedexclusivelyby variable Shifts, the best practice is to assign them a "Shell" or "Empty" Operating Hours record (one with zero time slots defined). With no base hours, the system looksonlyto the Shifts to determine when the resource is working. This ensures that if a Shift ends at 4 PM, the resource is truly unavailable at 5 PM.

Option B is administratively impossible (you cannot automate changing the STM Operating Hours record lookup daily without complex custom code, and it's not a standard practice).