Examkin

Soru

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

An organization requires a custom data model to track equipment assignments between technicians and tools. A single equipment assignment record must link one technician to one tool, forming a many-to-many relationship between technicians and tools. The business analyst specifies the following operational rules:
1. If a technician record is deleted, all associated equipment assignment records must be automatically removed.
2. If a tool record is deleted, associated equipment assignment records must remain in the system for auditing purposes.
3. Executive leadership must be able to view total assigned equipment counts directly on technician records using standard declarative aggregate fields.

Which TWO configuration steps must the administrator implement on the Equipment_Assignment__c custom object to meet these requirements? (Choose 2 answers)

  1. Define a Master-Detail relationship field on Equipment_Assignment__c that references Technician__c.Cevap
  2. Define a Lookup relationship field on Equipment_Assignment__c that references Tool__c.Cevap
  3. C
    Define a Master-Detail relationship field on Equipment_Assignment__c that references Tool__c.
  4. D
    Create a Roll-Up Summary field on the Tool__c object to aggregate related Equipment_Assignment__c records.

Cevap

The administrator must create a Master-Detail relationship pointing to Technician__c and a Lookup relationship pointing to Tool__c on the Equipment_Assignment__c junction object.
To satisfy all requirements, Equipment_Assignment__c acts as a junction object. Configuring a Master-Detail relationship to Technician__c ensures automatic deletion cascade when a technician is removed and allows standard Roll-Up Summary fields on Technician__c. Configuring a Lookup relationship to Tool__c prevents tool deletions from cascading to equipment assignments, preserving assignment history.

Adım Adım Çözüm

1
Analyze deletion cascade requirements for Technician__c
Technician__c must be the master in a Master-Detail relationship with Equipment_Assignment__c so that deleting a technician record automatically cascades deletion to detail records.
Master-Detail relationships enforce parent-child deletion cascade behavior.
2
Analyze deletion behavior and auditing requirements for Tool__c
Equipment_Assignment__c must use a Lookup relationship to reference Tool__c.
Lookup relationships allow child records to persist independently when parent records are deleted.
3
Analyze standard Roll-Up Summary capabilities on Technician__c and Tool__c
Roll-Up Summary fields are natively supported on Technician__c because it is the master object, whereas Tool__c cannot use standard Roll-Up Summary fields due to the Lookup link.
Salesforce platform rules strictly limit standard Roll-Up Summary fields to the master side of Master-Detail relationships.

Anahtar Kavram

Designing Many-to-Many Junction Objects with Mixed Master-Detail and Lookup Relationships
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Object Relationships (Lookup, Master-Detail, Many-to-Many)

Bu konudan daha fazla soru