Salesforce Updated AP-209 Exam Questions and Answers by kiyaan

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.

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.

This is the standard troubleshooting procedure for "Why wasn't this scheduled?".

Option A is correct. If there is white space, but the optimizer didn't use it, there is likely a Rule Violation (Hard Constraint) preventing it (e.g., The resource is missing a Skill, the Territory doesn't match, or the Travel Time is too long). Manually dragging the appointment to that specific spot on the Gantt triggers the rule validation logic, and the console will pop up a "Rule Violation" message telling you exactly which rule failed (e.g., "Match Skills Rule Violation").

Option B helps find valid slots, but it doesn't explain why the current white space is invalid.

Option C addresses scoring (Objectives), not hard constraints (Rules). If there was space, the objectives would just give it a low score, not prevent scheduling entirely (unless the score was 0, but Rule Violations are the more common culprit for unscheduled work).

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