A national nonprofit organization is using Salesforce to recruit members. The recruitment process requires a member to be matched with a volunteer opportunity. Given the following: 1. A record is created in Project__ c and used to track the project through completion. 2. The member may then start volunteering and is required to track their volunteer hours, which is stored in VTOTime_c object related to the project. 3. Ability to view or edit the VTOTime__c object needs to be the same as the Project__ c record. 4. Managers must see total hours volunteered while viewing the Project__ c record. Which data relationship should the data architect use to support this requirement when creating the custom VTOTime__c object?
A.
Lookup Field on Project_c to VTOTime_c displaying a list of VTOTime__c in a related list.
B.
Lookup field on VTOTime_c to Project_c with formula filed on Project__ c showing Sum of hours from VTOTime__c records.
C.
Master Detail Field on VTOTime_ c to Project_c with rollup summary field on Project __c showing sum of hours from VTOTime_c records.
D.
Master Detail field on Project _c to VTOTime _c showing a list of VTOTime_c Records in a related list.
C.
Master Detail Field on VTOTime_ c to Project_c with rollup summary field on Project __c showing sum of hours from VTOTime_c records.
Explanation:
Master-detail relationships ensure strong data integrity and controlled data sharing. This structure automatically inherits permissions from parent to child (requirement 3), ensures visibility alignment, and enables roll-up summary calculations. A roll-up summary on Project__c efficiently aggregates total volunteer hours, fulfilling requirement 4. Lookups (options A and B) lack inherent permission inheritance and native roll-up capabilities. Master-detail relationships offer a clear, structured, and highly maintainable approach, ideal for hierarchical and summary-reporting scenarios precisely like this one.