An administrator is designing a custom data model to track logistics operations between a parent custom object, Shipment_Route__c, and a child custom object, Delivery_Hub__c. The business requires aggregate reporting of completed hubs directly on the route record and demands that deleting a shipment route automatically purges all connected hubs. However, several existing Delivery_Hub__c records currently lack an assigned parent.
Which two steps must the administrator take to establish this data model successfully? (Choose 2 answers)
- Populate the parent reference field on all existing Delivery_Hub__c records before converting the relationship field to a Master-Detail type.Answer
- Create a Roll-Up Summary field on the Shipment_Route__c object to aggregate metrics from related Delivery_Hub__c records.Answer
- CCreate a Roll-Up Summary field directly on the parent Shipment_Route__c object while maintaining a standard Lookup relationship.
- DMaintain the relationship as a Lookup and configure a deletion trigger, because detail records are retained independently when a Master-Detail parent is deleted.
Answer
The administrator must populate the parent reference on all existing child records prior to converting the relationship to Master-Detail, and create a Roll-Up Summary field on the parent object.
Establishing a Master-Detail relationship satisfies the cascading deletion requirement and enables Roll-Up Summary fields on the parent object. Because existing child records lack parent references, those fields must be populated on every record before converting a lookup relationship to Master-Detail.
Step-by-Step Solution
Key Concept
Master-Detail Relationship Conversion Requirements and Roll-Up Summary Field Capabilities
Estimated Time:2m 0s