Question

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

A Salesforce Administrator needs to model a relationship between the standard Account object and a custom object named Vendor_Evaluation__c. The business requires that deleting an Account automatically deletes all related Vendor_Evaluation__c records, and administrators must be able to create Roll-Up Summary fields on the Account object to aggregate evaluation metrics. Which two actions must the administrator take to fulfill these requirements? (Choose 2 answers)

  1. Create a custom Master-Detail relationship field on the Vendor_Evaluation__c object that references the Account object.Answer
  2. Ensure all existing Vendor_Evaluation__c records have a populated Account reference before creating the Master-Detail relationship field.Answer
  3. C
    Create a custom Lookup relationship field on Vendor_Evaluation__c and enable Roll-Up Summary functionality in field settings.
  4. D
    Configure a Lookup relationship field on Vendor_Evaluation__c and rely on standard deletion behavior to retain child records if the Account is deleted.

Answer

The administrator must create a Master-Detail relationship field on Vendor_Evaluation__c referencing Account, and ensure all existing Vendor_Evaluation__c records have an Account populated prior to creating the field.
Creating a Master-Detail relationship field on the detail object (Vendor_Evaluation__c) pointing to the Account object satisfies both business requirements: cascading record deletion and enabling Roll-Up Summary fields on the parent Account object. Additionally, because Master-Detail fields are mandatory on detail records, any pre-existing records on the object must have their parent field populated before creating the relationship field.

Step-by-Step Solution

1
Analyze business requirements for deletion and aggregation
Automatic cascading deletion and Roll-Up Summary field capabilities require a Master-Detail relationship rather than a Lookup relationship.
Roll-Up Summary fields and automatic cascade deletion are native capabilities exclusively available on Master-Detail relationships.
2
Determine field placement and data prerequisites
The relationship field must be defined on the detail object (Vendor_Evaluation__c) pointing to the master object (Account), and all existing child records must have a parent assigned.
Detail records strictly require a parent reference; if existing records are unassigned, field creation will fail.

Key Concept

Master-Detail Relationship Capabilities and Prerequisites
Rate this question