Soru

Zorluk: Çok zorObject Relationships (Lookup, Master-Detail, Many-to-Many)

An organization tracks safety compliance using custom objects. An administrator is tasked with connecting the Inspection_Audit__c object and the Compliance_Regulation__c object using a custom linking structure. The design must meet the following requirements:
1. Deleting an Inspection_Audit__c record must automatically delete all associated link records.
2. Deleting a Compliance_Regulation__c record must NOT delete associated link records, but instead clear the reference field value.
3. Executive managers must be able to view a real-time aggregate count of all linked audit regulations directly on each Inspection_Audit__c record.

Which two configuration actions should the administrator take to fulfill these requirements? Choose 2 answers.

  1. Create a Master-Detail relationship field on the link object referencing Inspection_Audit__c as the primary master.Cevap
  2. B
    Create a Master-Detail relationship field on the link object referencing Compliance_Regulation__c as a secondary master.
  3. Create a Lookup relationship field on the link object referencing Compliance_Regulation__c.Cevap
  4. D
    Create a Roll-Up Summary field on Compliance_Regulation__c to count the related link records across the lookup relationship.

Cevap

The administrator must create a Master-Detail relationship field on the link object pointing to Inspection_Audit__c, and a Lookup relationship field on the link object pointing to Compliance_Regulation__c.
To satisfy the scenario requirements, a Master-Detail relationship must be defined on the link object pointing to Inspection_Audit__c so that child records are deleted when the audit is deleted and so that a Roll-Up Summary field can be created on Inspection_Audit__c. Concurrently, a Lookup relationship must be created on the link object pointing to Compliance_Regulation__c so that deleting a regulation does not cascade deletion to the link record.

Adım Adım Çözüm

1
Analyze cascading deletion requirements for the parent objects.
Inspection_Audit__c requires cascading deletion (Master-Detail), whereas Compliance_Regulation__c requires record preservation (Lookup).
Master-Detail relationships enforce cascading deletes from parent to child, while Lookup relationships allow child records to remain intact.
2
Determine where Roll-Up Summary fields can be created.
A Roll-Up Summary field can be placed on Inspection_Audit__c to calculate the aggregate count of child link records.
Roll-Up Summary fields require a Master-Detail relationship to summarize child records.
3
Select the correct combination of relationship fields on the junction object.
A Master-Detail field referencing Inspection_Audit__c and a Lookup field referencing Compliance_Regulation__c fulfill all business constraints.
This hybrid design allows counting child records on the audit parent while preventing unintended data loss when regulations are removed.

Anahtar Kavram

Object Relationships & Roll-Up Summary Eligibility
Bu soruyu puanla