ADM-201 - Automation (15% of the exam) - Section 7.2

Configure approval processes, including entry criteria, approval steps, approvers, and the field updates and actions that fire on approval or rejection.

Configure approval processes with entry criteria, ordered approval steps, and assigned approvers, including delegated approvers and queues, to route records such as discounts for sign-off. Define the initial submission, final approval, final rejection, and recall actions - including field updates and email alerts - that fire as a record moves through the process.

Approval processesApproval stepsApproversInitial submission actionsFinal approval actions

Practice question for this objective

Free sampleAutomationmedium

What is the purpose of a final approval action in an approval process, as distinct from a final rejection action?

AIt defines the entry criteria that a record must satisfy before it can be submitted into the approval process at all.
BIt specifies which fields the approver is permitted to edit on the record while the request is still pending.
CIt runs the field updates, email alerts, and other actions that fire once the record has been fully approved. Correct
DIt reassigns the pending request back to the previous step so the earlier approver can reconsider the decision.

Distinguish final approval actions, which fire on full approval, from final rejection actions and from entry criteria. Final approval actions are the field updates, email alerts, tasks, and outbound messages that run only when a record completes every required step, commonly unlocking the record and stamping an approved status, whereas final rejection actions run on a rejected request.

Why A is wrong: Entry criteria control whether submission is allowed, which is a separate setting; final approval actions fire after a decision, so this confuses the two stages.

Why B is wrong: Editable fields for approvers are controlled elsewhere in the step and page layout, not by final actions, so this misplaces the setting.

Why C is correct: Final approval actions execute after the last required approval, and they typically unlock the record and set a status field, distinct from final rejection actions that fire on a rejected request.

Why D is wrong: Routing back to a prior step is rejection-behaviour on a step, not a final approval action, so this describes a different mechanism.

See more ADM-201 practice questions, answers explained.

Exam traps in Automation

Answers that look right on this material and are not. Each one is a distractor from a different question in the ADM-201 bank for this domain.

In a final approval action that runs once every step is approved
Why it is wrong: Final approval actions fire only after the whole process is approved, far too late to set a Pending Approval status at submission time.
As initial submission actions, so that the field update and email are queued the instant the record enters the approval process.
Why it is wrong: Tempting because initial submission actions are genuine approval actions, but they fire when the record is first submitted, long before approval, which contradicts the requirement to act only after final sign-off.
As soon as the record is first submitted into the approval process by the submitter.
Why it is wrong: Actions that fire at submission are the initial submission actions, not the final approval actions. They run before any approver has made a decision.

Examworthy is not affiliated with or endorsed by Salesforce. Original, blueprint-aligned practice material only.