AP-209 Exam Questions & Answers

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

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.

This issue arises because Salesforce Field Service calculates availability by combining Operating Hours AND Shifts. If a user has Operating Hours of 9-5, they are fundamentally 'Available' during that time. A Shift is typically used to add or extend availability (or define it if using specific settings), but standard Operating Hours often take precedence as the 'Base.'

Option A is correct. To have a resource's availability defined exclusively by variable Shifts, the best practice is to assign them a 'Shell' or 'Empty' Operating Hours record (one with zero time slots defined). With no base hours, the system looks only to the Shifts to determine when the resource is working. This ensures that if a Shift ends at 4 PM, the resource is truly unavailable at 5 PM.

Option B is administratively impossible (you cannot automate changing the STM Operating Hours record lookup daily without complex custom code, and it's not a standard practice).

Change management is one of the biggest risks on any Field Service implementation. When end-users are openly resistant, the consultant must adjust scope and approach rather than push more technology on top of the unrest.

Option C is correct. Investing in training reduces fear of the unknown and gives users confidence with the new tool. Phasing the rollout to a single Business Unit or Service Territory limits blast radius, lets the team build success stories, and turns early adopters into advocates for the broader rollout. This is a textbook change-management response.

Option A is incorrect because adding more new functionality (the Mobile App) to a team that is already overwhelmed will increase resistance, not reduce it.

Option B is incorrect because outsourcing the work does not address the user adoption problem and may further demoralize the existing staff.

Option D is incorrect because adding more automation does not solve cultural resistance; users need to understand and trust the system before automation will be embraced.

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.