SF-Admin Automation Practice Question
A Salesforce administrator is asked to automate a multi-step approval process for discount requests on Opportunity. The process must route to different approvers based on the discount percentage, allow approvers to reject with comments, and update the Opportunity stage upon final approval. The administrator wants to build this declaratively without code. Which tool should be used?
⚠ Common exam trap
The trap here is assuming Flow can replace Approval Processes because it can submit for approval, when the native approver routing, rejection comments, and audit trail are only fully provided by Approval Processes.
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
✓
Approval Process with steps and approval actions.
Approval Processes are the declarative Salesforce feature designed specifically for routing records to approvers, supporting multiple steps with criteria-based approver selection, rejection with comments, and post-approval actions like field updates. The other options either lack native approval mechanics or require custom development to approximate them, making Approval Processes the correct choice for this requirement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Einstein Next Best Action with a recommendation strategy.
Why it's wrong here
Einstein Next Best Action is designed to surface recommendations to users based on strategies and business rules; it does not manage approval workflows, approver assignments, or record locking. It cannot enforce sequential approvals or capture rejection comments as part of an auditable process. This tool is inappropriate for approval routing.
- ✓
Approval Process with steps and approval actions.
Why this is correct
Approval Processes are purpose-built for sequential or parallel approval routing, support multiple steps with different approver assignments based on record criteria, allow rejections with comments, and can execute approval actions such as field updates and email alerts. This matches every requirement declaratively and is the standard Salesforce tool for approval routing without code.
- ✗
Record-Triggered Flow with a decision element and an approval action.
Why it's wrong here
While Flow can submit records for approval and orchestrate complex logic, it does not natively provide the approver inbox, rejection-with-comments UI, or multi-step approver routing that Approval Processes deliver out of the box. Building equivalent functionality in Flow would require significant custom work and would not replicate the standard approval interface users expect.
- ✗
Scheduled-Triggered Flow that checks discount fields nightly and assigns tasks to approvers.
Why it's wrong here
A scheduled flow cannot provide real-time approval routing, and using tasks as a proxy for approvals loses the audit trail, rejection comments, and locking behavior of the standard approval engine. Nightly processing also delays the approval cycle, which is unacceptable for time-sensitive discount requests. This approach does not satisfy the routing or rejection requirements.
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.