Examkin

Question

Difficulty: HardFlow Types and Triggers

An administrator at CloudHorizon is designing automation for the custom object Partner_Tier_Review__c to fulfill two distinct business requirements:

1. Automatically calculate and set the Expiration_Notice_Date__c and Tier_Status__c fields on the triggering Partner_Tier_Review__c record whenever its status changes to 'Pending Approval', prior to committing the record to the database.
2. On the first day of every month at 1:00 AM, automatically evaluate all active Partner_Tier_Review__c records and generate a reminder Task record for partner account managers if the review status remains 'Pending Approval'.

Which TWO automation design choices should the administrator implement to fulfill these requirements efficiently? (Select 2)

  1. Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) that triggers when a Partner_Tier_Review__c record is updated to 'Pending Approval'.Answer
  2. Configure a Schedule-Triggered Flow scheduled to run monthly that queries active Partner_Tier_Review__c records with a status of 'Pending Approval' and creates Task records.Answer
  3. C
    Configure a Record-Triggered Flow optimized for Actions and Related Records (After-Save) that triggers when a Partner_Tier_Review__c record is updated to 'Pending Approval' to set the record's field values.
  4. D
    Configure a Screen Flow invoked by an Apex scheduled job to process background record updates and create Task records without user interaction.

Answer

The administrator should implement a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) for same-record field modifications, and a Schedule-Triggered Flow executing monthly for automated batch task creation.
Updating field values on the originating record prior to saving to the database is best executed by a Record-Triggered Flow optimized for Fast Field Updates (before-save), as it avoids unnecessary DML operations. For recurring automated tasks operating on a batch of records on a specific cadence (monthly at 1:00 AM), a Schedule-Triggered Flow is the designated standard automation tool.

Step-by-Step Solution

1
Evaluate Requirement 1 (updating fields on the originating record prior to database commit).
Determine that updating fields on the record initiating the transaction before saving requires a Record-Triggered Flow configured for Fast Field Updates (Before-Save).
Before-save flows modify the record payload directly prior to database insertion/update, avoiding extra DML operations and save cycles.
2
Evaluate Requirement 2 (recurring batch processing to create related records on a scheduled cadence).
Determine that executing an automated check on a recurring schedule (monthly) to create related Task records requires a Schedule-Triggered Flow.
Schedule-Triggered flows provide native scheduling capabilities to run logic across targeted record batches without requiring custom code or user interaction.

Key Concept

Selecting the correct Salesforce Flow trigger types (Record-Triggered Fast Field Updates vs. Schedule-Triggered Flows) based on record update context and execution scheduling requirements.
Estimated Time:2m 0s
Rate this question

Topics

Flow Types and Triggers

More questions from this topic