Examkin

Question

Difficulty: Very hardFlow Types and Triggers

Universal Containers requires an automated solution for managing Case lifecycle events according to three key requirements:
1. Update a custom internal priority score on the Case record prior to saving it to the database.
2. Send a payload to an external REST Web API endpoint and create a follow-up Task record whenever a Case status is changed to Escalated.
3. Perform a weekly batch review of all open Case records inactive for more than 14 days and update their status to Pending Archive.

Which TWO flow types and trigger configurations should the administrator select to fulfill these requirements while adhering to Salesforce performance and governor limit best practices?

  1. Configure a Fast Field Update (Before-Save) Record-Triggered Flow to set the custom internal priority score on the triggering Case record.Answer
  2. Configure a Schedule-Triggered Flow that runs weekly to filter inactive Case records and execute the status update.Answer
  3. C
    Configure an Actions and Related Records (After-Save) Record-Triggered Flow to calculate and save the custom internal priority score on the triggering Case record.
  4. D
    Configure an Autolaunched Flow inside a SOQL loop within a batch Apex trigger to invoke the external REST Web API callout for each escalated record.

Answer

The administrator should implement a Fast Field Update (Before-Save) Record-Triggered Flow for same-record updates before database commit, and a Schedule-Triggered Flow running weekly to handle scheduled batch processing of inactive records.
The solution requires matching business needs with optimal flow types: (1) Updating fields on the triggering record before database commit is best performed using a Fast Field Update (Before-Save) Record-Triggered Flow because it modifies the record in memory without an extra DML statement. (2) Performing routine interval-based evaluation of inactive records is best handled by a Schedule-Triggered Flow, which automatically processes records in batch mode at scheduled times.

Step-by-Step Solution

1
Analyze same-record field modification requirement prior to database save.
Identified that Fast Field Update (Before-Save) Record-Triggered Flow is optimal because it modifies values in memory prior to the database commit without incurring extra DML overhead.
Before-save flows are up to 10 times faster than after-save flows for same-record updates.
2
Analyze recurring time-based batch evaluation requirement.
Identified that a Schedule-Triggered Flow should be used to run at specified intervals (weekly) on target record datasets.
Schedule-triggered flows allow filtering records directly in the start element and running batch operations asynchronously.
3
Evaluate distractors involving after-save same-record updates and DML/callout operations in loops.
Eliminated choices that use after-save flows for same-record field updates or execute flow invocations inside iteration loops.
These improper patterns violate order of execution optimization rules and Salesforce governor limits.

Key Concept

Flow Trigger Types and Execution Optimization (Before-Save vs After-Save vs Schedule-Triggered)
Rate this question

Topics

Flow Types and Triggers

More questions from this topic