Examkin

Soru

Zorluk: ZorFlow Types and Triggers

An administrator at Universal Containers is building automation for a custom object named Fulfillment_Order__c. When a Fulfillment_Order__c record is updated with the status set to 'Ready for Shipping', two automated tasks must occur:
1. Update the custom field Standard_Handling_Fee__c on the triggering Fulfillment_Order__c record.
2. Create a new related Shipping_Manifest__c record and make a callout to an external logistics service API.

Which two trigger types and architectural configurations should the administrator select in Flow Builder to fulfill these business requirements efficiently? (Choose two.)

  1. Configure a Record-Triggered Flow optimized for Fast Field Updates (before-save) to populate the Standard_Handling_Fee__c on the triggering record.Cevap
  2. Configure a Record-Triggered Flow optimized for Actions and Related Records (after-save) utilizing an Asynchronous Path to create the Shipping_Manifest__c record and execute the external API callout.Cevap
  3. C
    Configure a single Record-Triggered Flow optimized for Actions and Related Records (after-save) to perform both the Standard_Handling_Fee__c update on the triggering record and the child record creation in the synchronous path.
  4. D
    Configure a Fast Field Updates (before-save) Record-Triggered Flow to query the related Account records using a Get Records element inside a loop to verify credit limits before callout execution.

Cevap

The administrator should use a Record-Triggered Flow optimized for Fast Field Updates (before-save) to set the field value on the triggering record, and a Record-Triggered Flow optimized for Actions and Related Records (after-save) with an Asynchronous Path to create the related record and make the external web service callout.
The correct approach splits the workload based on optimal trigger capabilities. Setting field values on the triggering record before database commit is best handled by a Fast Field Updates (before-save) flow, which executes significantly faster and avoids additional DML operations. Creating child records and invoking external web service callouts requires an Actions and Related Records (after-save) flow; using an asynchronous path ensures external API calls do not block or delay the main transaction execution.

Adım Adım Çözüm

1
Analyze requirement 1: Updating a field on the triggering object record itself.
Identified that Fast Field Updates (before-save flows) are up to 10 times faster than after-save flows when updating the triggering record because they modify the record in memory before database save without firing additional DML statements.
Before-save record-triggered flows are optimized specifically for same-record updates prior to database commit.
2
Analyze requirement 2: Creating a related child record and making an external API callout.
Identified that creating related records requires an Actions and Related Records (after-save) flow. Web service callouts require an Asynchronous Path or scheduled path to prevent transaction timeout and governor limit conflicts.
After-save flows provide access to the record ID and system fields, while asynchronous paths allow external integrations to run out-of-band without blocking the main transaction.
3
Evaluate potential architecture pitfalls against Salesforce governor limits.
Rejected performing same-record updates in after-save flows with explicit DML updates and rejected performing SOQL/DML actions inside loops or before-save callouts.
Enforces order of execution efficiency and governor limit compliance.

Anahtar Kavram

Flow Trigger Selection: Fast Field Updates vs. Actions and Related Records
Bu soruyu puanla

Konular

Flow Types and Triggers

Bu konudan daha fazla soru