An administrator at Cloud Kicks needs to build automation for custom Subscription__c records to satisfy two operational requirements:
1. Update the Discount_Tier__c field on the triggering subscription record before it is committed to the database whenever the subscription value changes.
2. Create a Renewal_Opportunity__c record and send an email notification to the account owner after a subscription is marked as 'Active'.
Which two flow trigger configurations should the administrator use to achieve this? (Choose two.)
- Configure a Record-Triggered Flow optimized for Fast Field Updates (before-save) to update the Discount Tier on the triggering record.Answer
- Configure a Record-Triggered Flow optimized for Actions and Related Records (after-save) to create the renewal opportunity and send the email notification.Answer
- CConfigure a Record-Triggered Flow optimized for Actions and Related Records (after-save) to calculate and update the Discount Tier on the triggering record.
- DConfigure a Record-Triggered Flow optimized for Fast Field Updates (before-save) to create the renewal opportunity and send the email notification.
Answer
The administrator should configure a Record-Triggered Flow optimized for Fast Field Updates (before-save) for same-record updates, and a Record-Triggered Flow optimized for Actions and Related Records (after-save) for creating related records and sending emails.
Record-Triggered Flows provide two main trigger optimization paths: Fast Field Updates (before-save) and Actions and Related Records (after-save). Updating fields on the triggering record before save is best handled by Fast Field Updates because it modifies record values directly in memory prior to the database commit. Conversely, creating related records and executing communication actions like sending emails require an after-save context (Actions and Related Records) because the triggering record must already be committed and have a valid ID.
Step-by-Step Solution
Key Concept
Selecting the appropriate Record-Triggered Flow optimization (Fast Field Updates vs. Actions and Related Records) based on the target object and action type.