試験CRT-450 トピック1 問題70 スレッド

To implement the total_Hours__c field on the Opportunity object, the developer should use a roll-up summary field on the Opportunity object. A roll-up summary field calculates values from related records, such as those in a related list1. In this case, the roll-up summary field on the Opportunity object would sum up the Number_of_Hours__c values from the Sales_Help_Request__c records that are related to the Opportunity via the Lookup relationship. This is the simplest and most declarative way to achieve the requirement.
The other options are not valid because:
* A roll-up summary field on the Sales_Help_Request__c object would not be able to aggregate the values from the child records to the parent record. A roll-up summary field can only calculate values from the child records to the parent record in a master-detail relationship, not a lookup relationship1.
* A trigger on the Opportunity object would not be able to access the Number_of_Hours__c values from the Sales_Help_Request__c records without performing a SOQL query. A trigger can only access the fields of the records that are being inserted, updated, deleted, or undeleted2. A trigger would also require more coding and testing than a roll-up summary field.
* A record-triggered flow on the Sales_Help_Request__c object would not be able to update the total_Hours__c field on the Opportunity object without performing a SOQL query and a DML
* operation. A record-triggered flow can only access and update the fields of the record that triggered the flow3. A record-triggered flow would also be more complex and less efficient than a roll-up summary field.
References:
* 1: Roll-Up Summary Field - Salesforce
* 2: Triggers and Order of Execution - Salesforce
* 3: Record-Triggered Flows - Salesforce