Examkin

Question

Difficulty: MediumObject Relationships (Lookup, Master-Detail, Many-to-Many)

A Salesforce Administrator at a financial services firm is designing a custom data model to track Loan Applications (Loan_Application__c) and associated Underwriting Reviews (Underwriting_Review__c). Management has specified the following key requirements:
1. Deleting a Loan Application record must automatically delete all associated Underwriting Review records.
2. A summary field on the Loan Application record must automatically calculate the total number of linked Underwriting Review records.
3. User access permissions to an Underwriting Review record must be inherited directly from its parent Loan Application record.

Which relationship type should the administrator create on the Underwriting_Review__c object to meet these business requirements?

  1. A Master-Detail relationship field referencing Loan_Application__cAnswer
  2. B
    A Lookup relationship field referencing Loan_Application__c with a native Roll-Up Summary field configured on Loan_Application__c
  3. C
    A Lookup relationship field referencing Loan_Application__c with custom record-level sharing rules configured for security inheritance
  4. D
    A Many-to-Many junction relationship connecting Loan_Application__c and Underwriting_Review__c via a secondary custom object

Answer

The administrator should create a Master-Detail relationship field on Underwriting_Review__c referencing Loan_Application__c.
Creating a Master-Detail relationship field on the child object (Underwriting_Review__c) referencing the parent object (Loan_Application__c) satisfies all three requirements out of the box. Master-Detail relationships automatically delete detail records when the master record is deleted, permit native Roll-Up Summary fields on the master object to aggregate child record counts or values, and enforce parent-level security inheritance across all child records.

Step-by-Step Solution

1
Analyze the record deletion behavior requirement
Cascading deletion (deleting parent deletes children) is a built-in feature of Master-Detail relationships.
Master-Detail relationships enforce tight coupling where detail records cannot exist independently of their master record.
2
Analyze the aggregation requirement
Creating a standard Roll-Up Summary field on Loan_Application__c requires a Master-Detail relationship.
Salesforce standard Roll-Up Summary fields are only available on the Master object when connected to Detail objects via Master-Detail relationships.
3
Analyze the security inheritance requirement
Detail records in a Master-Detail relationship inherit sharing and security settings directly from the Master record.
The 'Controlled by Parent' sharing model is automatically enforced in Master-Detail relationships.

Key Concept

Master-Detail Relationship Capabilities and Limitations
Rate this question

Topics

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

More questions from this topic