Examkin

Soru

Zorluk: ZorObject Relationships (Lookup, Master-Detail, Many-to-Many)

Universal Containers uses a custom object named Project__c to track consulting engagements and a custom object named Consultant__c to manage staff availability. A Salesforce Administrator must establish a relationship structure using a custom object named Assignment__c to link consultants to projects. The business requirements state that:
1. Deleting a Project__c record must automatically delete all related Assignment__c records.
2. Deleting a Consultant__c record must leave the related Assignment__c records intact while clearing the consultant reference.
3. Administrators must be able to create Roll-Up Summary fields on the Project__c object to calculate total billable hours from related Assignment__c records.

Which relationship configuration on the Assignment__c object satisfies all of these requirements?

  1. Create a Master-Detail relationship pointing to Project__c and a Lookup relationship pointing to Consultant__c.Cevap
  2. B
    Create a Lookup relationship pointing to Project__c with cascade delete enabled and a Lookup relationship pointing to Consultant__c.
  3. C
    Create a Master-Detail relationship pointing to both Project__c and Consultant__c, enabling reparenting on the Consultant__c relationship.
  4. D
    Create a Lookup relationship pointing to Project__c and a Master-Detail relationship pointing to Consultant__c.

Cevap

Create a Master-Detail relationship pointing to Project__c and a Lookup relationship pointing to Consultant__c.
Establishing a Master-Detail relationship from Assignment__c to Project__c fulfills two requirements: deleting a Project__c record cascades deletion to related Assignment__c records, and it allows Roll-Up Summary fields to be created on Project__c. Establishing a Lookup relationship from Assignment__c to Consultant__c ensures that deleting a Consultant__c record will not delete the Assignment__c record.

Adım Adım Çözüm

1
Analyze the requirement for cascading record deletion and Roll-Up Summary capability on Project__c.
Project__c must be the Master object in a Master-Detail relationship with Assignment__c.
Master-Detail relationships enforce cascade deletion from master to detail and enable Roll-Up Summary fields on the master object.
2
Analyze the requirement for record preservation upon deletion of Consultant__c.
Consultant__c must be linked to Assignment__c via a Lookup relationship.
Lookup relationships allow child records to remain intact when the parent record is deleted, clearing the lookup field value.
3
Combine the relationship definitions on the Assignment__c object.
Assignment__c requires one Master-Detail field referencing Project__c and one Lookup field referencing Consultant__c.
This hybrid structure satisfies all cascading delete, roll-up summary, and record preservation requirements.

Anahtar Kavram

Master-Detail vs. Lookup Relationship Behaviors and Limitations
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

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

Bu konudan daha fazla soru