Soru

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

Universal Containers has configured a custom architecture involving three custom objects: Program__c, Project__c, and Resource_Allocation__c.

The business analyst defines the following strict security and operational constraints:
1. Deleting a Program__c record must automatically cascade and delete all associated child Project__c records.
2. Administrators must display the sum of allocated hours from child Project__c records directly on the parent Program__c record using native declarative features.
3. Resource_Allocation__c must serve as a junction object establishing a Many-to-Many relationship between Project__c and Contact.
4. Users who possess only Read access to a parent Program__c record must be prevented from creating, editing, or deleting its related Project__c records.

Which two configuration steps must the administrator implement to satisfy these requirements? (Choose 2 answers)

  1. Create a Master-Detail relationship field on Project__c referencing Program__c and define a Roll-Up Summary field on Program__c to aggregate allocated hours.Cevap
  2. Configure the Master-Detail relationship field on Project__c with a Sharing Setting of Read/Write to require edit permissions on the master record for detail modifications.Cevap
  3. C
    Establish a Lookup relationship from Project__c to Program__c and define a Roll-Up Summary field on Program__c to calculate total hours.
  4. D
    Establish a Lookup relationship from Resource_Allocation__c to Project__c and rely on standard lookup cascade deletion to clean up junction records when a project is deleted.

Cevap

The administrator must create a Master-Detail relationship on Project__c referencing Program__c with a Roll-Up Summary field on Program__c, and configure the Master-Detail field sharing setting to Read/Write.
Creating a Master-Detail relationship from Project__c to Program__c satisfies automatic cascade deletion upon parent deletion and unlocks native Roll-Up Summary fields on Program__c. Additionally, setting the Master-Detail relationship Sharing Setting to Read/Write forces users to have edit rights on Program__c to create, edit, or delete child Project__c records.

Adım Adım Çözüm

1
Evaluate cascade deletion and aggregation requirements for Program__c and Project__c.
Determined that a Master-Detail relationship is required from Project__c (detail) to Program__c (master).
Master-Detail relationships enable automatic cascade deletion of child records and allow declarative Roll-Up Summary fields on the master object.
2
Evaluate record editing security requirements on child Project__c records based on parent Program__c access.
Configured the Master-Detail relationship Sharing Setting attribute to Read/Write.
Setting the relationship sharing setting to Read/Write restricts users with only Read access on the master record from creating, editing, or deleting detail records.

Anahtar Kavram

Master-Detail Relationship Capabilities and Security Settings
Bu soruyu puanla