AP-209 Exam Dumps : Advanced Field Service Accredited Professional

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

Options A and B are correct.TheAsset Relationshipobject 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 replacedthisasset (Option A).

Backward:See the old asset thatthisasset 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.)

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 addresses the "Shift vs. Operating Hours" architecture.

Option B is correct.When a schedule hasno consistent weekly pattern, using standard Operating Hours (which repeat Mon-Sun indefinitely) is inefficient. The best practice is to assign the Service Territory Member (the resource) a "Shell" Operating Hours record that haszero time slots(No Availability).

You then useShiftsto define the specific working times for specific dates (e.g., "Nov 1st: 9am-2pm").

Because the base Operating Hours are empty, the Scheduling Engine looksonlyat the Shifts to determine availability. This avoids the conflict of having to "subtract" time from a standard day or constantly update the base record.