An administrator at a global media distribution company needs to create a custom data model to link Media Content (Media_Content__c) records with Distribution Territory (Distribution_Territory__c) records. Each media content item can be released in multiple territories, and each territory can host multiple content items. The requirements specify that deleting a media content item or a territory record must automatically delete its corresponding relationship records. Additionally, executives want to view a real-time total count of associated territories directly on each Media Content record. Which two configuration steps should the administrator take to fulfill these requirements? Choose 2 answers.
- Create a custom junction object that includes a Master-Detail relationship field to Media Content and a Master-Detail relationship field to Distribution Territory.Answer
- Create a Roll-Up Summary field of type COUNT on the Media Content object referencing the junction object records.Answer
- CCreate a custom junction object that includes two Lookup relationship fields and enable record-level cascading deletes on both relationships.
- DCreate a Roll-Up Summary field on the Distribution Territory object that references a Lookup relationship on the junction object.
Answer
The administrator should create a custom junction object with two Master-Detail relationship fields pointing to Media Content and Distribution Territory, and create a Roll-Up Summary field of type COUNT on the Media Content object referencing the junction object.
To fulfill a many-to-many requirement with cascading deletion behavior, an administrator must construct a junction object linked by two Master-Detail relationships. Because the Media Content object acts as a master in one of these Master-Detail relationships, the administrator can build a Roll-Up Summary field of type COUNT on Media Content to calculate the total number of associated records.
Step-by-Step Solution
Key Concept
Many-to-Many Relationships and Roll-Up Summary Requirements