Question

Difficulty: MediumFlow Types and Triggers

A Salesforce administrator is tasked with updating the custom field Risk_Score__c on the Case object whenever a Case record is created or modified, prior to saving the record to the Salesforce database. The calculation depends solely on field values within the triggering Case record itself, without requiring changes to related records or external web service callouts. Which flow implementation option provides the most efficient and recommended approach?

  1. Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save).Answer
  2. B
    Configure a Record-Triggered Flow optimized for Actions and Related Records (After-Save).
  3. C
    Configure a Schedule-Triggered Flow that runs nightly to update the field on modified Case records.
  4. D
    Configure an Autolaunched Flow invoked by a Process Builder process upon Case creation or update.

Answer

Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save).
Configuring a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) is the recommended best practice when updating values on the triggering record prior to database commit. Before-Save flows update the record values in memory before saving to the database, offering optimal execution speed and avoiding additional DML operations or re-triggering validation rules.

Step-by-Step Solution

1
Analyze the automation requirement and trigger timing needs.
The requirement involves modifying fields on the triggering record itself during record creation or update before database commit.
Determining whether changes affect the triggering record or related records guides selection between before-save and after-save optimization.
2
Evaluate Salesforce flow trigger options for performance and best practice.
Fast Field Updates (Before-Save) execute 10x faster than after-save automations because values are assigned directly to the record before it writes to the database without requiring extra DML operations.
Salesforce architecture mandates Before-Save record-triggered flows as the optimal choice for same-record field updates.

Key Concept

Fast Field Updates vs Actions and Related Records in Record-Triggered Flows
Rate this question