Examkin

Question

Difficulty: HardAutomation Tool Selection

A renewable energy enterprise tracks site surveys using a custom object named Installation Task, which maintains a Lookup relationship to the standard Account object. When an Installation Task status changes to 'Completed', the administrator must implement declarative automation to meet two specific requirements:
1. Update status tracking fields directly on the triggering Installation Task record before it is committed to the database.
2. Calculate and update summary metrics on the parent Account record.

Which TWO declarative solutions should the administrator implement to meet these requirements while adhering to Salesforce performance best practices? (Select TWO.)

  1. Configure a Record-Triggered Flow optimized for Fast Field Updates (before-save) on the Installation Task object to update fields on the triggering record.Answer
  2. Configure a Record-Triggered Flow optimized for Actions and Related Records (after-save) on the Installation Task object to update the parent Account fields.Answer
  3. C
    Create a Roll-Up Summary field on the Account object to aggregate metric values from related Installation Task records.
  4. D
    Configure a single Record-Triggered Flow optimized for Actions and Related Records (after-save) to update both the triggering Installation Task and the parent Account fields.

Answer

The administrator should implement a Record-Triggered Flow configured for Fast Field Updates (before-save) to update fields on the triggering record, and a Record-Triggered Flow configured for Actions and Related Records (after-save) to update the parent Account record.
In Salesforce automation best practices, field modifications on the triggering record itself must be implemented using a Record-Triggered Flow configured for Fast Field Updates (before-save) to eliminate extra save cycles. Modifications to parent records connected through a Lookup relationship require a Record-Triggered Flow configured for Actions and Related Records (after-save) because Roll-Up Summary fields cannot cross Lookup boundaries.

Step-by-Step Solution

1
Evaluate same-record automation requirement
Identify that field updates on the triggering object should utilize Fast Field Updates (before-save) flows.
Before-save flows run before records are written to the database, offering up to 10x faster execution and avoiding redundant DML update statements.
2
Evaluate cross-object parent record automation requirement
Identify that updates to a parent record across a Lookup relationship require an Actions and Related Records (after-save) flow.
Native Roll-Up Summary fields are unavailable for Lookup relationships, necessitating an after-save record-triggered flow to execute cross-object record updates.

Key Concept

Salesforce Automation Tool Selection and Record-Triggered Flow Execution Optimization
Rate this question

Topics

Automation Tool Selection

More questions from this topic