ADM-201 - Automation (15% of the exam) - Section 7.1
Build automation with Flow Builder, distinguishing record-triggered, screen, scheduled, and autolaunched flows and choosing the right flow type for a requirement.
Build record-triggered, screen, scheduled, and autolaunched flows in Flow Builder, choosing before-save updates for same-record field changes and after-save for related-record actions. Recognise that Flow is Salesforce's strategic automation tool and that Workflow Rules and Process Builder are being retired in favour of it.
Flow BuilderRecord-triggered flowScreen flowBefore-save vs after-saveScheduled flow
Practice question for this objective
lock_openFree sampleAutomationhard
At Kununurra Mining, a new requirement is to validate and standardise a Lead's postcode on the same record every time a Lead is created or updated. The administrator is deciding which automation approach to adopt for this brand-new requirement and wants the strategic, recommended tool rather than a legacy one. Which approach should the administrator choose?
ACreate a Workflow Rule with a field update on the Lead object
BCreate a Process Builder process that updates the Lead's postcode field
CBuild a screen flow that agents run to correct the postcode after saving the Lead
DBuild a before-save record-triggered flow that standardises the postcode on the Leadcheck_circle Correct
Adopt Flow, not Workflow Rules or Process Builder, as the strategic tool for new automation requirements. Salesforce has designated Flow as the go-forward automation platform and is retiring Workflow Rules and Process Builder, so a new same-record update requirement is best met by a before-save record-triggered flow rather than either legacy tool.
Why A is wrong: Workflow Rules can update a field, but they are a legacy tool that Salesforce no longer recommends for new automation, so they are the wrong strategic choice.
Why B is wrong: Process Builder is also legacy and being retired, so building a new automation on it goes against the recommendation to use Flow for new work.
Why C is wrong: A screen flow needs manual agent interaction after the save and cannot enforce standardisation automatically on every create or update as required.
Why D is correct: Flow is the strategic automation tool, and a before-save record-triggered flow standardises a value on the same record efficiently, so it is the correct approach for this new requirement.
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.
Workflow Rules should be preferred because they process records faster than any flow
errorWhy it is wrong: Speed is not the deciding factor and this misrepresents current guidance; Workflow Rules are a retiring tool and are not recommended for new automation.
A screen flow launched from the Case page layout so the agent can populate the field.
errorWhy it is wrong: Tempting because it uses a flow, but wrong: a screen flow needs a user to run it, which contradicts the requirement for no user interaction.
Rebuild the same recalculation logic separately inside a screen flow and inside a record-triggered flow
errorWhy it is wrong: Duplicating the logic in two flows works initially but doubles the maintenance and risks the two copies drifting apart, so it is not the maintainable choice.