An administrator is designing a custom data structure to manage IT infrastructure assets for an enterprise client. The requirement calls for establishing a many-to-many relationship between a custom object named Server_Instance__c and another custom object named Software_License__c using a custom junction object named License_Assignment__c. Additionally, business rules specify that deleting a Server_Instance__c record must automatically delete all associated License_Assignment__c records, and total active license fees must be calculated directly on the Server_Instance__c record. Which two configuration steps must the administrator complete on the License_Assignment__c object to fulfill these requirements? (Choose 2 answers.)
- Create a Master-Detail relationship field referencing the Server_Instance__c custom object.Cevap
- Create a Master-Detail relationship field referencing the Software_License__c custom object.Cevap
- CCreate a Lookup relationship field referencing Server_Instance__c and create a Roll-Up Summary field on Server_Instance__c.
- DCreate a Lookup relationship field referencing Software_License__c and select the option to restrict deletion of the lookup record.
Cevap
The administrator must create two Master-Detail relationship fields on the License_Assignment__c junction object: one referencing Server_Instance__c and one referencing Software_License__c.
To build a many-to-many relationship that supports automatic record deletion cascade and Roll-Up Summary field calculations on the primary object, the administrator must configure two Master-Detail relationship fields on the custom junction object (License_Assignment__c): one pointing to Server_Instance__c and the second pointing to Software_License__c.
Adım Adım Çözüm
Anahtar Kavram
Junction Objects and Master-Detail Relationship Behaviors
Tahmini Süre:2m 0s