Examkin

Question

Difficulty: HardFormula Fields and Roll-Up Summary Fields

An administrator at Cloud Kicks is configuring field requirements for a custom parent object, Equipment_Service_Plan__c, and a custom child object, Service_Log__c. The two objects are connected via a Lookup relationship so that service logs can be retained independently if a service plan is deactivated. The operations team requires a field on Equipment_Service_Plan__c that displays the total accumulated cost of all completed Service_Log__c records. Which configuration strategy should the administrator implement to fulfill this requirement while maintaining the existing relationship architecture?

  1. Create a declarative Record-Triggered Flow on Service_Log__c that executes upon creation or update to calculate and update a custom currency field on Equipment_Service_Plan__c.Answer
  2. B
    Create a native Roll-Up Summary field on Equipment_Service_Plan__c using the SUM function with filter criteria for completed service logs.
  3. C
    Create a Cross-Object Formula field on Equipment_Service_Plan__c using the SUM() function to aggregate the cost field from related child Service_Log__c records.
  4. D
    Convert the Lookup relationship to a Master-Detail relationship, acknowledging that deleting an Equipment_Service_Plan__c record will leave child Service_Log__c records orphaned without deletion.

Answer

The administrator should build a declarative Record-Triggered Flow on Service_Log__c that calculates the total cost of completed records and updates a custom currency field on Equipment_Service_Plan__c.
Because standard Roll-Up Summary fields are strictly limited to Master-Detail relationships, an administrator must use declarative automation such as Record-Triggered Flows (or Apex triggers) to aggregate child record data up to a parent record connected via a Lookup relationship. This preserves the independent lifecycle of the child records while meeting the reporting requirement.

Step-by-Step Solution

1
Analyze object relationship constraints
Equipment_Service_Plan__c and Service_Log__c are joined via a Lookup relationship to preserve child records independently upon parent deactivation/deletion.
Master-Detail relationships enforce cascading deletes, which violates the requirement to retain service logs.
2
Evaluate native Roll-Up Summary field availability
Native Roll-Up Summary fields are disabled for Lookup relationships in standard Salesforce functionality.
Roll-Up Summary fields strictly require a Master-Detail relationship between parent and child objects.
3
Evaluate alternative declarative automation tools
A Record-Triggered Flow can summarize child record values and update a parent custom field without altering relationship definitions.
Flow automation provides custom roll-up capabilities while keeping the underlying Lookup relationship architecture intact.

Key Concept

Roll-Up Summary Relationship Prerequisites and Declarative Workarounds
Estimated Time:2m 0s
Rate this question

Topics

Formula Fields and Roll-Up Summary Fields

More questions from this topic