Examkin

Soru

Zorluk: OrtaFlow Types and Triggers

An administrator at a medical device manufacturing company is designing automation for a custom object named Device_Complaint__c. The business requires the following behavior:
1. Automatically calculate and update the Severity_Score__c field on the triggering Device_Complaint__c record whenever it is created or updated, maximizing system performance.
2. Create child Investigation_Task__c records and send an email alert to the safety committee when the complaint status changes to 'High Risk'.

Which two Flow trigger configurations should the administrator use to satisfy these requirements? (Choose two.)

  1. A Record-Triggered Flow optimized for Fast Field Updates to update the Severity_Score__c field on the triggering record before it is saved to the database.Cevap
  2. A Record-Triggered Flow optimized for Actions and Related Records to create the Investigation_Task__c records and send the email alert after the record is saved.Cevap
  3. C
    A Record-Triggered Flow optimized for Fast Field Updates to create the Investigation_Task__c records and dispatch the email alert.
  4. D
    A Record-Triggered Flow optimized for Actions and Related Records using an explicit Update Records element to modify the Severity_Score__c field on the triggering record.

Cevap

The administrator should implement a Record-Triggered Flow optimized for Fast Field Updates for same-record updates, and a Record-Triggered Flow optimized for Actions and Related Records to create related records and send email alerts.
Salesforce provides two primary optimization settings for record-triggered flows: 'Fast Field Updates' (before-save) and 'Actions and Related Records' (after-save). Updating fields on the triggering record before database commit is best handled by Fast Field Updates because it executes in memory without additional DML transactions. In contrast, creating related records and sending email alerts require the record to be committed to the database, which necessitates the Actions and Related Records configuration.

Adım Adım Çözüm

1
Analyze Requirement 1 for updating fields on the triggering record.
Identify that setting Severity_Score__c on Device_Complaint__c is a same-record update.
Fast Field Updates (before-save) run up to 10 times faster than after-save flows because they update the record fields in memory prior to the database commit without creating additional DML events.
2
Analyze Requirement 2 for creating related records and external notifications.
Identify that creating Investigation_Task__c records and sending email alerts require database persistence.
Before-save flows do not support core actions (like email alerts) or creating/modifying related records; these capabilities require an Actions and Related Records (after-save) trigger.
3
Combine the optimal trigger configurations.
Select Fast Field Updates for the field calculation and Actions and Related Records for the tasks and email alerts.
Separating concerns according to Salesforce architectural best practices optimizes governor limits and adheres to standard order-of-execution rules.

Anahtar Kavram

Selecting appropriate Record-Triggered Flow optimization paths (Fast Field Updates vs. Actions and Related Records) based on required operations and execution performance.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Flow Types and Triggers

Bu konudan daha fazla soru