Question

Difficulty: MediumObject Relationships (Lookup, Master-Detail, Many-to-Many)

A company uses a custom object named Course_Feedback__c to track feedback provided by employees for training courses managed in a custom object named Training_Course__c. Management has specified two key operational requirements:
1. If a Training_Course__c record is deleted, all associated Course_Feedback__c records must be automatically removed from the system.
2. Administrators must display the total count of feedback submissions directly on the Training_Course__c detail page using standard declarative functionality.

Which two configuration steps should the Salesforce Administrator perform to satisfy these requirements? (Select 2 answers)

  1. Create a Master-Detail relationship field on the Course_Feedback__c object that references the Training_Course__c object.Answer
  2. Create a Roll-Up Summary field on the Training_Course__c object to aggregate the total count of related Course_Feedback__c records.Answer
  3. C
    Create a Lookup relationship field on the Course_Feedback__c object and configure a Roll-Up Summary field on the Training_Course__c object.
  4. D
    Create a Lookup relationship field on the Course_Feedback__c object with the 'Clear the value of this field' deletion option selected.

Answer

The administrator must create a Master-Detail relationship field on Course_Feedback__c pointing to Training_Course__c, and create a Roll-Up Summary field on Training_Course__c using the COUNT function.
To satisfy both requirements natively in Salesforce without code, a Master-Detail relationship must be established on the detail object (Course_Feedback__c). This automatically enforces cascading deletion of feedback records whenever a training course is deleted. Additionally, establishing a Master-Detail relationship enables the creation of a standard Roll-Up Summary field on the master object (Training_Course__c) to count related feedback records.

Step-by-Step Solution

1
Analyze the deletion requirement
Automatic deletion of child records when a parent record is deleted requires a Master-Detail relationship rather than a Lookup relationship.
Master-Detail relationships natively support cascade deletion where deleting the master record automatically deletes all associated detail records.
2
Analyze the roll-up count requirement
A native Roll-Up Summary field must be created on the master object (Training_Course__c).
Declarative Roll-Up Summary fields are exclusively available on the master side of a Master-Detail relationship.
3
Select the correct implementation steps
Define the Master-Detail relationship field on Course_Feedback__c and add the Roll-Up Summary field to Training_Course__c.
Custom relationship fields are defined on the child object referencing the parent, while Roll-Up Summary fields are created on the master parent object.

Key Concept

Master-Detail Relationship Capabilities and Roll-Up Summary Field Requirements
Rate this question