Salesforce AP-209 Advanced Field Service Accredited Professional Exam Practice Test

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.TheMatch BooleanWork 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 theJoband theResource(e.g., Skill or Location matching), which is not the same as a blanket exclusion of a resource type.

Service Territory design heavily impacts the performance of the Gantt and Optimization engine.

Option C is correct:Historically, Salesforce recommended keeping Service Territories to around50 Resourcesto ensure the Gantt loads quickly and optimization runs efficiently. (While limits have increased, this remains a safe "rule of thumb" for design).

Option D is correct:Territories are almost alwaysGeographic. This drives the travel time calculations, which are central to the Field Service value proposition.

Option B is correct:This refers to theAppointment Bookingsearch space. If a territory is too massive, the engine has to score thousands of candidates, which is slow. Designing territories/policies so that the engine evaluates a focused set (e.g., ~20 qualified candidates) ensures sub-second response times for booking slots.

Option A (Skill assignments) is about Resources, not Territory structure.

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.

This question asks how to track the history/link between an old asset and a new one.

Option C is correct.TheAsset Relationshipobject is a standard Salesforce object designed specifically to link two assets. It includes fields like Relationship Type (which can be set to "Replacement," "Upgrade," etc.) and From Date/To Date. This creates a clear lineage: Asset A was replaced by Asset B.

Option A (Child Asset) implies a hierarchy (one ispartof the other), not a replacement.

Option D (Maintenance Asset) is used for Maintenance Plans (PMs), not for tracking swap/upgrade history.

The goal is to prevent low-priority "Inspections" from being ignored indefinitely until they miss their deadline, without permanently ranking them above high-value "New Installs."

Option B is correct(based on the scenario's specific constraints). By using automation to elevate the Inspection's priority to '1' (High) only when it is due "tomorrow," the system treats it as urgentonlywhen necessary to avoid the penalty. Since "New Installs" are also Priority '1', the two will compete on equal footing on that final day, ensuring the Inspection has a fighting chance to be scheduled alongside high-value work.

Option C (Dynamic Priority) is a standard solution for "aging" work. However, the option states it caps the value at '2'. In standard SFS priority (where 1 is highest), a '2' willneverbeat a '1'. Therefore, the inspection would still likely be bumped by a New Install (Priority 1) even on its due date, leading to a penalty.

Option D ("Schedule Over Lower Priority") is used for emergency reshuffling, but does not inherently solve the prioritization logic between these two specific task types.

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.

This question tests the Maintenance Plan generation logic.

Option D is correct.The requirement isSingle Visit(One Appointment) forMultiple Assets.

One Work Order Line Item per Asset:This groups all the assets under asingleparent Work Order. Each asset gets its own line item (WOLI) for tracking purposes.

One Service Appointment per Work Order:This creates asingleappointment for the parent Work Order. The technician arrives once and works through the list of line items (Assets).

Option B("One Work Order per Asset") would create separate Work Orders (and likely separate Appointments) for every single asset, resulting in multiple visits or a cluttered schedule.

Option C("One SA per WOLI") would explicitly create a separate appointment for every single asset line item, causing massive double-booking/overlap.

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 supportsMulti-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 Dis incorrect because the app specifically allows for theconsumptionof parts while offline; the transactions sync back to the server once connectivity is restored.

This question addresses the trade-off between Customer Experience and Schedule Optimization.

Reducing the arrival window (e.g., from 4 hours to 2 hours) is a common strategy to improve customer service. Customers prefer shorter wait times and more precise appointments. However, a consultant must identify the technical impact of this business decision.

Option B is correctbecause it acknowledges the benefit (customer experience) while correctly identifying the risk. Smaller arrival windows serve as tighter constraints on the scheduling engine (Optimization). The engine has less "wiggle room" to shuffle appointments, which can lead to lower overall utilization or higher travel times.

Option C is incorrect because reducing the windowdecreases(restricts) flexibility for optimization, it does not increase it.

Options A and D suggest increasing the window to 8 hours. While this is great for the optimization engine (maximum flexibility), it is generally considered a poor customer experience to ask a prospect to wait all day (8 hours), contradicting the business goal of being "more competitive."

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 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 multipleField Service Mobile Settingsrecords. You assign these settings records to specificUser 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).

This scenario describes a structured process with validation (Checklist + Data + Images).

Option A is correct.Work Plansare the standard, modern feature for checklists in Salesforce Field Service. A Work Plan consists of "Work Steps." These steps can be linked to aFlow, which provides a user-friendly wizard to capture specific data inputs and upload images in a structured way.

Option Bis the legacy method. Adding fields directly to the Service Appointment creates clutter and doesn't offer a step-by-step "Checklist" experience.

Option Cis a security risk (too much access) and provides no process guidance.

Option D(Deep Linking) is used to jumpoutof the app to another app, which is not needed here since SFS can handle flows natively.

During the "Day 1" or Scoping phase of an implementation, the goal is to define the high-level architecture and business model.

A is correct:DefiningIntegrationpoints (ERP, HR, Inventory) is a foundational requirement that dictates the project scope and data strategy.

D is correct:Defining theWork(Work Types, Skills, Durations) is the core of the Field Service data model. You cannot configure the system without knowing what services are being performed.

E is correct:Defining theTerritory Structure(Business Units) sets up the security model, sharing settings, and resource organization.

Options B and Care incorrect for thefirst daybecause they are detailed configuration specifics (Refinement). You cannot define "Service Objective Weights" or "Gantt Features" until you understand the basic business goals, services, and territories.