SF-Admin Automation Practice Question
Universal Containers wants to build a Screen Flow that collects a Case's priority and description, then creates a Case record and immediately sends a confirmation email. The administrator must ensure the Flow can perform both operations in a single interview. (Choose two.)
⚠ Common exam trap
The trap here is reaching for a Record-Triggered Flow to insert the record, when a Screen Flow can create records directly with a Create Records element.
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
✓
Use a Create Records element to insert the Case record.
A Screen Flow can both create records and send email within one interview. The Create Records element inserts the Case and returns its Id, and the Send Email core action then sends a confirmation using that Id. Together they satisfy the requirement without Apex or a separate trigger-based Flow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a Wait element configured to resume after one minute, then send the email.
Why it's wrong here
The Wait element pauses an interview and is intended for asynchronous timing, but it does not create the Case record. Adding a wait would delay the confirmation without satisfying the insert requirement, and it introduces unnecessary complexity. The Flow still needs a Create Records element to persist the Case.
- ✗
Use a Post to Chatter action to notify the support team instead of sending email.
Why it's wrong here
Posting to Chatter creates a feed item, not an email, so it does not meet the requirement of sending a confirmation email. While it can notify users, the recipient experience and channel differ from email. This option changes the requested behavior rather than implementing it.
- ✗
Use a Record-Triggered Flow with a before-save update to insert the Case.
Why it's wrong here
A Record-Triggered Flow requires an existing record event to fire; it cannot be launched interactively by a user to collect screen input. Mixing a Screen Flow with a Record-Triggered Flow is not how a single interview both gathers input and inserts a record. The Screen Flow itself should perform the create.
- ✓
Use a Create Records element to insert the Case record.
Why this is correct
The Create Records element is the standard Flow element for inserting new records. It can create one or many records and stores the resulting record Id in a variable. In a Screen Flow, this element runs after the user submits the screen, creating the Case before the confirmation email is sent, which satisfies the requirement.
- ✓
Use an Action element referencing the standard Send Email action.
Why this is correct
The Send Email core action allows a Flow to send an email to specified recipients with a subject and body, and it can reference variables from earlier elements. Placing it after the Create Records element lets the Flow include the new Case number in the confirmation. This is the supported way to send email from a Flow without Apex.
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 →
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.