Examkin

Question

Difficulty: MediumFlow Types and Triggers

A financial services organization requires automation for a custom object named Vendor_Invoice__c. The organization has defined two distinct processing needs:

1. Immediately upon the creation of an invoice record, populate the Tax_Rate__c and Payment_Terms__c fields on the triggering record before database commit.
2. Every Sunday at midnight, evaluate all existing invoice records with a status of 'Pending Approval' that have remained unapproved for more than 14 days and dispatch a summary notification to the finance team.

Which two automation configurations should the administrator implement to fulfill these requirements? (Choose two.)

  1. Deploy a Record-Triggered Flow set to Fast Field Updates (before-save) on record creation to populate fields directly on the triggering invoice record.Answer
  2. Implement a Schedule-Triggered Flow set to a weekly cadence with filter conditions to evaluate stagnant invoices and send notifications.Answer
  3. C
    Deploy a Record-Triggered Flow set to Actions and Related Records (after-save) with an explicit Update Records element targeting the triggering record.
  4. D
    Construct an Autolaunched Flow with a loop structure executing individual database queries and update operations on each invoice iteration.

Answer

Deploying a Record-Triggered Flow configured for Fast Field Updates (before-save) on record creation, along with implementing a Schedule-Triggered Flow running on a weekly schedule to evaluate records and send notifications.
For the first requirement, a Record-Triggered Flow configured for Fast Field Updates (before-save) is optimal because it modifies fields on the triggering record before the record is saved to the database, eliminating the need for an extra DML statement. For the second requirement, a Schedule-Triggered Flow configured with a weekly schedule on Sunday evaluates qualifying records in batches and executes the notification action without manual intervention.

Step-by-Step Solution

1
Analyze Requirement 1: Updating fields on the newly created record prior to database commit.
Identify that a Record-Triggered Flow configured for Fast Field Updates (before-save) is the best practice because it updates fields on the $Record prior to committing data to the database without requiring an Update Records DML element.
Before-save flows run much faster than after-save flows and avoid triggering additional save cycles or validation rules unnecessarily.
2
Analyze Requirement 2: Evaluating records at a specific recurring time and dispatching notifications.
Identify that a Schedule-Triggered Flow running weekly can filter for records meeting 'Pending Approval' for >14 days and perform outbound notification actions.
Schedule-Triggered flows are designed specifically for recurring batch jobs without requiring user interaction or a record change event.
3
Evaluate alternative and distractor architectures.
Eliminate after-save trigger flows for same-record updates and autolaunched flows with unbulkified loop operations.
After-save flows consume excessive governor limits when performing same-record updates, and autolaunched flows cannot run on an automated schedule without an external trigger or Schedule-Triggered architecture.

Key Concept

Selecting appropriate Flow types (Record-Triggered Fast Field Updates vs. Schedule-Triggered Flows) based on trigger timing and business operational requirements.
Estimated Time:1m 30s
Rate this question

Topics

Flow Types and Triggers

More questions from this topic