SF-Admin Automation — Timed 25 Questions

Question 1

An administrator needs to ensure that a Flow only executes when a Lead record is created and the 'Rating' field is set to 'Hot'. Which TWO conditions should the administrator configure in the Flow trigger?

25 minute time limit — choose an answer to begin.

Accepted Answer

Set the trigger to run when a record is created.. Configuring entry conditions directly on the Flow trigger is a best practice to reduce unnecessary resource consumption. By setting the trigger to only fire when the record is created and the Rating field equals Hot, the administrator avoids running the flow on every save operation. This improves system performance, prevents unnecessary CPU time usage, and keeps the flow logic clean by eliminating the need for an initial Decision element.

Answer

Use a Decision element to check if Rating equals Hot.

Answer

Set the trigger to run on create or update.

Answer

Set the entry condition to Lead Source Equals Web.

Question 2

Which THREE actions can a Record-Triggered Flow perform before a record is saved to the database?

Accepted Answer

Update fields on the triggering record.. Before-save Record-Triggered Flows are highly performant because they run in the 'Fast Field Update' path, which executes before the database write operation. This allows administrators to update fields on the triggering record with minimal impact on execution time and without triggering additional system processes. These flows are limited to field updates on the triggering record, making them ideal for setting default values, data validation, and ensuring consistent field formatting upon record creation.

Answer

Send an email alert.

Answer

Create a related record.

Question 3

An administrator has a flow that updates a custom field on the Account record. Which debug setting should the administrator enable to see the values of the record fields before and after the flow executes?

Accepted Answer

Use Current Record. When debugging, the 'Use Current Record' option allows administrators to run the flow against an existing record and view the 'Before' and 'After' snapshots. This is critical for troubleshooting logic, as it highlights exactly how the flow modifies data. By inspecting these values in the debug log, the administrator can verify if the field assignment logic is accurate and whether the flow behaves as expected in a realistic environment.

Answer

Debug as Another User

Answer

Show Governor Limits

Answer

Run as Rollback Mode

Question 4

Universal Containers has a Record-Triggered Flow on Case that sends an email to the customer when a Case is escalated. The flow is after-save and uses an email action. During testing, the administrator notices that the email is sent even when the escalation checkbox is unchecked and then re-checked in the same transaction. The administrator wants to ensure the email is sent only when the escalation flag changes from false to true. What should the administrator do?

Accepted Answer

Use the PRIORVALUE() function in the entry criteria to compare the old and new values of the escalation field.. The duplicate email occurs because the flow runs on any update where the escalation field is true, including updates that do not change the field. Using PRIORVALUE() in the entry criteria to require a false-to-true transition ensures the flow fires only when the field is actually escalated. This is the correct declarative pattern for transition-based automation.

Answer

Add a decision element after the trigger that checks if the escalation field is true.

Answer

Change the flow to run before-save and use a field update to set the escalation flag.

Answer

Add a fault path to the email action that logs errors and retries the email only once.

Question 5

A Salesforce administrator needs to automate the creation of a follow-up Task whenever a Lead is converted. The Task should be assigned to the Lead owner and due three days after conversion. The administrator wants to use a declarative tool that runs immediately after the conversion. Which tool should be used?

Accepted Answer

Record-Triggered Flow on Lead with a create records element.. A Record-Triggered Flow on Lead is the correct declarative tool because it can run after a Lead is converted and create a Task with a due date and owner assignment. It executes immediately in the same transaction, meeting the timing requirement, and is the current best practice for this type of automation. Legacy tools like Process Builder and Workflow Rules are not suitable for new development.

Answer

Scheduled-Triggered Flow that runs daily and queries converted Leads.

Answer

Process Builder with a scheduled action.

Answer

Workflow Rule with a time-dependent action.

Question 6

AW Computing's sales team uses a custom object 'Invoice__c' with a lookup to Account. When an Invoice's 'Status__c' is changed to 'Paid', the administrator wants to automatically update the related Account's 'Last_Paid_Date__c' to today's date. The update should only occur when the status changes to 'Paid' and must not trigger any other automation on the Account. Which automation tool should the administrator use?

Accepted Answer

Record-Triggered Flow on Invoice__c, after-save, with a condition checking ISCHANGED(Status__c) && Status__c = 'Paid'.. A record-triggered flow on Invoice__c can run after save, check that the status changed to Paid, and update the related Account. This provides immediate, condition-specific automation without code and avoids unintended updates on other records. Process Builder and Workflow Rules are legacy and cannot meet the related-record update and ISCHANGED condition requirements.

Answer

Scheduled Flow that runs nightly to find all Invoices with Status__c = 'Paid' and updates the related Account's Last_Paid_Date__c.

Answer

Workflow Rule on Invoice__c with a field update on Account.

Answer

Process Builder on Invoice__c with a criteria node for Status__c = 'Paid' and an immediate action to update the Account.

Question 7

Northern Trail Outfitters has a Record-Triggered Flow on the Opportunity object that is configured to run only when a record is updated and the StageName field changes to 'Closed Won'. The administrator needs the flow to also send a confirmation email to the opportunity owner after the record is saved. Which Flow element should the administrator use to send the email after the record is committed to the database?

Accepted Answer

An Email Alert action from the Core suite, placed in a Run Asynchronously path after the Update Records element.. The requirement is to send an email after the record is saved. The Send Email action in a Record-Triggered Flow, when placed in an asynchronous path after the Update Records element, ensures the email is sent after the transaction commits. This avoids sending premature notifications and aligns with the after-save behavior. The other options either send the email too early or use mechanisms that do not actually send an email.

Answer

A Create Records element that creates an EmailMessage record.

Answer

A Post to Chatter action configured to mention the opportunity owner.

Answer

A Send Email action placed before the Update Records element in the immediate path.

Question 8

AW Computing's sales team wants a visual, guided process that prompts reps to collect required qualification details after a Lead is created, allowing them to enter data step by step before the record is saved. Which automation tool should the administrator configure?

Accepted Answer

Screen Flow. A Screen Flow is the correct tool because it delivers an interactive, multi-step interface that collects user input before saving data. The sales team needs reps to enter qualification details in a guided manner after a Lead is created, and only Screen Flows combine visual screens with the ability to create or update records. Background and approval tools cannot present the required interactive prompts.

Answer

Record-Triggered Flow

Answer

Scheduled-Triggered Flow

Answer

Approval Process

Question 9

Universal Containers has a Record-Triggered Flow on the Case object that runs when a Case is created. The flow uses a Decision element to check if the Case Origin is 'Phone' and then creates a Task for the case owner. The administrator notices that the Task is sometimes created multiple times for the same Case. What is the most likely cause of this issue?

Accepted Answer

The flow is configured to run on create and update, causing it to run again when the Task is created.. The most likely cause of duplicate Tasks is that the Record-Triggered Flow is configured to run on both create and update. When the Task is created, if it causes an update to the Case (e.g., through a roll-up summary or a separate process), the flow runs again, creating another Task. This recursive behavior can be mitigated by using entry criteria to only run on create or by adding a condition to check if a Task already exists.

Answer

The flow uses a Get Records element that retrieves multiple Case records.

Answer

The flow is configured to run in system context without sharing, causing it to bypass duplicate rules.

Answer

The flow has a scheduled path that runs every time the Case is updated.

Question 10

Northern Trail Outfitters uses a Record-Triggered Flow on the Opportunity object that runs after save when an Opportunity is closed won. The flow creates a contract record and sends a notification. During testing, the administrator notices that the flow sometimes fails to create the contract due to a validation rule on the Contract object. The administrator wants to handle this error gracefully and allow the flow to continue processing other records. Which TWO actions should the administrator take? (Choose two.)

Accepted Answer

Add a fault path to the Create Records element and use an Assignment element to log the error to a custom object.. To handle errors gracefully, the administrator can add a fault path to catch the validation rule error and log it, or use a Decision element to check conditions before creating the contract. Both approaches prevent the flow from failing and allow it to continue. Bypassing validation rules or deactivating them is not appropriate and can lead to data quality issues.

Answer

Set the flow to run asynchronously to allow the validation rule to be ignored.

Answer

Deactivate the validation rule on the Contract object.

Answer

Configure the flow to run in system context without sharing to bypass the validation rule.

Question 11

Cloud Kicks has a Record-Triggered Flow on the Account object that updates a custom field 'Last_Activity_Date__c' whenever a related Task is created. The administrator wants to ensure the flow runs only when the Task is created and not when other related records are created. Which configuration should the administrator use?

Accepted Answer

Configure the flow to run on the Task object with a trigger on create, and use a Get Records element to update the related Account.. The requirement is to run the flow only when a Task is created. Placing the Record-Triggered Flow on the Task object with a create trigger ensures that it runs only on Task creation. The flow can then update the related Account using a Get Records element. This is the most direct and efficient configuration. The other options either run on the wrong object or include unnecessary triggers.

Answer

Configure the flow on the Task object with a trigger on create and update, and use a Decision element to check if the Task is new.

Answer

Configure the flow on the Account object with a trigger on create or update, and use a Get Records element to check for new Tasks.

Answer

Configure the flow on the Account object with a trigger on update, and use a Decision element to check if the update is due to a Task creation.

Question 12

DreamHouse Realty has a Record-Triggered Flow on the Opportunity object that fires when a Stage changes to 'Closed Won'. The Flow uses a Get Records element to retrieve the primary Contact Role and then sends an email to that Contact. During testing, the Flow fails on Opportunities where no Contact Role exists. Which element should the administrator add to handle this scenario without failing the transaction?

Accepted Answer

Add a Decision element after the Get Records element that checks whether the record variable is null.. A Decision element is the correct way to branch on whether a Get Records element returned a record. Because Get Records returns null rather than faulting when nothing matches, the Flow must explicitly test the variable before using it. Adding the Decision after the lookup lets the Flow skip the email action when no Contact Role exists, preventing the runtime error.

Answer

Add an Assignment element that sets a default Contact Id before the Get Records element runs.

Answer

Add a Fault Path on the Get Records element that sends an email to the administrator.

Answer

Change the Get Records element to 'Store All Records' and loop through the collection.

Question 13

An administrator at Ursa Major Solar is debugging a Record-Triggered Flow that updates a custom field on the Account record. The administrator wants to see the exact values of the flow variables and the record fields at each step of the execution. Which debug option should the administrator enable?

Accepted Answer

Enable 'Debug' mode in the Flow Builder and run the flow.. The Flow Builder's Debug feature allows administrators to run a flow and inspect variable values and record fields at each step. By enabling Debug mode and running the flow, the administrator can see exactly how data changes throughout execution. This provides the detailed visibility needed to troubleshoot the custom field update on the Account record.

Answer

Set the flow to run in system context and review the debug output.

Answer

Enable debug logs for the user.

Answer

Use the Flow Debugger with 'Show details' enabled.

Question 14

Northern Trail Outfitters has a Record-Triggered Flow on the Case object that runs before save when a Case is created. The Flow updates the Case Owner to a queue based on the Case Origin. After deployment, users report that the Case is still being assigned to the default owner, and the debug log shows the Flow executed successfully. What is the most likely cause?

Accepted Answer

The Flow's Update Records element is configured to update the triggering record, but the OwnerId assignment is being overwritten by a separate assignment rule that runs after the Flow.. Salesforce's order of execution runs before-save Flows before assignment rules. When both a Flow and an active Case assignment rule set the owner, the assignment rule executes later and wins. Because the Flow itself completes without error, the debug log looks clean while the final OwnerId reflects the assignment rule. Deactivating or adjusting the assignment rule restores the Flow's intended owner assignment.

Answer

The Flow needs a Scheduled Path because before-save Flows cannot update the triggering record.

Answer

The Flow is running in system context and cannot modify the OwnerId field.

Answer

The administrator must enable 'Run Flow in System Context with Sharing' in the Flow properties.

Question 15

An administrator at Get Cloudy Consulting built an Autolaunched Flow that is invoked from an Apex trigger on the Account object. The Flow performs several Update Records elements on related Contacts. During bulk data loads of 200 Accounts, the transaction fails with a 'Too many SOQL queries: 101' error. Which approach should the administrator take to resolve the issue?

Accepted Answer

Move the Update Records elements outside the loop and use collection variables to process all related Contacts in a single bulk operation.. Governor limits are per-transaction and cannot be bypassed. The failing Flow is performing DML and queries inside a loop, so processing 200 Accounts multiplies the operations until the SOQL limit is exceeded. Collecting Contacts into a collection variable and updating them once outside the loop bulkifies the Flow, dramatically reducing query and DML counts and resolving the error.

Answer

Increase the SOQL query limit by enabling 'Bypass Governor Limits' in the Flow properties.

Answer

Convert the Flow to a Process Builder process, which is exempt from SOQL limits.

Answer

Add a Fault Path to the Flow that catches the limit exception and retries the operation.

Question 16

Cloud Kicks needs a process to automatically update the 'Account Status' field on all related Contacts to 'Inactive' whenever an Account's status is changed to 'Closed'. Which automation tool should the administrator use to achieve this with the least amount of maintenance?

Accepted Answer

Record-Triggered Flow. Record-Triggered Flows are the recommended tool for cross-object field updates in Salesforce. They replace legacy workflows and process builders because they are more efficient and execute before or after database changes. By using an after-save flow, the administrator can easily traverse the Account-Contact relationship to perform bulk updates while ensuring the process remains declarative, scalable, and highly visible within the Flow Builder interface for future maintenance.

Answer

Workflow Rules

Answer

Approval Process

Answer

Apex Trigger

Question 17

An administrator wants to automate a process that requires a user to confirm they want to proceed before the record is updated. Which tool should the administrator choose?

Accepted Answer

Screen Flow. Screen Flows are the only declarative automation tool that allows for user interaction through a UI. By placing a screen element, the administrator can prompt users for input or confirmation. This is essential when the automation logic depends on human judgment or manual verification, which cannot be achieved through record-triggered background automation. Screen flows provide the necessary interface to engage users in a guided, consistent business process.

Answer

Record-Triggered Flow

Answer

Scheduled Flow

Answer

Platform Event-Triggered Flow

Question 18

Universal Containers has a Record-Triggered Flow on the Case object that runs when a Case is created or updated and sends a notification email to the assigned owner. During testing, the administrator notices the flow sends duplicate emails when a user edits a Case twice within a few seconds. The administrator needs the flow to run only when the Case's Priority field actually changes value. Which configuration should the administrator apply?

Accepted Answer

Set the Start element to run only when a record is updated, and add an entry condition comparing the PriorValue of Priority to its current value.. Record-Triggered Flows that start on create or update fire on every qualifying save, so unrelated edits can re-trigger notifications. Restricting the Start element to updates and adding an entry condition that compares the prior stored value of Priority against the incoming value ensures the automation runs only when that specific field is genuinely modified, which removes the duplicate sends without blocking other edits.

Answer

Create a validation rule on the Case object that blocks saves when Priority is unchanged, forcing users to modify the field before the record can be saved.

Answer

Configure the flow to run asynchronously so that rapid successive edits are consolidated into a single scheduled interview before the notification is sent.

Answer

Add a Decision element immediately after the Start element that checks whether the record's Priority equals High, and route non-matching records to an end element.

Question 19

An administrator at Cloud Kicks has built a Record-Triggered Flow on Opportunity that fires when Stage changes to 'Closed Won'. The flow sends a notification email to the opportunity owner. Testing shows the email fires multiple times for a single stage change when the opportunity is updated by an integration user. The administrator wants to ensure the email is sent only once per opportunity close. What should the administrator do?

Accepted Answer

Add a condition to check that the prior value of Stage is not 'Closed Won' and the current value is 'Closed Won'.. The duplicate emails occur because the entry condition matches any update where Stage equals 'Closed Won', including updates that do not change Stage. Using PRIORVALUE() to detect the actual transition from a different stage into 'Closed Won' ensures the flow fires exactly once per close. This is the recommended pattern for one-time transition automation in Record-Triggered Flows.

Answer

Set the flow to run asynchronously so that it processes only the most recent update.

Answer

Configure the flow to run only when the record is updated by a specific user.

Answer

Change the flow trigger to run only when a record is created and set the Stage to 'Closed Won' by default.

Question 20

A Salesforce administrator is asked to automate a multi-step approval process for discount requests on Opportunity. The process must route to different approvers based on the discount percentage, allow approvers to reject with comments, and update the Opportunity stage upon final approval. The administrator wants to build this declaratively without code. Which tool should be used?

Accepted Answer

Approval Process with steps and approval actions.. Approval Processes are the declarative Salesforce feature designed specifically for routing records to approvers, supporting multiple steps with criteria-based approver selection, rejection with comments, and post-approval actions like field updates. The other options either lack native approval mechanics or require custom development to approximate them, making Approval Processes the correct choice for this requirement.

Answer

Einstein Next Best Action with a recommendation strategy.

Answer

Record-Triggered Flow with a decision element and an approval action.

Answer

Scheduled-Triggered Flow that checks discount fields nightly and assigns tasks to approvers.