A Salesforce Administrator at an enterprise software firm needs to model a data structure to track software license allocations across corporate departments. A single software license can be allocated to multiple departments, and a single department can hold allocations for multiple software licenses. Each allocation must record unique metadata such as seat count and allocation date. Furthermore, if either a software license or a department record is deleted, its associated allocation records must be automatically removed. Which two configuration steps should the administrator take to fulfill these requirements? (Select 2 answers.)
- Create a custom junction object with two Master-Detail relationship fields linking to the Software License and Department objects.Cevap
- Add custom fields for seat count and allocation date directly onto the custom junction object.Cevap
- CCreate a custom junction object with two Lookup relationship fields to ensure allocation records are preserved if a parent record is deleted.
- DCreate Roll-Up Summary fields on the Department object pointing directly to a Lookup relationship on the Software License object.
Cevap
To model a many-to-many relationship with automatic cascade deletion, the administrator must create a custom junction object containing two Master-Detail relationship fields (referencing Software License and Department) and place the allocation-specific fields (seat count and allocation date) directly on that junction object.
A many-to-many relationship in Salesforce requires a custom junction object. Using two Master-Detail relationship fields ensures that deleting either a Software License or a Department record automatically deletes the associated allocation record. Storing seat count and allocation date on the junction object properly captures metadata specific to each allocation.
Adım Adım Çözüm
Anahtar Kavram
Junction Objects and Master-Detail Relationship Rules