Question 1
Choose 1
Universal Containers (UC) wants to track the Asset lifecycle whenEquipment has been swapped out.
What should a Consultant recommend to meet this requirement?
What should a Consultant recommend to meet this requirement?
Correct answer:
A. Add the Related Asset related list to the Asset Page and configure the Asset Relationship object.
Explanation:
To track the Asset lifecycle when equipment is swapped out, the Consultant should use the Related Assets related list on the Asset page and configure the Asset Relationship object. The Asset Relationship object is specifically designed to record non-hierarchical, peer-level relationships between assets, such as replacements or swaps. This creates a lasting record showing which asset replaced which other asset, preserving the equipment change history even after statuses change.
Correct Option:
A. Add the Related Asset related list to the Asset Page and configure the Asset Relationship object.:
This is correct because the Related Assets related list displays Asset Relationship records that track replacement history. When an old asset is swapped for a new one, an Asset Relationship record links them, with the old asset showing the new one in its Primary Assets list and the new asset showing the old one in its Related Assets list. This directly satisfies the requirement to track asset lifecycle during equipment swaps.
Incorrect Option:
B. Add the field history tracking related list to the Asset Page and configure the Product Request object.:
This is incorrect because field history tracking only records changes to individual field values over time; it does not create linked records between old and new assets. Product Requests track parts being requested, transferred, or returned for service appointments, not asset-to-asset replacement relationships.
C. Add the Related Asset related list to the Asset Page and configure the Product Request object.:
This is incorrect because while the Related Assets list is correct, Product Requests do not track asset swaps. Product Requests are for inventory movements (transferring parts, requesting stock), not for recording that one asset replaced another.
D. Add the field history tracking related list to the Asset Page and configure the Asset Relationship object.:
This is incorrect because field history tracking does not create the peer-to-peer asset replacement records needed for lifecycle tracking. While Asset Relationship is the correct object, the Related Assets related list—not field history—is what displays those relationships on the Asset page.
Reference:
Salesforce documentation: Asset Relationship represents "a non-hierarchical relationship between assets caused by an asset modification, for example a replacement, an upgrade, or another circumstance." The Related Assets list shows assets that the current asset replaced, while Primary Assets shows assets that replaced the current asset.
To track the Asset lifecycle when equipment is swapped out, the Consultant should use the Related Assets related list on the Asset page and configure the Asset Relationship object. The Asset Relationship object is specifically designed to record non-hierarchical, peer-level relationships between assets, such as replacements or swaps. This creates a lasting record showing which asset replaced which other asset, preserving the equipment change history even after statuses change.
Correct Option:
A. Add the Related Asset related list to the Asset Page and configure the Asset Relationship object.:
This is correct because the Related Assets related list displays Asset Relationship records that track replacement history. When an old asset is swapped for a new one, an Asset Relationship record links them, with the old asset showing the new one in its Primary Assets list and the new asset showing the old one in its Related Assets list. This directly satisfies the requirement to track asset lifecycle during equipment swaps.
Incorrect Option:
B. Add the field history tracking related list to the Asset Page and configure the Product Request object.:
This is incorrect because field history tracking only records changes to individual field values over time; it does not create linked records between old and new assets. Product Requests track parts being requested, transferred, or returned for service appointments, not asset-to-asset replacement relationships.
C. Add the Related Asset related list to the Asset Page and configure the Product Request object.:
This is incorrect because while the Related Assets list is correct, Product Requests do not track asset swaps. Product Requests are for inventory movements (transferring parts, requesting stock), not for recording that one asset replaced another.
D. Add the field history tracking related list to the Asset Page and configure the Asset Relationship object.:
This is incorrect because field history tracking does not create the peer-to-peer asset replacement records needed for lifecycle tracking. While Asset Relationship is the correct object, the Related Assets related list—not field history—is what displays those relationships on the Asset page.
Reference:
Salesforce documentation: Asset Relationship represents "a non-hierarchical relationship between assets caused by an asset modification, for example a replacement, an upgrade, or another circumstance." The Related Assets list shows assets that the current asset replaced, while Primary Assets shows assets that replaced the current asset.