An administrator at a medical device manufacturing company needs to track calibration records for specialized factory machinery. The business requirements state that each Calibration_Log__c record must strictly belong to a Machine__c record, access permissions for calibration logs must be controlled by access to the parent machine record, and deleting a Machine__c record must automatically remove all associated Calibration_Log__c records. Additionally, the administrator must display the total number of related Calibration_Log__c records directly on the Machine__c record. Which two configuration steps should the administrator implement to fulfill these requirements? (Choose 2 answers)
- Create a Master-Detail relationship field on the Calibration_Log__c object that references the Machine__c object.Cevap
- Create a Roll-Up Summary field on the Machine__c object using the COUNT aggregate operation on Calibration_Log__c records.Cevap
- CCreate a Lookup relationship field on the Calibration_Log__c object and configure a Roll-Up Summary field on the Machine__c object.
- DCreate a Lookup relationship field on the Calibration_Log__c object with the 'Delete this record also' cascade deletion option selected.
Cevap
The administrator should create a Master-Detail relationship field on the child object (Calibration_Log__c) pointing to the parent object (Machine__c), and create a Roll-Up Summary field on the parent object (Machine__c) to count the related calibration logs.
Defining a Master-Detail relationship field on Calibration_Log__c referencing Machine__c ensures that security access is inherited from the parent Machine__c record and that child calibration logs are automatically cascade-deleted when a parent Machine__c record is removed. Furthermore, establishing a Master-Detail relationship enables the creation of a native Roll-Up Summary field on Machine__c to count the related detail records.
Adım Adım Çözüm
Anahtar Kavram
Master-Detail Relationship Capabilities and Roll-Up Summary Fields
Tahmini Süre:1m 30s