Examkin

Soru

Zorluk: OrtaAutomation Tool Selection

A Salesforce Administrator at a telecommunications company needs to design an automated solution on the standard Case object to meet two distinct business requirements:
1. Update target fields on the triggering Case record immediately before it is committed to the database to ensure optimal system performance.
2. Automatically create a child Task record assigned to the case owner and trigger an email notification when a high-priority Case is created.

Which TWO declarative automation solutions should the administrator implement to fulfill these requirements? (Select TWO)

  1. A Fast Field Updates (Before-Save) Record-Triggered Flow to modify field values directly on the triggering Case record.Cevap
  2. An Actions and Related Records (After-Save) Record-Triggered Flow to create the child Task record and execute the email alert.Cevap
  3. C
    A Fast Field Updates (Before-Save) Record-Triggered Flow to create the child Task record and dispatch the email alert.
  4. D
    A Roll-Up Summary field on the parent Account object linked via a standard Lookup relationship to calculate total open cases for routing.

Cevap

The administrator should implement a Fast Field Updates (Before-Save) Record-Triggered Flow for same-record field updates and an Actions and Related Records (After-Save) Record-Triggered Flow to create the child Task and send the email notification.
The correct combination requires choosing the right Record-Triggered Flow execution optimization. Fast Field Updates (Before-Save) flows are explicitly designed for updating fields on the triggering record without incurring additional database write operations. Actions and Related Records (After-Save) flows run after the primary record save, providing access to system fields like CreatedDate/Id and granting capability to create related objects (such as Task) and execute external actions (such as Email Alerts).

Adım Adım Çözüm

1
Analyze requirement 1 (same-record field updates prior to database commit).
Identify that Fast Field Updates (Before-Save Record-Triggered Flow) are designed for updating fields on the triggering record before it is saved, offering up to 10x performance gains.
Before-save flows run before validation rules and database save operations, avoiding unnecessary recursion.
2
Analyze requirement 2 (creating a child Task record and sending an email notification).
Identify that Actions and Related Records (After-Save Record-Triggered Flow) must be used when creating records on other objects or performing external side effects.
The triggering record must have a system-assigned ID and exist in the database before related child records can link to it or actions can reference it.
3
Evaluate alternative declarative options for validity and limitations.
Reject creating related records in a before-save flow and reject roll-up summary fields over lookup relationships.
Before-save flows lack DML support for creating non-triggering records, and native roll-up summary fields require master-detail relationships.

Anahtar Kavram

Selecting between Before-Save (Fast Field Updates) and After-Save (Actions and Related Records) Record-Triggered Flows based on trigger execution timing and record modification context.
Bu soruyu puanla

Konular

Automation Tool Selection

Bu konudan daha fazla soru