ADM-201 domain - 15% of the exam

Automation

Automation is 15% of the ADM-201 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

45
Practice questions
2
Objectives
22
Medium
23
Hard

Where people go wrong

  • Giving before-save flows after-save abilities

    The wrong answers have a before-save flow create a related Task or child record, or send an email alert, or they reject it only on speed or trigger event. A before-save flow can only set fields on the triggering record. Creating related records, sending email and anything that needs the committed Id belong in an after-save record-triggered flow, which runs once the record is saved.

    See it in a sample question
  • Using a record-triggered flow for a timed sweep

    The wrong answers pick a record-triggered, screen or autolaunched flow for a requirement that runs across many records at a set time with no user. A record-triggered flow fires only when a record is saved, so records whose date arrives without any edit never start it. A scheduled flow has a start time and frequency and filters the records it processes.

    See it in a sample question
  • Choosing a legacy tool for new automation

    The wrong answers reach for Workflow Rules or Process Builder because they can update a field or create a related record. Both are legacy tools that Salesforce is retiring, so neither is the recommended path for a new requirement. Flow is the strategic automation tool, and a same-record field change on create or update is built as a before-save record-triggered flow.

    See it in a sample question
  • Placing an approval action at the wrong point

    The wrong answers attach an action to the wrong stage of an approval process. Initial submission actions run the moment the record is submitted, so a field update there sets Status to Pending Approval, and the process locks the record on submission by itself. Final approval actions run only after every step is approved. Final rejection actions run on rejection, and recall actions run only when the submitter withdraws the request.

    See it in a sample question
  • Hard-coding or guessing the approver

    The wrong answers name one user, let the submitter pick manually, or use a queue when the requirement is the submitter's own manager. Automatic assignment through the Manager field on the submitter's user record resolves a different approver per submitter. A queue fits a shared pool where any member can take ownership, and a public group is not a valid approver type.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleAutomationhard

A record-triggered flow must create a related task and send an email whenever an Opportunity is closed. Why should this run after save rather than before save?

  • ABefore-save flows cannot create related records or send emails, which only after-save flows support Correct
  • BBefore-save flows run too slowly to complete the additional work within the save window
  • CBefore-save flows always require a screen element, which cannot be shown during a save
  • DBefore-save flows run only on record creation and would miss the Opportunity being edited to closed
Before-save flows can only update the triggering record; creating related records or sending email requires an after-save flow. The before-save context exists purely to set fields on the record being saved before it commits, so it exposes no elements for related-record DML or actions like email; those require the record to be committed, which is the after-save context.

Why A is correct: Before-save flows are limited to updating the triggering record and cannot perform actions such as creating related records, sending email, or calling other automation, all of which require the after-save context.

Why B is wrong: Before-save flows are actually the faster path; the reason they are unsuitable here is functional rather than a matter of speed, so this misstates the constraint.

Why C is wrong: No record-triggered flow, before or after save, can contain a screen element, so requiring a screen is not the distinction; this misdescribes both flow behaviour.

Why D is wrong: Before-save flows can be configured to run on create, on update, or both, so the trigger event is not the limitation; the true limitation is the actions they may perform.

Free sampleAutomationhard

An administrator needs an automation that runs each night and processes every Opportunity that closed during that day. Which flow type fits this requirement?

  • AA record-triggered flow configured to run whenever an Opportunity record is updated by a user.
  • BA screen flow embedded on the Opportunity home page for an administrator to run manually.
  • CAn autolaunched flow that is invoked in real time by a platform event message.
  • DA scheduled flow with a defined start time and frequency that filters the records it runs against. Correct
A scheduled flow is the flow type that runs automatically at a set time and frequency over a filtered set of records. A scheduled flow is defined with a start date, time, and frequency, and can specify an object with filter conditions so that it iterates over the matching records at each run, which is exactly what a recurring nightly batch job requires.

Why A is wrong: Tempting because Opportunities do change, but wrong: a record-triggered flow reacts to each individual save, not to a nightly batch run over a set of records at a fixed time.

Why B is wrong: Tempting as a way to process records, but wrong: a screen flow needs a user to launch and step through it, so it cannot run unattended on a nightly timetable.

Why C is wrong: Tempting because autolaunched flows run without a user, but wrong: this fires on an event message rather than on a nightly clock, so it does not meet the scheduled batch requirement.

Why D is correct: Correct: a scheduled flow runs on a set schedule and can be given entry conditions so it processes only the records that match, such as Opportunities closed that day.

Free sampleAutomationhard

At Onslow Freight, whenever a Shipment record is created or edited, the administrator must set a Total Weight field on that same record by adding two of its own number fields together. The calculation must run before the record is committed so no extra update is needed. Which automation is the best fit for this requirement?

  • AA Workflow Rule with a field update on the Shipment object, evaluated when a record is created and every time it is edited.
  • BAn after-save record-triggered flow that updates the same Shipment record with the calculated Total Weight.
  • CA scheduled flow that runs each hour to recalculate Total Weight on Shipment records edited since the last run.
  • DA before-save record-triggered flow on Shipment that assigns Total Weight in the same transaction the record is saved. Correct
Choose a before-save record-triggered flow for same-record field updates that must run efficiently as the record is saved. Before-save record-triggered flows execute during the save transaction and write to the triggering record directly, so no second DML statement or separate update is generated, which is the fastest way to set fields on the same record.

Why A is wrong: Field updates on the same record are the classic Workflow Rule use, which makes this tempting, but Workflow Rules are retired for new automation and Flow is the strategic tool, so this is the wrong choice for a new requirement.

Why B is wrong: An after-save flow can update the triggering record, but doing so issues an additional DML on the same record, which is exactly the extra update the requirement wants to avoid, so before-save is preferred here.

Why C is wrong: A scheduled flow would eventually populate the field, but it runs asynchronously on a batch rather than before the record is committed, so the value is stale between runs and the requirement is not met.

Why D is correct: Before-save record-triggered flows set fields on the triggering record within the same save, with no extra DML, which meets the requirement to run before commit efficiently.

Free sampleAutomationmedium

At Busselton Media, when a Campaign Budget record receives its final approval, the administrator needs the Approved checkbox ticked and an email sent to the requester confirming the outcome. Which combination of approval process actions meets this requirement?

  • AA field update and an email alert placed in the initial submission actions
  • BA field update and an email alert placed in the final approval actions Correct
  • CA field update in the first step's rejection actions plus a task in the final approval actions
  • DA field update in the final approval actions and an email alert in the recall actions
Final approval actions run only after every step is approved, making them the place for approval field updates and notifications. Final approval actions fire once a record has been approved through all steps, so placing both the Approved field update and the confirmation email alert there ensures they run exactly when the budget is fully approved.

Why A is wrong: Initial submission actions run at submission, so the checkbox would be ticked and the email sent before any approver had actually approved the budget.

Why B is correct: Final approval actions execute only after the record clears every step, so a field update ticks the Approved checkbox and an email alert notifies the requester precisely on final approval.

Why C is wrong: Rejection actions fire when a record is rejected, so tying the Approved update to a rejection would set it at exactly the wrong time.

Why D is wrong: Recall actions fire only when a submitter withdraws the request, so the confirmation email would never be sent on approval and would instead trigger on recall.

Free sampleAutomationmedium

Which approver setting on an approval step routes each request to the submitter's manager without naming a specific person?

  • ARequire the submitter to choose an approver manually each time they submit the record for approval.
  • BAutomatically assign to one specific named user who is selected at the time the approval step is built.
  • CAutomatically assign to approvers using a hierarchy field such as the standard Manager field on the submitter's user record. Correct
  • DAutomatically assign using a custom related-user lookup field that must be populated on the record itself.
Assigning an approval step using a user hierarchy field such as Manager routes each request to the submitter's manager dynamically. Approval steps can assign approvers automatically from a hierarchy field on the user record, such as the standard Manager field. Salesforce reads that field on the submitter's user record at run time, so the request always follows the current reporting line without naming a fixed user.

Why A is wrong: Manual selection lets the submitter pick anyone, so it does not guarantee the manager receives the request. It relies on the submitter making the right choice every time.

Why B is wrong: A static named approver is a valid option but sends every request to the same person regardless of who submits, so it does not follow each submitter's own manager.

Why C is correct: Correct. Choosing automatic assignment based on a user hierarchy field sends the request to whoever is named in that field, so it follows the submitter's manager dynamically without hardcoding a user.

Why D is wrong: A related user field on the record can route dynamically, which makes it tempting, but it draws from a field on the record rather than the submitter's Manager field, so it does not represent the reporting manager.

Other domains in this exam

See also the ADM-201 cert hub, the study guide, and the cheat sheet.

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