Process Automation

Choosing and combining declarative automation tools, Flow design and limits, approval processes, troubleshooting automation and the order of execution (20% of exam).

5 minutes 5 Questions

Process Automation is a core domain of the Salesforce Certified Platform Administrator II exam, testing your ability to choose and configure declarative tools that automate business logic without code. The central tool today is Flow Builder. Flows come in several types: Record-Triggered Flows run w…

Concepts covered
Troubleshooting Automation with Debug LogsBulkification and Governor Limits in FlowsGet Records, Loops, Collections and Decisions in FlowFlow Trigger Explorer and Trigger OrderAutolaunched Flows and SubflowsBefore-Save Versus After-Save Record-Triggered FlowsTroubleshooting Approval Processes and Record LockingChoosing the Right Declarative Automation ToolEmail Alerts and Outbound MessagesEntry Conditions and Run-When-Updated CriteriaFormula Fields and Validation Rules in Automation DesignScheduled Paths and Schedule-Triggered FlowsApproval Processes: Steps, Approvers and ActionsPlatform Event-Triggered FlowsScreen FlowsDebugging Flows and Flow Error EmailsOrder of ExecutionMigrating Workflow Rules and Process Builder to FlowMulti-Step and Parallel ApprovalsFault Paths and Error Handling in Flows
Test mode:
Start practice test

Admin II - Process Automation Example Questions

Test your knowledge of Process Automation

Question 1

Cloud Kicks uses an approval process for large discount requests. In the second step, the finance manager and the legal manager must review each request at the same time. The request may move to the final VP step only after both of them approve, and either can approve first. How should the administrator configure the second step?

Correct Answer: Add both managers to one step set to require unanimous approval

Adding both managers as approvers in a single step and requiring unanimous approval sends the request to both at the same time, lets either respond first, and advances the record to the VP step only after both approve.
Accepting the first response would move the request forward after only one manager approves. Assigning the step to a queue also needs just one member to act, so both reviews are not guaranteed. Two sequential steps force a fixed order and stop the managers from reviewing in parallel, which contradicts the requirement that either can approve first.
Key concept: multiple approvers in one approval step with the unanimous approval setting for parallel review.

Question 2

At Cloud Kicks, a record-triggered flow on Opportunity sends an email alert to the finance team. Its entry condition is Stage equals Closed Won, and it is set to run every time a record is updated and meets the condition requirements. Finance now gets repeat emails whenever a sales rep edits any field on an opportunity that is already Closed Won. The email must still go out once, at the moment the deal closes. What should the administrator do?

Correct Answer: Set the flow to run only when the record is updated to meet the conditions

Choosing "Only when a record is updated to meet the condition requirements" makes the flow fire only when Stage changes from something else to Closed Won. Later edits to an already Closed Won opportunity no longer trigger the email, so finance gets exactly one alert when the deal closes.
A before-save flow cannot send email alerts, and it would still evaluate on every update. Triggering on create or update widens the scope and still fires on repeat edits. A validation rule blocking edits would stop legitimate post-close updates and does not fix the trigger logic.
Key concept: record-triggered flow entry criteria, specifically running only when a record is updated to meet the conditions.

Question 3

Universal Containers has two record-triggered flows on Opportunity that run when a record is updated, both configured for actions and related records. The approval flow reads a discount tier that the discount flow writes to a related record. Users report that the approval flow sometimes runs first and works from stale values. The administrator needs the discount flow to run first every time. What should the administrator do?

Correct Answer: Open Flow Trigger Explorer and give the discount flow a lower trigger order

Flow Trigger Explorer lets the administrator set a Trigger Order value from 1 to 2,000 on record-triggered flows that share an object, timing, and trigger type. Flows with lower values run first, so giving the discount flow the lower value makes it run before the approval flow every time.
Giving the discount flow a higher value would make it run after the approval flow. A fast field update flow runs before the save, which is earlier than the discount flow, not later. It also cannot update related records. Renaming the API name only affects the tiebreaker for flows with equal or unset trigger orders, so it is not the intended control.
Key concept: record-triggered flow trigger order.

More Process Automation questions
592 questions (total)
Practice 100 questions
One session at a time, always new questions