Examkin

Question

Difficulty: MediumFlow Types and Triggers

An administrator at a professional certification institute is designing an automation solution for a custom object named Course_Registration__c to satisfy two business requirements:

1. When a new registration record is submitted, calculate and set the Discount_Amount__c and Final_Fee__c fields on the record before it is committed to the database.
2. Every Monday at 8:00 AM, identify all registration records where the Status__c is 'Pending Payment' for more than 5 days and send automated payment reminder emails to the applicants.

Which TWO Flow configurations should the administrator implement to meet these requirements with optimal performance? (Choose 2)

  1. A Record-Triggered Flow optimized for Fast Field Updates (Before-Save) on the Course_Registration__c object.Answer
  2. A Schedule-Triggered Flow configured with weekly recurrence specifying filter criteria for Course_Registration__c records.Answer
  3. C
    A Record-Triggered Flow optimized for Actions and Related Records (After-Save) to update fields on the triggering Course_Registration__c record.
  4. D
    A Screen Flow deployed to the administrator home page designed to execute an unguided batch loop across all Course_Registration__c records.

Answer

The administrator should implement a Record-Triggered Flow configured for Fast Field Updates (Before-Save) for same-record calculations, and a Schedule-Triggered Flow running weekly to process overdue registrations and send reminder emails.
The correct architecture pairs a Fast Field Updates (Before-Save) Record-Triggered Flow with a Schedule-Triggered Flow. Before-Save flows are specifically designed to populate and update fields on the triggering record before it is committed to the database, offering optimal performance without additional DML transactions. Schedule-Triggered Flows natively support recurring scheduled execution (such as every Monday at 8:00 AM) and automatically query and batch-process the filtered records to perform asynchronous actions like sending reminder emails.

Step-by-Step Solution

1
Evaluate requirement 1 regarding same-record field updates prior to database commit.
Identify that updating fields on the triggering record before database save is best handled by a Record-Triggered Flow set to Fast Field Updates (Before-Save).
Before-save flows update fields directly in memory on the $Record global variable without issuing extra DML statements, ensuring maximum execution speed and preventing recursive trigger loops.
2
Evaluate requirement 2 regarding automated batch processing at a designated recurring time.
Identify that a recurring weekly batch operation requiring email alerts is handled natively by a Schedule-Triggered Flow.
Schedule-Triggered Flows allow administrators to define recurring schedules and filter batches of records without requiring custom code or user intervention.
3
Eliminate inappropriate automation types.
Reject After-Save flows for same-record updates and Screen Flows for automated background scheduling.
After-save updates incur unnecessary DML overhead for same-record changes, and Screen Flows require interactive user sessions rather than background scheduling.

Key Concept

Selecting the optimal Flow type and trigger timing based on execution context (before-save for same-record updates vs. schedule-triggered for recurring time-based batch operations).
Rate this question

Topics

Flow Types and Triggers

More questions from this topic