All practice questions

1784 questions

All types1,784 Multiple choice918 Multiple select587 Matching142 Ordering137

A Salesforce administrator is configuring data quality controls and automation on a custom object. Which two automation or validation events execute BEFORE custom validation rules during the Salesforce record save order of execution? (Select two answers.)

Select all that apply

System validation rules (such as checking required fields and field data formats)

Before-save record-triggered flows

After-save record-triggered flows

Workflow rules and automated field updates

Case or Lead Assignment rules

Show answer & explanation

Answer: System validation rules (such as checking required fields and field data formats); Before-save record-triggered flows

Answer

System validation rules and before-save record-triggered flows execute before custom validation rules during the Salesforce record save order of execution.

In the Salesforce order of execution, system validation rules (verifying standard required fields and length constraints) and before-save record-triggered flows execute prior to custom validation rules. This allows before-save flows to populate or adjust fields before custom validation logic evaluates the record.

Step-by-Step Solution

Analyze the standard sequence of events when saving a record in Salesforce.

Salesforce first checks system validation rules, then executes before-save record-triggered flows, and subsequently runs custom validation rules.

Running before-save flows prior to custom validation rules allows automated field updates on the triggering record to be validated before committing changes.

Evaluate post-validation automation events.

After-save flows, assignment rules, and workflow rules execute after custom validation rules have completed.

Custom validation rules must pass to ensure data integrity before record updates proceed to database insertion and downstream automation.

Key Concept

Salesforce Order of Execution: Pre-Validation Automation Steps

Question 1482Question →

A company requires an automated process on the Case object. When a Case status is updated to 'Closed', all associated open Task records must have their status changed to 'Completed'. To maintain system efficiency and prevent reaching governor limits during bulk updates, which design pattern and element structure should be used in Flow Builder?

Retrieve open Tasks with a Get Records element, loop through the collection, update each Task item's fields and add it to a output collection variable using an Assignment element inside the loop, then execute a single Update Records element outside the loop.

Retrieve open Tasks with a Get Records element, loop through the record collection, and place an Update Records element inside the loop to save each Task record immediately upon modification.

Create a Roll-Up Summary field on the Case object to count open Tasks, then use a Decision element to update child Tasks directly without using a collection variable.

Loop through the Task records and use an Assignment element inside the loop to update the available picklist values assigned to the Task record type.

Show answer & explanation

Answer: Retrieve open Tasks with a Get Records element, loop through the collection, update each Task item's fields and add it to a output collection variable using an Assignment element inside the loop, then execute a single Update Records element outside the loop.

Answer

Retrieve open Tasks using a Get Records element, loop through the collection, update field values and append items to a new collection using an Assignment element inside the loop, and place a single Update Records element outside the loop.

The correct approach uses a Get Records element to retrieve all related open Tasks into a collection, iterates through the collection using a Loop element, uses Assignment elements inside the loop to modify field values in memory and stage them into a output collection, and finally uses a single Update Records element outside the loop to commit all updates to the database in a single transaction.

Step-by-Step Solution

Query related records into a collection variable

A Get Records element fetches all open Tasks related to the triggering Case into a record collection.

Bulkifying data retrieval ensures only one SOQL query is executed.

Process items in memory using Loop and Assignment elements

For each Task in the loop, set the Status field to 'Completed' and add the current loop item to a new output record collection variable.

In-memory variable manipulation does not consume database governor limits.

Persist changes using a single DML operation outside the loop

An Update Records element references the output collection variable after the loop finishes.

Executing DML outside the loop ensures only one database write operation occurs regardless of record count.

Key Concept

Bulkification in Flow Builder using collections, loops, and external DML elements

Question 1483Question →

An administrator is creating an autolaunched flow to process a collection of Contract records associated with an Account whenever the Account tier is upgraded. The flow must update the Status field to 'In Review' on each associated Contract record and persist these changes back to Salesforce. Which design pattern should the administrator implement to ensure the flow executes efficiently without hitting governor limits?

Iterate through the Contract collection using a Loop element, use an Assignment element inside the loop to set updated field values on the current item and append it to a target Record Collection Variable, and place a single Update Records element outside the loop referencing the target collection.

Iterate through the Contract collection using a Loop element, update the field values on the current record item, and execute an Update Records element inside the loop during each iteration.

Place a Get Records element inside a Loop element to re-fetch each Contract record, update the values directly on the retrieved record, and invoke a single Update Records element at the end of the flow referencing the Account record.

Use a Decision element inside a Loop element to clear the existing collection, assign the modified values to a single Record Variable, and execute a Create Records element inside the loop to insert duplicate contracts.

Show answer & explanation

Answer: Iterate through the Contract collection using a Loop element, use an Assignment element inside the loop to set updated field values on the current item and append it to a target Record Collection Variable, and place a single Update Records element outside the loop referencing the target collection.

Answer

To process multiple records efficiently in Salesforce Flow, field assignments should be staged in memory using an Assignment element inside the Loop. The modified items are added to a separate Record Collection Variable, and a single Update Records element is executed outside the loop to commit all updates in bulk.

Step-by-Step Solution

Iterate over the collection of Contract records

Each record item is made available sequentially within the Loop element context.

Allows memory-based field modifications for every record in the collection.

Modify fields and add to an output collection variable using an Assignment element inside the loop

Field changes are stored in memory and added to a target Record Collection Variable.

Prevents database transactions inside loop iterations.

Execute a single Update Records element outside the loop

All updated records in the target Record Collection Variable are persisted to Salesforce in one bulk DML statement.

Adheres to Salesforce governor limits by executing only one DML statement regardless of collection size.

Key Concept

Flow Bulkification and Collection Processing

Question 1484Question →

An administrator is configuring automated record processing for a custom object that tracks Service Requests. When a record meets specified criteria, the business requires immediate automated actions to be executed using a Workflow Rule. Which TWO standard actions can be natively added to a Workflow Rule? (Select TWO)

Select all that apply

Creating a new Task assigned to a specific user

Sending an Outbound Message to an external designated endpoint

Executing an autolaunched Flow directly from the workflow action menu

Invoking an Apex class directly without using an Apex trigger

Show answer & explanation

Answer: Creating a new Task assigned to a specific user; Sending an Outbound Message to an external designated endpoint

Answer

The two native workflow actions are creating a new Task and sending an Outbound Message.

Salesforce Workflow Rules allow four specific types of automated actions: Field Updates, Email Alerts, Tasks, and Outbound Messages. Therefore, assigning a new Task and sending an Outbound Message are both valid native actions.

Step-by-Step Solution

Identify the standard automated actions supported natively by Salesforce Workflow Rules.

Workflow Rules natively support exactly four automated actions: Field Updates, Email Alerts, Tasks, and Outbound Messages.

Understanding native capability prevents selecting actions that belong to other automation tools like Flow Builder or Apex.

Evaluate the options against the four standard workflow actions.

Creating a Task and sending an Outbound Message match the supported list, whereas launching a Flow or calling Apex code directly are not supported in Workflow Rules.

Only Tasks, Outbound Messages, Field Updates, and Email Alerts can be configured directly inside a Workflow Rule.

Key Concept

Salesforce Classic Workflow Rules support four specific native automated actions: Field Updates, Email Alerts, Tasks, and Outbound Messages.

Estimated Time:1m 0s

Question 1485Question →

A Salesforce Administrator is building an autolaunched flow to update the status of multiple Account records. The flow iterates through a collection of records using a Loop element. What should the administrator do to perform the update while adhering to Salesforce governor limits and bulkification best practices?

Add an Update Records element inside the Loop element to immediately save changes for each Account record during each iteration.

Assign modified values to record variables, add each variable to a record collection inside the loop, and place a single Update Records element outside the loop.

Use an after-save record-triggered flow element inside the loop to automatically push updates to the database.

Place a Get Records element inside the loop to re-query each Account before updating it with a separate Update Records element inside the loop.

Show answer & explanation

Answer: Assign modified values to record variables, add each variable to a record collection inside the loop, and place a single Update Records element outside the loop.

Answer

Assign modified values to record variables, add each variable to a record collection inside the loop, and place a single Update Records element outside the loop.

The correct option follows Salesforce flow bulkification standards: field updates are staged in memory and collected into a record collection variable during loop iteration, followed by a single Update Records element after the loop completes.

Step-by-Step Solution

Iterate over the collection using the Loop element

Each record in the collection is processed individually in memory.

Allows individual field modifications on current loop items without performing immediate database queries or commits.

Update field values and add modified record variables to a output collection variable using Assignment elements

All updated records are stored in a single collection variable in memory.

Accumulating changes in memory prevents executing DML statements repeatedly inside the loop.

Execute a single Update Records element referencing the output collection variable after the loop finishes

All modified records are committed to the database in a single bulkified DML operation.

Consumes only 1 DML statement against governor limits regardless of the number of items in the collection.

Key Concept

Bulkification of DML Operations in Flow Loops

Question 1486Question →

A Salesforce Administrator is configuring data quality enforcement rules for different business scenarios across standard and custom objects. Match each business requirement with the validation rule formula snippet that correctly implements the required logic.

Click a left item, then click its matching right item

Show answer & explanation

Answer

Each business requirement correctly maps to its respective formula function: 1 maps to AND with ISCHANGED/ISPICKVAL/ISBLANK; 2 maps to NOT(ISNEW()) combined with $Permission verification; 3 maps to the VLOOKUP function for cross-record validation; 4 maps to the REGEX function for string pattern validation.

Each requirement leverages the appropriate formula function tailored to the target data type and logic requirement: ISPICKVAL and ISBLANK for picklist/null checks, ISNEW and $Permission for record lifecycle and access controls, VLOOKUP for dynamic cross-record lookup comparisons, and REGEX for text pattern validation.

Step-by-Step Solution

Analyze requirement 1 (Rating to 'Hot' requiring Annual Revenue)

Identified the need for ISPICKVAL to evaluate the picklist value, ISCHANGED to detect transitions, and ISBLANK for null checking.

Picklist fields must be evaluated with ISPICKVAL or TEXT in validation rules.

Analyze requirement 2 (Account Number edit restrictions)

Matched with NOT(ISNEW()) to exclude newly created records, ISCHANGED for field modification tracking, and $Permission to evaluate custom user permissions.

Validation rules fire on both create and update operations unless constrained by ISNEW().

Analyze requirement 3 (Cross-object postal code to state match)

Matched with VLOOKUP, which evaluates field values across custom object data records.

VLOOKUP is specifically designed in Salesforce validation rules to look up values in custom objects based on a key field.

Analyze requirement 4 (Tax ID string format enforcement)

Matched with REGEX matching the regular expression string template \d{3}-\d{2}-\d{4}.

Pattern validation for structured text (like SSN, Phone, Tax IDs) requires the REGEX function.

Key Concept

Salesforce Validation Rule Formula Functions (ISBLANK, ISPICKVAL, VLOOKUP, REGEX, ISNEW)

Question 1487Question →

An administrator is troubleshooting an Approval Process configured for a custom object named Project Request. Upon initial submission, an initial submission action is configured to lock the record. However, during testing, a sales manager who is assigned as the approver for Step 1 is still able to edit field values on the record while its status is 'Pending Approval'. System administrators wish to understand why this user can edit the locked record while non-approver submitters cannot. Which approval process configuration setting accounts for this behavior?

The Approval Process Record Editability setting is configured to allow Administrators OR the currently assigned approver to edit records during the approval process.

The record locking action was omitted from the Initial Submission Actions section during approval process setup.

The sales manager's profile has the 'Modify All Data' permission, which completely disables approval locking mechanism triggers on custom objects.

The Organization-Wide Default (OWD) sharing setting for the Project Request object is set to Public Read/Write, overriding approval locking.

Show answer & explanation

Answer: The Approval Process Record Editability setting is configured to allow Administrators OR the currently assigned approver to edit records during the approval process.

Answer

The Approval Process Record Editability setting is configured to allow Administrators OR the currently assigned approver to edit records during the approval process.

Salesforce Approval Processes feature a specific configuration property called Record Editability. When set to 'Administrators OR the currently assigned approver', the system allows the user assigned to the current approval step to edit the record even while it remains locked to all other non-admin users.

Step-by-Step Solution

Analyze the observed behavior

The record is locked upon initial submission so standard users cannot edit it, but the assigned approver (sales manager) can still edit fields while the record is in the approval step.

Identifying that only assigned approvers can edit helps isolate step-specific editability settings from global locking failures.

Evaluate Salesforce Approval Process properties

During Approval Process detail setup, administrators select Record Editability options: 'Administrators ONLY' or 'Administrators OR the currently assigned approver'.

Choosing 'Administrators OR the currently assigned approver' grants editing rights to whoever is currently assigned to approve the active step.

Confirm why other settings do not apply

OWD permissions do not bypass approval locking, and omitting locking entirely would leave the record editable by all users rather than just the approver.

Ruling out misconceptions ensures accurate diagnosis of Salesforce record locking mechanics.

Key Concept

Approval Process Record Editability Settings

Question 1488Question →

An administrator is configuring a multi-step approval process for custom Equipment Request records. Step 1 requires approval from the submitter's manager. Step 2 requires executive approval, but only when the requested amount exceeds $5,000. If an Equipment Request with an amount of$ 2,500 is approved in Step 1, which step entry criteria configuration ensures the record automatically completes the process as fully approved without routing to Step 2?

Add an initial submission action to evaluate the amount field and set the approval status to approved.

Configure Step 2 entry criteria to 'Approve record' if the record does not meet the criteria.

Create a validation rule that updates the approval status field to approved when the amount is less than or equal to $5,000.

Use an after-save record-triggered flow to automatically clear the executive approver field prior to Step 2 execution.

Show answer & explanation

Answer: Configure Step 2 entry criteria to 'Approve record' if the record does not meet the criteria.

Answer

Configure Step 2 entry criteria to 'Approve record' if the record does not meet the criteria.

In Salesforce approval processes, step entry criteria dictate whether a record enters a specific step. Administrators configure the fallback behavior for records that do not meet the step's criteria. Setting the fallback option to 'Approve record' on Step 2 ensures that if the request amount is $5,000 or less, the record bypasses Step 2 and immediately executes the final approval actions.

Step-by-Step Solution

Analyze the approval process step requirements

Step 1 must execute for all records. Step 2 only applies to records exceeding $5,000.

Records equal to or under $5,000 should finish the process as approved once Step 1 is completed.

Evaluate Salesforce Approval Step entry criteria options

Each step allows defining entry criteria and specifies what should happen if a record fails those criteria (e.g., 'Approve record', 'Reject record', or 'Skip this step').

Choosing 'Approve record' when criteria are not met instructs Salesforce to mark the process as approved and execute final approval actions when a record under $5,000 reaches Step 2.

Key Concept

Approval Step Entry Criteria and Unmet Criteria Behavior

Question 1489Question →

An administrator at CloudHorizon is designing automation for the custom object Partner_Tier_Review__c to fulfill two distinct business requirements:

1. Automatically calculate and set the Expiration_Notice_Date__c and Tier_Status__c fields on the triggering Partner_Tier_Review__c record whenever its status changes to 'Pending Approval', prior to committing the record to the database.
2. On the first day of every month at 1:00 AM, automatically evaluate all active Partner_Tier_Review__c records and generate a reminder Task record for partner account managers if the review status remains 'Pending Approval'.

Which TWO automation design choices should the administrator implement to fulfill these requirements efficiently? (Select 2)

Select all that apply

Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) that triggers when a Partner_Tier_Review__c record is updated to 'Pending Approval'.

Configure a Schedule-Triggered Flow scheduled to run monthly that queries active Partner_Tier_Review__c records with a status of 'Pending Approval' and creates Task records.

Configure a Record-Triggered Flow optimized for Actions and Related Records (After-Save) that triggers when a Partner_Tier_Review__c record is updated to 'Pending Approval' to set the record's field values.

Configure a Screen Flow invoked by an Apex scheduled job to process background record updates and create Task records without user interaction.

Show answer & explanation

Answer: Configure a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) that triggers when a Partner_Tier_Review__c record is updated to 'Pending Approval'.; Configure a Schedule-Triggered Flow scheduled to run monthly that queries active Partner_Tier_Review__c records with a status of 'Pending Approval' and creates Task records.

Answer

The administrator should implement a Record-Triggered Flow optimized for Fast Field Updates (Before-Save) for same-record field modifications, and a Schedule-Triggered Flow executing monthly for automated batch task creation.

Updating field values on the originating record prior to saving to the database is best executed by a Record-Triggered Flow optimized for Fast Field Updates (before-save), as it avoids unnecessary DML operations. For recurring automated tasks operating on a batch of records on a specific cadence (monthly at 1:00 AM), a Schedule-Triggered Flow is the designated standard automation tool.

Step-by-Step Solution

Evaluate Requirement 1 (updating fields on the originating record prior to database commit).

Determine that updating fields on the record initiating the transaction before saving requires a Record-Triggered Flow configured for Fast Field Updates (Before-Save).

Before-save flows modify the record payload directly prior to database insertion/update, avoiding extra DML operations and save cycles.

Evaluate Requirement 2 (recurring batch processing to create related records on a scheduled cadence).

Determine that executing an automated check on a recurring schedule (monthly) to create related Task records requires a Schedule-Triggered Flow.

Schedule-Triggered flows provide native scheduling capabilities to run logic across targeted record batches without requiring custom code or user interaction.

Key Concept

Selecting the correct Salesforce Flow trigger types (Record-Triggered Fast Field Updates vs. Schedule-Triggered Flows) based on record update context and execution scheduling requirements.

Estimated Time:2m 0s

Question 1490Question →

A Salesforce Administrator at an automotive fleet management company is creating an Opportunity report to evaluate vehicle leasing pipeline records. The leadership team requests the following report criteria:

1. Include deals with an Amount greater than $100,000 OR deals in the 'Negotiation/Review' stage.
2. Exclusively restrict results to accounts headquartered in 'California' or 'Texas', regardless of amount or stage.
3. Include only opportunities whose parent Account has at least one related Service Contract record.

The administrator creates three field filters:
- Filter 1: Amount > 100000
- Filter 2: Stage equals Negotiation/Review
- Filter 3: Billing State/Province equals California, Texas

Which TWO configuration steps must the administrator take to meet these business requirements?

Select all that apply

Set the report filter logic string to (1 OR 2) AND 3.

Add a Cross Filter on the report for Opportunities with Accounts, with a sub-filter of Service Contracts with Count greater than or equal to 1.

Set the report filter logic string to 1 OR (2 AND 3).

Create a bucket field on the Account object to filter out opportunities without related service contracts.

Show answer & explanation

Answer: Set the report filter logic string to (1 OR 2) AND 3.; Add a Cross Filter on the report for Opportunities with Accounts, with a sub-filter of Service Contracts with Count greater than or equal to 1.

Answer

The administrator must set the report filter logic to (1 OR 2) AND 3 and add a Cross Filter for Opportunities with Accounts having related Service Contracts.

Configuring filter logic as (1 OR 2) AND 3 correctly groups the alternative opportunity conditions while ensuring the geographic boundary is enforced across all records. Adding a Cross Filter dynamically evaluates whether related service contracts exist for each account without requiring custom code or roll-up fields.

Step-by-Step Solution

Evaluate the Boolean logic needed for the standard field filters.

Filters 1 (Amount) and 2 (Stage) represent alternative criteria that must be grouped together with OR, whereas Filter 3 (State) is a mandatory condition that must be combined with AND.

Ensures that state restriction applies universally to both high-value deals and deals in negotiation.

Determine the proper tool to filter by related child object presence.

A Cross Filter configured for Opportunities with Accounts, filtered by related Service Contracts.

Standard report field filters operate on fields directly accessible on the report type, while Cross Filters enable conditional filtering based on related child object relationships.

Key Concept

Report Boolean Filter Logic and Cross Filters

Question 1491Question →

An administrator is reviewing the sequence of operations that occur when a record is saved in Salesforce. Place the following automation events and validation checks in the correct order of execution from earliest (first) to latest (last).

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of execution from first to last is: Before-Save Record-Triggered Flows, followed by Custom Validation Rules, then Apex After Triggers, and finally Workflow Rules.

In the Salesforce order of execution, before-save record-triggered flows run before custom validation rules. Once validation passes and the record is saved to the database, Apex after triggers execute. Workflow rules run later in the sequence, after Apex after triggers and assignment rules complete.

Step-by-Step Solution

Identify early-stage save processing

Before-save record-triggered flows execute first among the given items, running before Apex before triggers and validation rules.

Salesforce executes before-save flows near the beginning of the save cycle to allow fast field updates before database operations.

Identify validation phase

Custom validation rules run second among the given items.

Custom validation rules evaluate after before-save flows and Apex before triggers to ensure data compliance before inserting or updating the database record.

Identify post-insert/update trigger phase

Apex after triggers execute third among the given items.

After the record is initially written to the database (uncommitted), Apex after triggers execute to allow access to system fields like CreatedDate and Id.

Identify declarative post-save automation phase

Workflow rules run fourth among the given items.

Declarative automation processes such as assignment rules, auto-response rules, and workflow rules execute after Apex after triggers complete.

Key Concept

Salesforce Record Save Order of Execution

Question 1492Question →

A Salesforce Administrator is designing a record-triggered flow on a custom Contract object that executes when a Contract status updates to Activated. The flow must process all associated child Contract Line Item records linked via a custom lookup relationship, calculate total values, and update fields on both the line items and the parent Contract record while strictly avoiding governor limit violations. Which two design choices should the administrator implement within Flow Builder?

Select all that apply

Use an Assignment element inside the loop to aggregate values into variables and add modified line items to a record collection variable.

Place a Get Records element inside the loop to dynamically fetch full field details for each child Contract Line Item record during each iteration.

Position the Update Records element after the loop execution path to update the record collection in a single transaction.

Create a Roll-Up Summary field on the parent Contract object to calculate the total amount across the lookup relationship without using flow logic.

Show answer & explanation

Answer: Use an Assignment element inside the loop to aggregate values into variables and add modified line items to a record collection variable.; Position the Update Records element after the loop execution path to update the record collection in a single transaction.

Answer

The administrator should use an Assignment element inside the loop to accumulate totals and build a record collection in memory, and position the Update Records element after the loop path to perform a single bulkified DML operation.

To process multiple child records without reaching governor limits, calculations and record updates must be handled in memory within the loop using Assignment elements. The actual database update is bulkified by placing a single Update Records element outside the loop to process the accumulated collection.

Step-by-Step Solution

Evaluate relationship type and aggregation capabilities

Identified that Roll-Up Summary fields cannot be created on lookup relationships, necessitating automated Flow logic for calculations.

Roll-Up Summary fields strictly require a Master-Detail relationship on standard declarative configurations.

Configure loop iteration and in-memory variable assignment

Used Assignment elements within the loop path to calculate total amounts and append updated records into a collection variable.

Assignment elements execute in memory without consuming SOQL or DML transaction limits.

Bulkify database interactions

Placed the Update Records element along the 'After Last Item' path of the loop, targeting the record collection variable.

Executing data operations outside the loop ensures all record updates occur within a single DML statement.

Key Concept

Flow Builder Bulkification and Element Placement Rules

Question 1493Question →

An administrator is designing an autolaunched flow to process renewal opportunities associated with an Account. The flow must retrieve all related opportunities, isolate open renewal opportunities, modify their target dates, and commit the changes to Salesforce while adhering to governor limit best practices. Arrange the following flow execution steps in the correct sequential order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence is: 1) Execute a Get Records element to retrieve related Opportunity records. 2) Apply a Collection Filter element to isolate open renewal opportunities. 3) Iterate through the collection with a Loop element and use an Assignment element inside to update record fields and add items to a separate collection variable. 4) Execute an Update Records element after the loop finishes using the update collection variable.

The correct design sequence adheres to Salesforce bulkification principles: First, retrieve all records using Get Records. Second, filter the collection in memory using Collection Filter. Third, iterate over the filtered collection with a Loop and use Assignment elements to modify record values and store them in an output collection variable. Fourth, execute a single Update Records element after loop completion to update all records in one DML statement.

Step-by-Step Solution

Retrieve data into flow memory

Opportunity records linked to the Account are stored in a record collection variable.

Flow operations require records to be queried into memory before any filtering or updates can occur.

Filter record collection in memory

The collection is reduced to only open Renewal Opportunities.

Using a Collection Filter element processes data in memory without additional SOQL queries.

Loop and assign field changes to a new collection

Each record's fields are modified and added to an update collection variable.

Assignment elements inside loops stage record updates into a collection without invoking DML statements.

Perform bulkified DML update outside the loop

All updated records are committed to Salesforce in a single DML operation.

Placing the Update Records element after the loop prevents hitting the 150 DML statements governor limit.

Key Concept

Bulkified Flow Data Manipulation and Resource Processing Sequence

Estimated Time:2m 0s

Question 1494Question →

An organization wants to configure a Workflow Rule on the Account object to schedule a follow-up Task for the account owner 30 days after a VIP Account is marked as 'Active'. The administrator attempts to add a time-dependent workflow action, but the option to add time triggers is unavailable in the workflow rule setup. What is the most likely cause of this issue?

The rule evaluation criteria is set to 'created, and every time it's edited'.

The object has an active Record-Triggered Flow running after-save events.

The validation rules on the Account object are set to fire before system evaluation.

The initial submission action locks the record from triggering scheduled actions.

Show answer & explanation

Answer: The rule evaluation criteria is set to 'created, and every time it's edited'.

Answer

The rule evaluation criteria is set to 'created, and every time it's edited'.

Salesforce restricts time-dependent workflow actions on rules configured with the evaluation criteria 'created, and every time it's edited'. To use time-based triggers, the evaluation criteria must be set to 'created' or 'created, and any time it's edited to subsequently meet criteria'.

Step-by-Step Solution

Identify the restriction on time-dependent workflow actions in Salesforce Workflow Rules.

Time-dependent workflow actions are not supported for rules set to evaluate 'created, and every time it's edited'.

Because constantly re-evaluating on every edit could create unpredictable queues of pending actions.

Determine the required evaluation criteria setting to enable time triggers.

Change the evaluation criteria to 'created' or 'created, and any time it's edited to subsequently meet criteria'.

This allows Salesforce to cleanly schedule and clear time-based action queues.

Key Concept

Workflow Rule Evaluation Criteria Limitations for Time-Dependent Actions

Question 1495Question →

A financial services institution processes high volumes of custom Loan Application records daily. The architecture team requires an automated process to calculate and set a custom Risk Tier field directly on the Loan Application record whenever it is created or updated. To adhere to performance best practices and reduce database overhead, this field calculation on the triggering record must occur before the record is saved to the database, without initiating additional SQL DML statements or re-triggering save cycles.

Which declarative automation tool and configuration should the administrator select to fulfill this requirement?

A Record-Triggered Flow optimized for Fast Field Updates

A Record-Triggered Flow optimized for Actions and Related Records

A Roll-Up Summary field defined on the parent Account object linked via a lookup relationship

An Approval Process utilizing an Initial Submission Action field update to bypass execution order limits

Show answer & explanation

Answer: A Record-Triggered Flow optimized for Fast Field Updates

Answer

A Record-Triggered Flow optimized for Fast Field Updates is the correct declarative tool for updating fields on the triggering record before database commit.

The option selecting a Record-Triggered Flow optimized for Fast Field Updates is correct because before-save flows update fields on the triggering record in memory right before the record is saved to the database. This avoids additional DML operations, prevents recursion, and aligns with Salesforce performance architecture guidelines.

Step-by-Step Solution

Analyze the automation objective and record scope

The requirement involves setting a field on the triggering record itself (Loan Application) upon creation or edit.

Determining whether updates affect the triggering record or related records dictates the optimal trigger timing.

Evaluate performance guidelines and execution timing constraints

The solution must update the triggering record before saving to the database to eliminate extra DML statements.

Before-save flows run much faster than after-save automations because they modify the record in memory before the initial database write.

Select the appropriate Salesforce Flow configuration type

Choose a Record-Triggered Flow with the 'Fast Field Updates' (before-save) option selected.

Fast Field Updates is Salesforce's recommended declarative standard for same-record field modifications.

Key Concept

Selecting Record-Triggered Flow trigger types based on execution timing (Before-Save vs After-Save)

Question 1496Question →

A Salesforce Administrator is configuring a automated approval process for custom Discount Request records. Place the following stages of the approval process execution lifecycle in the correct chronological order from record submission to process completion.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct execution order is: 1. Evaluate overall process entry criteria -> 2. Execute Initial Submission Actions (locking record and updating status) -> 3. Evaluate step criteria and assign request to approver -> 4. Execute Final Approval Actions (unlocking record and setting final status).

In Salesforce Approval Processes, overall entry criteria are evaluated first upon submission. Once validated, Initial Submission Actions execute (locking the record and executing initial actions). Then step-level criteria are evaluated to assign the request. Finally, after all required steps are approved, Final Approval Actions execute to complete the process.

Step-by-Step Solution

Validate overall entry criteria

System checks if the record meets the criteria defined at the approval process level before proceeding.

If entry criteria are not met, the record cannot enter the approval process.

Trigger Initial Submission Actions

Record is locked by default and initial submission field updates, email alerts, or outbound messages execute.

Initial submission actions establish the pending state and prevent unauthorized edits while under review.

Evaluate Step Criteria and Route Request

System evaluates step-level criteria and routes the item to the designated approver's queue or manager.

Determines whether specific step actions are required and alerts the assigned decision-maker.

Perform Final Approval Actions

Upon final approval, the system executes final actions such as record unlocking, field updates, and notifications.

Completes the lifecycle by granting approval status and restoring standard editability if configured.

Key Concept

Salesforce Approval Process Execution Lifecycle

Question 1497Question →

Apex Financial Services requires a declarative automation strategy to optimize Case management operations. When a Case is created or updated, custom fields on that same Case record must be populated prior to saving to prevent extra DML operations and avoid re-triggering the Salesforce order of execution. Additionally, management needs to display a live aggregate count of related Compliance Audit records directly on the Case record, where Compliance Audit is linked to Case via a master-detail relationship. Which two declarative solutions should the administrator select to fulfill these requirements? (Select TWO)

Select all that apply

Create a Record-Triggered Flow set to optimize for Fast Field Updates to handle same-record field modifications.

Create a Roll-Up Summary field on the Case object to aggregate metrics from the related Compliance Audit records.

Create a Record-Triggered Flow set to optimize for Actions and Related Records to handle same-record field modifications.

Create a Roll-Up Summary field on the parent object to aggregate metrics from records linked via a Lookup relationship.

Show answer & explanation

Answer: Create a Record-Triggered Flow set to optimize for Fast Field Updates to handle same-record field modifications.; Create a Roll-Up Summary field on the Case object to aggregate metrics from the related Compliance Audit records.

Answer

The administrator should select a Record-Triggered Flow configured for Fast Field Updates for same-record updates, and a Roll-Up Summary field on the Case object to aggregate the child Compliance Audit records.

Fast Field Updates (Before-Save record-triggered flows) are specifically optimized for modifying fields on the triggering record before database commit without incurring DML overhead. Roll-Up Summary fields natively aggregate child record data on the master record in a Master-Detail relationship.

Step-by-Step Solution

Analyze the requirement for same-record field updates before database commit.

Fast Field Updates (Before-Save Flows) run prior to save, updating the triggering record without extra DML commands or re-triggering execution order.

Using After-Save flows for same-record updates introduces redundant database operations.

Analyze the requirement for real-time aggregate counts from related child records.

A Roll-Up Summary field on the Case parent object dynamically calculates aggregate values from child records linked by a Master-Detail relationship.

Roll-Up Summary fields are built-in declarative elements for Master-Detail relationships.

Key Concept

Automation Tool Selection based on execution timing and relationship types

Question 1498Question →

A Salesforce Administrator needs to build a daily Schedule-Triggered Flow that processes expired Subscription custom records and updates their parent Account records with the aggregated renewal values. The Subscription object is related to Account via a Lookup relationship. Which design approach using Flow Builder elements accurately satisfies this requirement while respecting governor limits?

Use a Loop element to iterate through the retrieved Subscriptions, an Assignment element inside the loop to calculate updated values into record variables, and a single Update Records element placed after the loop finishes.

Place an Update Records element inside the Loop element to immediately save changes to each parent Account record during every iteration.

Create a Roll-Up Summary field on the Account object to automatically calculate the total subscription sum without needing Flow Builder logic.

Use an Assignment element inside the loop to commit field modifications directly to the database without needing an Update Records element.

Show answer & explanation

Answer: Use a Loop element to iterate through the retrieved Subscriptions, an Assignment element inside the loop to calculate updated values into record variables, and a single Update Records element placed after the loop finishes.

Answer

Use a Loop element to iterate through retrieved records, an Assignment element inside the loop to modify values in memory, and an Update Records element outside the loop to execute a single bulkified DML operation.

The correct approach bulkifies the flow by utilizing an Assignment element within the loop to calculate aggregate values in memory, followed by executing a single Update Records element outside of the loop after iteration concludes.

Step-by-Step Solution

Evaluate relationship type constraints

Since Subscription and Account are connected via a Lookup relationship, standard Roll-Up Summary fields cannot be created on Account.

Roll-Up Summary fields require a Master-Detail relationship.

Design loop and assignment logic

Iterate through Subscription records with a Loop element and use an Assignment element to sum totals into flow variables.

Assignment elements perform in-memory calculations without consuming governor limits.

Place database operations outside the loop

Position the Update Records element after the loop path completes.

Bulkifying database operations by executing DML outside of loops avoids governor limit exceptions.

Key Concept

Flow Bulkification and Governor Limits

Question 1499Question →

An administrator is tasked with enforcing data quality standards on a custom object named Partner_Application__c. Business policy requires that whenever the Tier__c picklist field is set to either 'Gold' or 'Platinum', the Tax_Identification_Number__c custom text field must not be left blank. Which validation rule formula correctly enforces this requirement to prevent saving non-compliant records?

AND( OR(ISPICKVAL(Tier__c, 'Gold'), ISPICKVAL(Tier__c, 'Platinum')), ISBLANK(Tax_Identification_Number__c) )

OR( AND(ISPICKVAL(Tier__c, 'Gold'), ISPICKVAL(Tier__c, 'Platinum')), ISBLANK(Tax_Identification_Number__c) )

AND( OR(ISPICKVAL(Tier__c, 'Gold'), ISPICKVAL(Tier__c, 'Platinum')), NOT(ISBLANK(Tax_Identification_Number__c)) )

AND( Tier__c = 'Gold', Tier__c = 'Platinum', ISBLANK(Tax_Identification_Number__c) )

Show answer & explanation

Answer: AND( OR(ISPICKVAL(Tier__c, 'Gold'), ISPICKVAL(Tier__c, 'Platinum')), ISBLANK(Tax_Identification_Number__c) )

Answer

The correct formula is AND( OR(ISPICKVAL(Tier__c, 'Gold'), ISPICKVAL(Tier__c, 'Platinum')), ISBLANK(Tax_Identification_Number__c) ).

The correct formula uses OR(ISPICKVAL(Tier__c, 'Gold'), ISPICKVAL(Tier__c, 'Platinum')) to check if either target tier is selected, combined with ISBLANK(Tax_Identification_Number__c) inside an outer AND function. Because a validation rule fires when the formula evaluates to TRUE, this logic successfully blocks saves when a Gold or Platinum application lacks a tax identification number.

Step-by-Step Solution

Identify the conditions under which the validation rule should trigger an error message.

The rule must trigger when (Tier is 'Gold' OR Tier is 'Platinum') AND the Tax_Identification_Number__c field ISBLANK.

Salesforce validation rules display error messages when the formula expression evaluates to TRUE.

Select the correct Salesforce formula functions for picklists and text fields.

Use ISPICKVAL() to evaluate single-select picklist field values, and ISBLANK() to evaluate whether a text field contains no data.

Standard equality operators like '=' cannot be used on picklist fields in standard formula logic without ISPICKVAL, and ISBLANK is preferred over ISNULL for text fields.

Combine the logical functions inside an outer AND function.

AND( OR(ISPICKVAL(Tier__c, 'Gold'), ISPICKVAL(Tier__c, 'Platinum')), ISBLANK(Tax_Identification_Number__c) )

This guarantees that both the tier qualification (Gold or Platinum) and the missing data condition (blank Tax ID) must be simultaneously met to throw the error.

Key Concept

Validation Rule Logic and Picklist Evaluation Functions

Estimated Time:1m 15s

Question 1500Question →

An organization relies on several automation and data quality features on the Case object. A Salesforce administrator has configured both a custom validation rule and a before-save record-triggered flow on the Case object. When a user updates and saves a Case record, which sequence describes the correct order of execution?

The before-save record-triggered flow executes first, followed by the custom validation rule.

The custom validation rule executes first, followed by the before-save record-triggered flow.

The custom validation rule executes first, followed by Case assignment rules and then the before-save flow.

Workflow rules execute first, followed by the custom validation rule and before-save record-triggered flow.

Show answer & explanation

Answer: The before-save record-triggered flow executes first, followed by the custom validation rule.

Answer

The before-save record-triggered flow executes first, followed by the custom validation rule.

During the Salesforce record save process, before-save record-triggered flows execute very early, prior to Apex before triggers and custom validation rules. This allows any field values updated by the before-save flow to be evaluated by custom validation rules before the record is saved to the database.

Step-by-Step Solution

Identify the automation features being evaluated during record save.

The features present are a before-save record-triggered flow and a custom validation rule.

Determining which elements exist helps locate their respective positions in the Salesforce save order of execution.

Evaluate the standard Salesforce order of execution sequence.

Before-save record-triggered flows execute early in the sequence (before Apex before triggers and custom validation rules). Custom validation rules evaluate after before-save flows.

This sequence ensures field values populated or changed by before-save automation can be checked by custom validation rules.

Key Concept

Order of Execution: Before-Save Flows vs Custom Validation Rules

PreviousPage 75 / 90Next

All practice questions

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept