Free Salesforce AP-209 Exam Dumps July 2026

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.

When dealing with a Bring Your Own Device (BYOD) strategy (common with contractors), device compatibility is the biggest technical hurdle.

Option B is correct. Salesforce explicitly publishes a list of supported devices and operating systems (iOS and Android versions)6. Since the company does not own the phones, they cannot guarantee every contractor has a compatible device. The consultant must warn the client to check these specs against their contractors' hardware.

Option A is a policy decision, not a technical constraint. You can track contractor location if they agree to it.

Option C is false; Contractor licenses (Community Plus) do include access to the Field Service Mobile App.

Asset replacement and history in Salesforce are tracked using the Asset Relationship object.

Options A and B are correct. The Asset Relationship object links two assets together (e.g., Old Asset -> New Asset) with a relationship type like 'Replacement' or 'Upgrade.' On the Asset page layout, this related list (often labeled 'Asset Relationships' or 'Related Assets') allows you to see the history in both directions:

Forward: See the new asset that replaced this asset (Option A).

Backward: See the old asset that this asset replaced (Option B).

Options C and D are incorrect. 'Primary Assets' is typically a concept associated with Service Contracts (covering the main asset) or Entitlements, not the history of physical swaps/upgrades between asset records.

(Note: The provided PDF source likely contains an error marking D as correct. 'Primary Assets' is not the standard location for replacement history.)

When running optimization (Global or In-Day), the engine is allowed to move any appointment that is not 'Pinned.'

Option C is correct. In Salesforce Field Service, you must explicitly define which statuses are considered Pinned (immovable) during optimization. This is configured in Field Service Settings > Optimization > Logic. If the 'In Progress' status is not selected in the 'Pinned Statuses' list, the optimization engine sees that appointment as movable. To improve the schedule, it might unassign the current tech and assign a different one, even though the tech is already on-site.

Ensuring 'In Progress' is 'excluded from optimization logic' (Pinned) forces the engine to schedule around that appointment rather than moving it.

Option B refers to 'Status Transitions,' which controls the lifecycle flow (e.g., New -> Scheduled -> In Progress) but does not control the scheduling engine's permission to move the job.

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.

This question addresses the limits of Skills (Work Rules) vs. Extended Match (Custom Criteria).

Option B is correct. This offers the most efficient hybrid approach9.

Skills: Use standard Skills for the 'Service Type' (e.g., 'Repair,' 'Install'). This is simple and low-volume.

Extended Match: Use the Extended Match Work Rule to handle the 'Product' matching. Instead of creating thousands of skills (e.g., 'Repair-ModelX,' 'Repair-ModelY'), you create a custom object or field logic that matches the Asset's Product to a list of Products Supported on the Resource's record. Extended Match is designed exactly for this 'Pattern Matching' without polluting the Skills table.

Option C is incorrect because creating a unique skill for every combination (100+ per resource) leads to 'Skill Explosion.' This bloats the data model and degrades optimization performance10.