Question

Difficulty: MediumAutomation Tool Selection

A solar energy company tracks commercial installation projects using a custom Project Milestone object. Whenever a technician updates a Project Milestone record to indicate that site inspection is complete, the system must automatically set the Inspection Completion Timestamp on that same record before it is saved to the database, ensuring maximum system performance and avoiding additional DML operations.

Which automation mechanism should the administrator select to fulfill this requirement?

  1. A
    Create a Record-Triggered Flow that runs on the Actions and Related Records execution path to update the record.
  2. B
    Define a Roll-Up Summary field on the parent Account lookup relationship to compute the timestamp value.
  3. Build a Record-Triggered Flow optimized for Fast Field Updates that updates fields on the triggering record.Answer
  4. D
    Establish an Approval Process that uses an initial submission action to set the field and lock the milestone.

Answer

Build a Record-Triggered Flow optimized for Fast Field Updates that updates fields on the triggering record.
A Record-Triggered Flow configured for Fast Field Updates (before-save) is the best-practice declarative tool when updating fields on the triggering record. It runs before the record commits to the database, making updates in memory without consuming extra DML limits or initiating additional save cycles.

Step-by-Step Solution

1
Analyze the business requirement and target record
Identified that the update targets a field on the triggering Project Milestone record itself.
Determining whether the automation affects the triggering record or related records dictates optimal flow trigger architecture.
2
Evaluate execution timing and performance constraints
Selected before-save execution (Fast Field Updates) rather than after-save execution.
Fast Field Updates execute before database commit, modifying record fields in memory up to ten times faster without firing additional DML events or recursive triggers.
3
Eliminate inappropriate declarative tools
Ruled out Approval Processes, Roll-Up Summary fields, and after-save Flows.
Approval processes add unneeded record locks and submission steps, roll-ups require master-detail relationships, and after-save flows incur redundant database roundtrips.

Key Concept

Selecting Fast Field Updates (before-save) Record-Triggered Flows for same-record field modifications
Estimated Time:1m 15s
Rate this question