Examkin

Soru

Zorluk: ZorAutomation Tool Selection

A system administrator at a software enterprise needs to automate two separate data management requirements for a custom Subscription object linked to the standard Account object via a lookup relationship:

1. Automatically populate a custom Tier field on the triggering Subscription record prior to database commit whenever a new Subscription is created.
2. Update the parent Account record's Active Contract Status field immediately after a Subscription record is saved with an active status.

Which TWO automation design options adhere strictly to Salesforce architectural best practices for performance and capability limits? (Select TWO.)

  1. Implement a Record-Triggered Flow configured for Fast Field Updates (Before-Save) to evaluate and update the Tier field on the triggering Subscription record.Cevap
  2. Implement a Record-Triggered Flow configured for Actions and Related Records (After-Save) to update the parent Account record's Active Contract Status field.Cevap
  3. C
    Implement a Record-Triggered Flow configured for Actions and Related Records (After-Save) to populate the Tier field on the triggering Subscription record.
  4. D
    Create a Roll-Up Summary field on the Account object to automatically summarize active Subscription records connected via the lookup relationship.

Cevap

The correct architecture requires a Record-Triggered Flow configured for Fast Field Updates (Before-Save) for same-record updates, and a Record-Triggered Flow configured for Actions and Related Records (After-Save) for cross-object updates.
For same-record field modifications, Salesforce best practice dictates using a Record-Triggered Flow optimized for Fast Field Updates (Before-Save), as it modifies record values in memory prior to database storage without generating additional DML statements. For updates involving related objects (such as updating the parent Account), an Actions and Related Records (After-Save) Record-Triggered Flow must be used.

Adım Adım Çözüm

1
Analyze same-record field update requirements
Updating fields on the record that launched the flow must use a Fast Field Update (Before-Save) flow to execute before database save and prevent redundant DML operations.
Before-save flows run faster and eliminate additional save execution loops.
2
Analyze related-record update requirements
Updating fields on a parent or related record requires an Actions and Related Records (After-Save) flow because access to related records and system variables requires post-save context.
Cross-object record updates cannot take place in a before-save trigger context.
3
Evaluate relationship constraints for declarative aggregation
Declarative roll-up summary fields cannot be created on lookup relationships.
Salesforce standard Roll-Up Summary fields strictly require a Master-Detail relationship.

Anahtar Kavram

Selecting optimal record-triggered flow trigger timing and declarative tool limits for related records
Bu soruyu puanla

Konular

Automation Tool Selection

Bu konudan daha fazla soru