Examkin

Question

Difficulty: HardFlow Types and Triggers

An administrator at CloudData SaaS is designing automation for the custom object Subscription_Contract__c. The business requires the following two automated processes:

1. Whenever a Subscription_Contract__c record's status is changed to "Pending Renewal", the system must automatically calculate and update the Renewal_Discount__c field on that same triggering contract record prior to committing changes to the database.
2. Whenever a Subscription_Contract__c record's status is changed to "Renewed", the system must create a child Renewal_Notice__c record and execute an outbound callout notification to an external billing endpoint.

Which TWO flow trigger configurations should the administrator select to fulfill these requirements in accordance with Salesforce best practices? (Select TWO.)

  1. Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) to handle the same-record field update on Subscription_Contract__c.Answer
  2. Configure a Record-Triggered Flow set to Actions and Related Records (After-Save) to create the child Renewal_Notice__c record and initiate the external outbound callout.Answer
  3. C
    Configure a single Before-Save Record-Triggered Flow to execute both the same-record field updates and the creation of the child Renewal_Notice__c record.
  4. D
    Configure an After-Save Record-Triggered Flow for the same-record update and use an explicit Update Records element to write the new Renewal_Discount__c value to the triggering record.

Answer

The administrator should use a Before-Save (Fast Field Updates) Record-Triggered Flow to update fields on the triggering Subscription_Contract__c record, and an After-Save (Actions and Related Records) Record-Triggered Flow to create the child Renewal_Notice__c record and make external callouts.
The solution requires two distinct trigger types according to Salesforce automation best practices. Fast Field Updates (Before-Save) flows are designed specifically for updating fields on the record that launched the flow prior to committing to the database. Actions and Related Records (After-Save) flows are required when performing operations on related records (such as inserting child records) or performing integrations and external callouts.

Step-by-Step Solution

1
Analyze Requirement 1 for same-record field updates prior to database commit.
Identified that Fast Field Updates (Before-Save Record-Triggered Flow) is the optimal trigger type because it modifies values on `$Record` directly before saving, avoiding unnecessary DML overhead.
Before-save triggers run 10x faster than after-save triggers for same-record updates and do not require DML elements.
2
Analyze Requirement 2 for creating child records and calling external endpoints upon renewal.
Identified that Actions and Related Records (After-Save Record-Triggered Flow) is required.
Creating related records (DML operations on other objects) and executing callouts/actions require the record ID to exist and the database transaction to be in the after-save phase.

Key Concept

Selecting between Before-Save (Fast Field Updates) and After-Save (Actions and Related Records) Flow triggers based on target object scope and execution capabilities.
Rate this question

Topics

Flow Types and Triggers

More questions from this topic