AP-209 Sample Questions Answers

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.

This requires a balance of data accuracy (tracking the asset) and schedule accuracy (updating the duration).

Option D is correct because it uses Field Service Mobile Flows , which is the best practice for guiding technicians through complex processes.

Data: Creating a Work Order Line Item (WOLI) is the correct data model to track work done on a specific (secondary) Asset under the main Work Order.

Schedule: The flow can update the current Service Appointment's Duration and Scheduled End to reflect the reality that the tech will be there longer.

Automation: Triggering a "Scheduling Recipe" (now typically handled via Flows/Optimization services) ensures that if the appointment runs long, subsequent appointments for the day are automatically shifted (Reshuffled) to prevent overlapping/late arrivals.

Options A and C fail to update the schedule duration, meaning the tech will likely be late to their next job without the dispatcher knowing. Option B creates a second appointment, which is administratively heavy for "just looking at" another asset during the same visit.

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.

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 urgent only when 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' will never beat 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.

Salesforce Field Service schedules Service Resources, not Assets. To bring physical equipment into the scheduling engine, the equipment must be modeled as a Service Resource so the engine can check its availability, capacity, and skills.

Option D is correct. To include cranes, excavators, or any other equipment in scheduling, ACME must create Service Resource records for them (typically with a 'Resource Type' such as 'Equipment'). These records consume Field Service licenses, and once configured they participate in the candidate evaluation, capacity, and optimization just like a human technician.

Option A is incorrect because there is no 'Use for Scheduling' Boolean on the Asset object; Assets and Service Resources are separate concepts.

Option B is incorrect because a lookup field does not make the Asset part of the scheduling engine — it is just a reference.

Option C is incorrect because the Dispatcher Console does not expose an 'Include Assets' toggle on the Schedule action.

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.

Resource Absence is a flexible object that supports custom values, but it has specific behavior on the SFS Mobile App and in the scheduling engine that admins must understand.

Option B is correct. The SFS Mobile App creates Resource Absence records using the default record type. To ensure those absences are honored by Auto-Schedule and Global Optimization, the 'Non-Availability' record type must be the default — otherwise the engine ignores them.

Option D is correct. The standard 'Type' picklist on Resource Absence includes Vacation, Meeting, Training, and Medical out of the box. Admins can add custom values, but these are the seeded options.

Option E is correct. The SFS Mobile App's Profile tab includes an Absences section where Service Resources can view and create their own absences, which feeds directly into the Gantt and the optimizer.

Option A is incorrect because custom Type values do show on the Gantt; absences appear as colored bars on the resource row regardless of the Type value used.

Option C is incorrect because the optimizer considers all Resource Absence records with a Non-Availability record type, regardless of whether the Type value is standard or custom.

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

When a contractor company provides aggregate hours rather than a list of named technicians, the correct model is a Capacity-Based Resource so the engine schedules against capacity in hours, not against a specific individual.

Option A is correct. A Capacity-Based Resource lets you express '20 hours per day' as capacity, assign Operating Hours of 9:00 AM–5:00 PM that match the contractor's agreed window, and add the 'maintenance' skill to restrict the type of work routed to them.

Option B is incorrect because preferring contractors is a soft preference; it does not enforce the contractor's distinct hours or capacity.

Option C is incorrect because creating a separate Service Territory does not, by itself, model contractor capacity or restrict the work type assigned.

Option D is incorrect because a Named Resource represents a single person, not a company providing aggregate hours, and the Designated Work approach does not capture the daily capacity cap.

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.

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"). The Match Boolean Work Rule enforces that if the Appointment is checked, the Resource must also be checked.

Option E is correct (Extended Match): If the requirement is more complex (e.g., matching a specific type or level of badge), the Extended Match Work 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 requirement is to see data "from the Gantt" (the visual chart) with "minimal clicks."

Option D is correct. The Service Tooltip Gantt field set on the Service Appointment object controls the pop-up text box that appears when a dispatcher hovers their mouse over a Service Appointment bar on the Gantt chart. This requires zero clicks and is the fastest way to inspect details like "Description" without opening the full record.

Options A, B, and C refer to the "Appointment List" (the textual list on the left side of the console). While useful, scrolling through long descriptions in a list column is difficult (Option A) and requires looking away from the Gantt chart itself.

Salesforce Field Service uses a chain of objects — Product → Product Item → Product Item Transaction → Product Consumed — to track inventory from stock to consumption. The link between these records is what enables full lifecycle visibility.

Option D is correct. Populating the 'Product Item' on each Product Consumed record creates the link back to the specific stock record (held at a Location for a Service Resource or warehouse). This connection lets Salesforce decrement inventory, generate Product Item Transactions automatically, and trace where the consumed item originated.

Option A is incorrect because Product Item Transactions are generated automatically based on Product Item activity — they are not manually populated on Product Consumed.

Option B is incorrect because Price Book Entry tracks pricing data, not stock. Leaving Product Item blank breaks the inventory chain.

Option C is incorrect because Location is helpful context but is not, by itself, what links Product Consumed to inventory; the Product Item connection is required.

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.

During Scoping (the initial phase), the goal is to align on the "What" and "Why" before moving to the "How."

Option A is correct (Work Parameters): You must define what constitutes a "Job" (Work Order), how long it takes, and what skills are needed. This is the foundation of the data model.

Option C is correct (Terminology): Mapping the customer's language to Salesforce terms (e.g., "We have 'Truck Rolls' - > In Salesforce, that is a 'Service Appointment'") is crucial to avoid confusion throughout the project.

Option D is correct (Project Objectives): Defining what is "Essential" (MVP) vs. "Nice to Have" sets the project boundaries and success metrics.

Option B (Sprint Review) happens during the build phase (Agile methodology), not during initial scoping.

Option E (Solution Design) is the output of the scoping/analysis phase, not a topic you ask about during the initial discovery.

The goal is to fit high-priority work into a schedule already filled with low-priority work.

Option B is correct. The system must know that the Repair jobs are more important than the Maintenance jobs. This is handled by the Scheduling Priority field (used in the optimization logic to decide which job to drop if there is a conflict) or the Priority field mapped to Service Objectives.

Option C is correct. Global Optimization is the best tool here. It will look at the entire week, see the high-priority unscheduled jobs, and the low-priority scheduled jobs. It will then un-schedule or move the maintenance jobs to make room for the urgent repairs.

Option D is correct. For Optimization to work, the existing maintenance appointments must not be Pinned . If they are pinned, the optimizer treats them as immovable rock, and it won't be able to free up the time needed for the repairs.

Option A (Manual assignment) is inefficient and risky (could double-book). Option E (Resource Schedule Optimization) optimizes one person at a time; Global Optimization is better suited for balancing the load across the whole territory.

When Global Optimization leaves appointments unscheduled despite available capacity, the root cause is usually in the optimization configuration (which appointments are eligible) rather than in the Gantt UI state.

Option A is correct. 'Pinned Statuses' under Field Service Settings define which Service Appointment statuses are treated as locked by Global Optimization. If an appointment is in a pinned status, the optimizer will not move or schedule it, which produces exactly the symptom described.

Option C is correct. The lightbox shown when invoking optimization from the Gantt lets the dispatcher choose the Scheduling Policy, time horizon, filters and resources. A misconfigured run from this dialog directly causes appointments to be skipped.

Option D is correct. 'Optimization Insights' on the Optimization Request object surfaces detailed information about which appointments were considered and why some were not scheduled (work rule violations, no eligible resource, etc.). This is the most direct investigative tool available.

Option B is incorrect because list view visibility is a UI concern; Global Optimization picks up appointments based on the scope you select, not based on what is visible to the dispatcher.

Option E is incorrect because the Gantt's active Scheduling Policy is not what controls Global Optimization — the policy is chosen in the run dialog.