An administrator at a healthcare non-profit needs to track patient satisfaction surveys using a new custom object named Patient_Feedback__c. The business team requires that aggregate score totals from all feedback records display directly on the parent Account record using a declarative roll-up summary field. Additionally, if an Account is deleted, all associated Patient_Feedback__c records must automatically be removed. Which relationship configuration on the custom object satisfies these requirements?
- Create a Master-Detail relationship field on the Patient_Feedback__c custom object referencing the Account standard object.Answer
- BCreate a Lookup relationship field on the Patient_Feedback__c custom object referencing Account, and configure a roll-up summary field on Account.
- CCreate a Lookup relationship field on the Account standard object referencing Patient_Feedback__c and select the cascade delete option.
- DCreate a Master-Detail relationship field on the Account standard object referencing the Patient_Feedback__c custom object.
Answer
Create a Master-Detail relationship field on the Patient_Feedback__c custom object referencing the Account standard object.
Creating a Master-Detail relationship field on Patient_Feedback__c referencing Account satisfies both business requirements. In a Master-Detail relationship, the master record (Account) controls detail record behavior, enabling automatic cascade deletion of child records when the master is deleted, and allowing standard Roll-Up Summary fields to be created on Account.
Step-by-Step Solution
Key Concept
Master-Detail Relationship Capabilities and Setup