ADM-201 · Question #361
The administrator at Ursa Major Solar wants to configure automation that should run when an Account's rating changes along with the following actions: Check if the rating changed from Hot to Cold…
The correct answer is B. One Process Builder that calls one Flow C. One Process Builder. To automate conditional actions when an Account's rating changes (e.g., create Case/send email for Hot to Cold, delete Task for Cold to Hot), both a single Process Builder or a Process Builder that calls one Flow can accomplish these tasks.
Question
The administrator at Ursa Major Solar wants to configure automation that should run when an Account's rating changes along with the following actions:
- Check if the rating changed from Hot to Cold Calculator
o If yes, create a Case . o If yes, send an Email
- Check if the rating changed from Cold to Hot
o If yes, delete a related Task record Which two automation solutions would be able to accomplish these tasks? Choose 2 answers
Options
- AOne Flow
- BOne Process Builder that calls one Flow
- COne Process Builder
- DOne Flow that calls One Process Builder
How the community answered
(41 responses)- A10% (4)
- B73% (30)
- D17% (7)
Why each option
To automate conditional actions when an Account's rating changes (e.g., create Case/send email for Hot to Cold, delete Task for Cold to Hot), both a single Process Builder or a Process Builder that calls one Flow can accomplish these tasks.
While a single Flow (Record-Triggered Flow) is fully capable of accomplishing these tasks, options B and C represent two distinct architectural patterns that leverage Process Builder, which the question expects as specific solutions.
A Process Builder can initiate upon an Account rating change and then invoke a Flow to handle the conditional logic and specific actions (create Case, send Email, delete Task), offering a modular and robust automation solution.
A single Process Builder can directly manage these conditional actions by using multiple criteria nodes to detect the 'Hot to Cold' and 'Cold to Hot' rating changes and then executing the corresponding create record, send email, and delete record actions.
A Flow cannot directly call a Process Builder; automation is typically designed with Process Builder or other events triggering Flows, not the other way around.
Concept tested: Declarative automation for record updates and conditional logic
Source: https://help.salesforce.com/s/articleView?id=sf.process_overview.htm&type=5
Topics
Community Discussion
No community discussion yet for this question.