FS-Con-101 practice question 4 of 10

Universal Containers (UC) wants to track the Asset lifecycle when equipment has been swapped out. What should a Consultant recommend to meet thisrequirement?

Full set: 163 questions
Answer options
A: Add the field history tracking related list to the Asset Page and configure the Product Request object,
B: Add the Related Asset related list to the Asset Page and configure the Product Request object
C: Add the Related Asset related list to the Asset Page and configure the Asset Relationship object. Correct answer
D: Add the field history tracking related list to the Asset Page and configure the Asset Relationship object.
Correct Answer:
C. Add the Related Asset related list to the Asset Page and configure the Asset Relationship object.
Explanation

To track an asset swap, a relationship must be established between the original asset and its replacement. The standard Salesforce Field Service object for this purpose is the AssetRelationship. A consultant should configure this object by defining appropriate RelationshipType picklist values (e.g., "Replaced By," "Replacement For"). To make this relationship visible to users on the asset's record page, the "Related Asset" related list must be added to the Asset page layout. This combination directly addresses the requirement to track the asset's lifecycle concerning swaps by linking the distinct asset records involved.

Why Incorrect

A. Field history tracking shows changes to a single asset's fields, but it cannot create or display a link between two separate asset records, which is essential for a swap.
B. While the "Related Asset" related list is correct, the Product Request object is used for inventory management (requesting parts for a job), not for defining the relationship between the old and new assets.
D. Field history tracking is insufficient for tracking a relationship between two different assets. The core of the solution is the relationship object and its visibility on the page layout. ---

References

1. Salesforce Help Documentation: Track Relationships Between Assets

Content: This official guide explicitly states, "Create asset relationships to track how assets are related to each other. For example, if a part of your customer’s boiler is replaced, you can create a relationship between the original boiler asset and the new part asset." It also instructs administrators to add the "Related Assets" related list to asset page layouts to view these relationships.

Reference: Salesforce Help, Article Number 000337189, "Track Relationships Between Assets."

2. Salesforce Field Service Developer Guide: AssetRelationship

Content: The developer guide defines the AssetRelationship object as the junction object that "Represents the relationship between two assets." It contains key fields like AssetId, RelatedAssetId, and RelationshipType, which are fundamental to configuring and establishing the link between a swapped-out asset and its replacement.

Reference: Salesforce Field Service Developer Guide, Object Reference for Salesforce and Lightning Platform, "AssetRelationship."

3. Salesforce Help Documentation: Field History Tracking

Content: This documentation explains that Field History Tracking retains a history of changes to the values in specific fields on a record. It does not describe any capability to link one record to another, confirming why options A and D are incorrect for tracking a swap relationship.

Reference: Salesforce Help, Article Number 000329434, "Field History Tracking."

Scroll to Top