Question

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

An administrator is configuring a custom object named Event_Registration__c to link with the standard Contact object. The business requirement states that if a Contact record is deleted, all associated Event_Registration__c records must be deleted automatically. Additionally, executive leadership requires displaying the total number of event registrations directly on the Contact record. Which two configuration settings or relationship choices satisfy these requirements? (Choose 2 answers)

  1. Create a Master-Detail relationship field on Event_Registration__c pointing to Contact.Answer
  2. Create a Roll-Up Summary field on the Contact object to count related Event_Registration__c records.Answer
  3. C
    Create a Lookup relationship field on Contact pointing to Event_Registration__c with cascade delete enabled.
  4. D
    Create a Roll-Up Summary field on the Event_Registration__c object to aggregate data from Contact.

Answer

Create a Master-Detail relationship field on the Event_Registration__c object pointing to Contact, and create a Roll-Up Summary field on the Contact object to calculate the total count of child records.
Defining a Master-Detail relationship on the child object (Event_Registration__c) linking to Contact ensures that deleting a Contact record cascades deletion to all associated registration records. Furthermore, establishing a Master-Detail relationship allows the creation of a native Roll-Up Summary field on the parent Contact object to count related registrations.

Step-by-Step Solution

1
Identify the deletion cascade requirement.
Determine that a Master-Detail relationship must be created on the detail object (Event_Registration__c) referencing Contact so that deleting a Contact record automatically deletes its related registrations.
Master-Detail relationships inherently control deletion cascade behavior.
2
Identify the metric aggregation requirement.
Determine that a Roll-Up Summary field must be placed on the parent/master object (Contact) to count related detail records.
Roll-Up Summary fields are natively supported on master objects in Master-Detail relationships.

Key Concept

Master-Detail Relationship and Roll-Up Summary Fields
Estimated Time:1m 0s
Rate this question