Examkin

Question

Difficulty: Very hardFormula Fields and Roll-Up Summary Fields

Cloud Kicks tracks custom Project__c records that are linked to the standard AccountAccount object via a Lookup relationship, allowing independent record ownership and security settings. The executive team requires a real-time field on the AccountAccount record displaying the total budget of all related active projects. When attempting to create a new field on AccountAccount, the administrator observes that the Roll-Up Summary field type is disabled. What is the fundamental cause of this behavior, and how should the administrator meet the requirement using declarative functionality?

  1. Roll-Up Summary fields require a Master-Detail relationship; the administrator should create a custom currency field on Account and use a Record-Triggered Flow on Project__c to recalculate the total upon record creation, update, or deletion.Answer
  2. B
    Roll-Up Summary fields are disabled on standard objects when referencing custom child objects; the administrator must convert the Account relationship into a custom lookup formula field on the Project__c object.
  3. C
    Roll-Up Summary fields cannot be selected because the Lookup field on Project__c is editable; making the Lookup field required and read-only will enable native Roll-Up Summary capabilities on the Account object.
  4. D
    The administrator must convert the Lookup relationship on Project__c to a Master-Detail relationship to enable Roll-Up Summary fields, ignoring that deleting an Account will now automatically cascade delete all related Project__c records and change record ownership behavior.

Answer

Roll-Up Summary fields require a Master-Detail relationship; the administrator should create a custom currency field on Account and use a Record-Triggered Flow on Project__c to recalculate the total upon record creation, update, or deletion.
The correct response identifies that declarative Roll-Up Summary fields are structurally limited to Master-Detail relationships. Because the business requirement explicitly demands independent record ownership and security on the child object (which Lookup relationships provide), converting the relationship to Master-Detail would violate sharing and deletion requirements. Therefore, creating a custom target field on the parent object updated via a Record-Triggered Flow on the child object is the proper declarative solution.

Step-by-Step Solution

1
Analyze the relationship model requirements
Identified that independent record ownership and security settings require a Lookup relationship rather than a Master-Detail relationship.
Master-Detail relationships inherit sharing and security from the master record and do not allow independent owner assignment on child records.
2
Evaluate platform limits for Roll-Up Summary fields
Confirmed that native Roll-Up Summary fields are disabled because the parent object is linked via a Lookup relationship.
Salesforce declarative Roll-Up Summary fields are supported only on the master side of Master-Detail relationships.
3
Design the declarative automation solution
Selected a combination of a custom numeric/currency field on Account and a Record-Triggered Flow on Project__c to update the total asynchronously/synchronously on record changes.
Record-Triggered Flows provide declarative aggregation capability without compromising the underlying object relationship structure.

Key Concept

Roll-Up Summary Field Eligibility and Lookup Aggregation Strategies
Rate this question

Topics

Formula Fields and Roll-Up Summary Fields

More questions from this topic