Examkin

Question

Difficulty: HardAutomation Tool Selection

An administrator at a global enterprise is designing an automation strategy to satisfy two distinct business requirements while adhering to Salesforce architectural best practices:

1. Automatically calculate and update custom field values on the triggering Account record prior to database commit whenever an Account is created or modified.
2. Submit Opportunities with discount requests exceeding $100,000 through a multi-step authorization hierarchy while enforcing record locking during review.

Which TWO automation tools or configuration options should the administrator select to fulfill these requirements? (Select TWO)

  1. A Record-Triggered Flow optimized for Fast Field Updates (Before-Save) to populate field values on the triggering Account record.Answer
  2. An Approval Process to lock Opportunity records and manage sequential, multi-step authorization requests.Answer
  3. C
    A Record-Triggered Flow configured for Actions and Related Records (After-Save) to update fields on the triggering Account record.
  4. D
    A custom Roll-Up Summary field on the Account object to aggregate Opportunity data connected via a custom Lookup relationship.

Answer

The administrator should select a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) for updating the triggering Account record, and an Approval Process for locking and routing high-value Opportunity discount approvals.
The combination of Fast Field Updates (Before-Save Flow) and Approval Processes directly matches Salesforce best practices. Fast Field Updates allow immediate field manipulation on the triggering record before database storage without incurring extra DML statements. An Approval Process is the dedicated declarative tool designed for multi-tier approvals requiring record locking during review.

Step-by-Step Solution

1
Analyze Requirement 1 for same-record updates prior to save.
Identify that updating fields on the triggering record before database write requires a Before-Save (Fast Field Updates) Record-Triggered Flow to optimize performance and prevent unnecessary DML executions.
Before-save flows run before the record is written to the database, making field modifications directly on the triggering record highly efficient.
2
Analyze Requirement 2 for record locking and multi-step authorization workflows.
Select an Approval Process as the native declarative framework for submission locking and hierarchical multi-step routing.
Approval processes natively support record locking, submission actions, and multi-step approval routing.
3
Evaluate and eliminate incorrect declarative choices.
Reject the After-Save Flow configuration for same-record updates due to DML overhead, and reject Roll-Up Summary fields over Lookup relationships due to platform relationship constraints.
After-save updates on triggering records consume extra governor limits, and roll-up summaries require a Master-Detail relationship.

Key Concept

Salesforce Declarative Automation Selection Guidelines
Rate this question

Topics

Automation Tool Selection

More questions from this topic