A Salesforce Administrator is designing a custom data model for an event management company to track relationships between Trade Shows (`Trade_Show__c`) and Exhibitors (`Exhibitor__c`). Multiple exhibitors can register for multiple trade shows, and each registration record must capture specific details such as Booth Location and Registration Fee. Additionally, if a trade show record is deleted, all related registration records must automatically be removed, and the administration must automatically aggregate the total registration fees collected directly on the trade show record. Which two configuration steps should the administrator take to fulfill these requirements? (Choose 2 answers)
- Create a custom junction object that contains Master-Detail relationship fields referencing both the Trade Show and Exhibitor objects.Answer
- Create a Roll-Up Summary field on the Trade Show object to sum the Registration Fee field from the related registration records.Answer
- CCreate a custom junction object with Lookup relationships to both objects and configure a Roll-Up Summary field on the Trade Show object.
- DCreate a Lookup relationship from the registration object to Trade Show and set the relationship deletion option to cascade delete related records.
Answer
To model a many-to-many relationship with automatic cascade deletion and aggregate calculations, the administrator must create a custom junction object with Master-Detail relationships to both objects and create a Roll-Up Summary field on the master (Trade Show) object.
Establishing a junction object with Master-Detail relationships satisfies the requirement to model a many-to-many relationship between Trade Show and Exhibitor while providing automatic cascading record deletion. Adding a Roll-Up Summary field on the Trade Show object allows the administrator to natively sum the registration fees from the underlying child records without custom code.
Step-by-Step Solution
Key Concept
Many-to-Many Relationships and Roll-Up Summary Requirements