Salesforce AP-209 - Advanced Field Service Accredited Professional

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

Option C is correct: Historically, Salesforce recommended keeping Service Territories to around 50 Resources to 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 always Geographic . This drives the travel time calculations, which are central to the Field Service value proposition.

Option B is correct: This refers to the Appointment Booking search 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.

Service Crews are the Field Service feature designed for situations in which two or more resources must work together on the same Service Appointment, with one assignment representing the whole crew.

Option A is correct. Modeling the senior and junior as members of a Crew, and assigning the Service Appointment to the Service Crew Resource, ensures they show up together for the same job and the same time slot. The crew composition can be updated as the junior gains experience.

Option B is incorrect because two separate Service Appointments do not guarantee that both resources arrive at the same time on the same site, and they double-count the work for reporting.

Options C and D are incorrect because Multi Stage Work is intended for sequential or simultaneous jobs that produce different outputs — not for two resources performing the same activity together. Crews are the supported pattern for joint-execution work.

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

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

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

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

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

Salesforce Knowledge can be related directly to the Work Order object so that articles surface alongside the job a technician is performing, both on desktop and in the Field Service Mobile App.

Option C is correct. 'Knowledge on Work Orders' allows the admin to attach Knowledge Articles to Work Orders and Work Types. Technicians can read step-by-step procedures, troubleshooting guides, and reference material directly from the related Work Order on the Field Service Mobile App, which is exactly the experience needed in the field.

Option A is incorrect because Custom Links typically open external URLs and require connectivity. They do not provide a managed library of articles.

Option B is incorrect because Knowledge on Cases is a Service Cloud feature for case handling, not for field technicians who work from Work Orders.

Option D is incorrect because Attachments on Cases are unmanaged files associated with Cases, not curated, searchable content for technicians.

Priming is the process of caching data on the device so that the technician can work offline. Priming has limits, can be tuned, and must be combined with scoped list views to keep the device fast and accurate.

Option B is correct. Not every object and record is primed by default. The implementation team must map out which related records (Account, Contact, Asset, Knowledge, etc.) need to be available offline and configure priming or briefcase rules accordingly.

Option D is correct. A very low Schedule Update Frequency Time forces the device to sync constantly, draining battery and consuming bandwidth even when the technician is offline or on a poor connection. The frequency must be tuned to balance freshness against device and network impact.

Option E is correct. Scoping list views to the technician's own appointments (e.g., the next 7 days, my assignments) keeps the offline data set small and relevant, which improves performance and reduces sync time.

Option A is incorrect because the SFS Mobile App syncs automatically when connectivity is restored; the technician does not need to manually trigger a Data Sync.

Option C is incorrect because Product and Pricebook access offline is governed by priming and inventory configuration, not by whether the technician has reviewed them on the desktop.

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.

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

Option C is correct. The Resource Priority objective works on a scoring scale where a Higher Value indicates a Higher 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 D uses 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 B refer to Preferred Resource , which is typically defined on the Account or Work Order level (e.g., "Bob is preferred for Customer X"). It is not efficient for ranking entire groups of employees globally.

This question tests the Maintenance Plan generation logic.

Option D is correct. The requirement is Single Visit (One Appointment) for Multiple Assets .

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

One Service Appointment per Work Order: This creates a single appointment 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.

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 D are incorrect because Products are 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 B is incorrect because "Immediately Follow" implies a sequence (Technician finishes - > Vehicle starts), which is not how a shared ride/equipment scenario works.