The operations department at an equipment rental company uses a custom object named Equipment_Inspection__c. The team requires two specific automated processes:
1. Immediately calculate and assign the Risk_Level__c field on the Equipment_Inspection__c record itself whenever it is created or updated, prior to the record being committed to the database.
2. Automatically evaluate all Equipment_Inspection__c records that failed inspection and create a related Maintenance_Task__c record for each one every night at 11:00 PM.
Which two flow types and trigger settings should be utilized to satisfy these requirements? (Choose two.)
- A Record-Triggered Flow on Equipment_Inspection__c set to Fast Field Updates (before-save) to calculate and assign the Risk Level field.Answer
- A Schedule-Triggered Flow scheduled to execute daily at 11:00 PM that queries failed inspections and creates related maintenance tasks.Answer
- CA Record-Triggered Flow on Equipment_Inspection__c set to Actions and Related Records (after-save) to calculate and assign the Risk Level field.
- DAn Autolaunched Flow (no trigger) containing a Pause element configured to execute nightly at 11:00 PM across all failed inspection records.
Answer
The two required configurations are a Record-Triggered Flow on Equipment_Inspection__c configured for Fast Field Updates (before-save) to update the Risk Level field, and a Schedule-Triggered Flow configured to run daily at 11:00 PM to process failed inspections and generate maintenance tasks.
For requirement 1, updating a field on the triggering record before database commit is the primary use case for Fast Field Updates (before-save record-triggered flow). For requirement 2, running batch creation of related records at a specific scheduled time (11:00 PM nightly) is the standard function of a Schedule-Triggered Flow.
Step-by-Step Solution
Key Concept
Selecting optimal Flow trigger types based on execution timing (before-save vs after-save vs scheduled execution)
Estimated Time:1m 15s