Courseiva
Automation →mediumMultiple Select

SF-Admin Automation Practice Question

A sales manager at Get Cloudy Consulting wants a Record-Triggered Flow to update the 'Next Step' field on an Opportunity and also create a follow-up Task whenever the Opportunity stage changes to 'Negotiation'. The administrator is configuring the flow's start conditions. Which two considerations should the administrator keep in mind when designing this flow? (Choose two.)

⚠ Common exam trap

The trap here is assuming that a single before-save flow can both update the triggering record and create related records, when DML on other records is not allowed in before-save flows.

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

✓

The flow must use an after-save configuration to create a related Task record.

A before-save flow can update fields on the triggering Opportunity using the $Record variable without a separate Update Records element, which is efficient. However, creating a Task requires DML on a different record, so an after-save flow is necessary. These two considerations guide the administrator to design a flow that updates the Opportunity in a before-save context and creates the Task in an after-save context, or to use a single after-save flow for both actions.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    The flow must use an after-save configuration to create a related Task record.

    Why this is correct

    Creating a Task is a DML operation on a different record, which requires an after-save flow. Before-save flows cannot perform DML on other records; they can only modify the triggering record. Therefore, to create a follow-up Task, the administrator must use an after-save flow. This is a key design consideration for the described automation.

  • ✗

    The flow can create the Task in a before-save flow if the Task is related to the Opportunity.

    Why it's wrong here

    Even if the Task is related to the Opportunity, creating it requires a DML operation on a different record, which is not allowed in a before-save flow. Before-save flows are limited to modifying the triggering record itself. The administrator must use an after-save flow to create the Task, regardless of the relationship.

  • ✗

    The flow must use a scheduled path to create the Task at a later time.

    Why it's wrong here

    A scheduled path is used to execute flow logic at a future time, not immediately when the record changes. The requirement is to create a follow-up Task when the stage changes to Negotiation, which implies immediate action. Using a scheduled path would delay the Task creation and is not necessary unless a time delay is explicitly required.

  • ✓

    The flow can update the triggering Opportunity record without using a separate Update Records element if it is a before-save flow.

    Why this is correct

    In a before-save Record-Triggered Flow, the flow can directly modify fields on the triggering record using the $Record variable, and those changes are saved automatically without an Update Records element. This is the recommended approach for updating fields on the same record because it is more efficient and avoids additional DML. It aligns with the requirement to update the Next Step field on the Opportunity.

  • ✗

    The flow can update the Opportunity and create the Task in a single before-save flow.

    Why it's wrong here

    A before-save flow cannot create records because it does not support DML operations on records other than the triggering record. Attempting to create a Task in a before-save flow would result in an error or require an after-save flow instead. The administrator must separate the update of the triggering record from the creation of related records, typically using an after-save flow for the Task.

About these practice questions

This SF-Admin question is part of Courseiva's 202-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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.