An administrator at a clinical research organization is designing a custom object named Subject_Visit__c to track patient evaluation sessions associated with a parent custom object named Clinical_Trial__c. The business requires that deleting a Clinical_Trial__c record automatically removes all associated Subject_Visit__c records, and that total completed visits must be displayed as an aggregate count on the Clinical_Trial__c record. Which two configuration considerations and object capabilities apply to this implementation? (Select 2)
- A Master-Detail relationship must be created on Subject_Visit__c pointing to Clinical_Trial__c to enable native Roll-Up Summary fields on the parent object.Answer
- Standard system audit fields such as CreatedById, LastModifiedDate, and Name are automatically created when the Subject_Visit__c custom object is defined.Answer
- CA Lookup relationship can be used to link Subject_Visit__c to Clinical_Trial__c while still supporting native Roll-Up Summary fields on Clinical_Trial__c.
- DConfiguring a Lookup relationship with 'Clear the value of this field' will automatically cascade delete all child Subject_Visit__c records when the parent trial is deleted.
Answer
The correct selections are that a Master-Detail relationship must be created on Subject_Visit__c pointing to Clinical_Trial__c to enable native Roll-Up Summary fields, and that standard audit fields (such as CreatedById, LastModifiedDate, and Name) are automatically created when defining a custom object.
Master-Detail relationships inherently support native Roll-Up Summary fields on the parent master object and automatically enforce cascading deletion of child records when the master record is deleted. Additionally, whenever a new custom object is created in Salesforce, standard system fields (such as Name, CreatedById, LastModifiedDate, and CreatedDate) are automatically provisioned by the platform.
Step-by-Step Solution
Key Concept
Standard vs Custom Object Capabilities and Master-Detail Relationship Characteristics