SF-Admin Automation Practice Question
Universal Containers has a Record-Triggered Flow on the Case object that runs when a Case is created or updated and sends a notification email to the assigned owner. During testing, the administrator notices the flow sends duplicate emails when a user edits a Case twice within a few seconds. The administrator needs the flow to run only when the Case's Priority field actually changes value. Which configuration should the administrator apply?
⚠ Common exam trap
The trap here is assuming a Decision element can detect that a field changed, when it only evaluates the record's current values and cannot see the pre-save state.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set the Start element to run only when a record is updated, and add an entry condition comparing the PriorValue of Priority to its current value.
Record-Triggered Flows that start on create or update fire on every qualifying save, so unrelated edits can re-trigger notifications. Restricting the Start element to updates and adding an entry condition that compares the prior stored value of Priority against the incoming value ensures the automation runs only when that specific field is genuinely modified, which removes the duplicate sends without blocking other edits.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a validation rule on the Case object that blocks saves when Priority is unchanged, forcing users to modify the field before the record can be saved.
Why it's wrong here
A validation rule prevents the record from being saved at all, which blocks legitimate edits to other fields such as Status or Description. This harms normal user work instead of scoping the flow, and it cannot distinguish which automation should run based on a field-level change.
- ✗
Configure the flow to run asynchronously so that rapid successive edits are consolidated into a single scheduled interview before the notification is sent.
Why it's wrong here
Running a Record-Triggered Flow asynchronously defers execution to a future transaction but does not deduplicate or coalesce separate save events. Two edits still produce two asynchronous interviews, so two emails are still sent; asynchrony affects timing and governor limits, not change detection.
- ✓
Set the Start element to run only when a record is updated, and add an entry condition comparing the PriorValue of Priority to its current value.
Why this is correct
Entry conditions on an update-triggered Start element can reference $Record__Prior, which exposes the field values stored in the database before the save. Comparing Priority's prior value to its current value makes the flow fire only on a genuine change, eliminating the duplicate sends caused by unrelated edits that leave Priority untouched.
- ✗
Add a Decision element immediately after the Start element that checks whether the record's Priority equals High, and route non-matching records to an end element.
Why it's wrong here
A Decision element evaluates the record as it exists after the change, not what changed. If a Case already has Priority set to High, every subsequent edit still passes the check and the notification fires again, so the duplicate-email problem persists rather than being solved by this routing logic.
About these practice questions
One of 202 original SF-Admin practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Admin practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Admin exam.