Examkin

All practice questions

137 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 1Question →

A Salesforce Administrator needs to convert a standard Record Detail component on a custom object record page to Dynamic Forms. What is the correct sequence of steps the administrator must take within the Lightning App Builder to complete this migration?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence to convert a page layout to Dynamic Forms is: 1) Open the record page in Lightning App Builder, 2) Select the standard Record Detail component on the canvas, 3) Click 'Upgrade Now' in the component properties pane, 4) Select the source page layout to import fields and sections and complete the wizard, 5) Save and activate the Lightning Record Page.
To migrate an existing record page to Dynamic Forms, an administrator opens the record page in Lightning App Builder, selects the Record Detail component on the canvas, clicks the 'Upgrade Now' action in the properties pane, chooses the source page layout to import existing fields and sections, and finally saves and activates the page.

Step-by-Step Solution

1
Navigate to Lightning App Builder for the target object's record page.
The Lightning App Builder canvas loads with the current page components.
Dynamic Forms setup and page customization take place directly within the Lightning App Builder interface.
2
Click on the standard Record Detail component on the canvas.
The right-hand panel opens, displaying the properties for the Record Detail component.
The migration feature is initiated from the properties panel of the existing Record Detail component.
3
Click the 'Upgrade Now' button in the properties panel.
The Dynamic Forms migration wizard launches.
This action initiates the guided process to break down the monolithic layout into flexible field section components.
4
Select the desired page layout to migrate and complete the wizard steps.
Fields and Field Section components are placed onto the canvas automatically based on the selected layout.
Selecting an existing page layout allows Salesforce to automatically extract fields and sections without manual reconstruction.
5
Save the page and activate it for the appropriate profiles, apps, or org default.
The newly upgraded Dynamic Forms page is deployed to end users.
Changes in Lightning App Builder must be saved and activated before they become visible to users in Salesforce.

Key Concept

Upgrading Record Detail to Dynamic Forms in Lightning App Builder
Estimated Time:1m 30s
Question 2Question →

An administrator needs to enable Dynamic Actions on an existing custom object record page in Lightning App Builder and restrict the visibility of the 'Delete' action based on user permission. What is the correct sequence of steps to accomplish this requirement?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins by opening the record page in Lightning App Builder, selecting the Highlights Panel component, clicking 'Upgrade Now' in the properties pane, choosing a page layout source to migrate actions, and finally selecting the specific action to apply an Action Visibility filter.
To enable Dynamic Actions, an administrator must open the Lightning Record Page in Lightning App Builder, select the Highlights Panel, click 'Upgrade Now', select a layout source to complete the migration wizard, and then select the specific action to apply visibility filter rules.

Step-by-Step Solution

1
Navigate to the Lightning App Builder for the target object page.
The page canvas opens with all configured components accessible.
Component-level configuration for actions requires working within the Lightning App Builder tool.
2
Click directly on the Highlights Panel component.
The right-hand properties panel updates to show Highlights Panel settings.
Dynamic Actions are managed through the Highlights Panel properties pane.
3
Click the 'Upgrade Now' button in the properties panel.
The Dynamic Actions migration wizard pops up.
Upgrading converts action management from page layouts to Lightning App Builder component level.
4
Select the source page layout to extract existing actions and complete the wizard.
Actions are converted to Dynamic Actions directly configurable on the component.
Migrating preserves existing page layout action assignments as a baseline.
5
Select the 'Delete' action from the action list and add an Action Visibility rule.
The action is restricted based on specified filter criteria.
Filters on Dynamic Actions determine runtime visibility per user or record context.

Key Concept

Configuring Dynamic Actions and Action Visibility Filters in Lightning App Builder
Question 3Question →

An administrator needs to configure a weekly automated backup of all organizational data using the native Salesforce Data Export Service. Arrange the steps in the correct chronological order to complete this setup.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for scheduling a weekly data export is: 1) Navigate to Data Export in Setup, 2) Click Schedule Export, 3) Configure file encoding and attachment options, 4) Set the frequency to Weekly along with the date and time window, and 5) Select the object data to export and save the schedule.
To set up an automated recurring backup in Salesforce using the native Data Export Service, an administrator must first access Data Export in Setup, choose to Schedule Export, specify encoding and attachment settings, establish the weekly frequency window, and select the objects to export before saving.

Step-by-Step Solution

1
Locate the Data Export tool in Setup.
Opens the Data Export administration page.
Setup is the central hub for administrative tasks including backup configuration.
2
Click Schedule Export.
Opens the scheduling interface for automated backups.
Export Now performs an immediate run, whereas Schedule Export creates a recurring job.
3
Define file encoding and attachment inclusion settings.
Ensures document attachments and chatter files are included if required.
Attachment settings must be configured prior to specifying scheduled times.
4
Set frequency parameters.
Schedules the export service to run weekly within specified date ranges.
Salesforce requires a start/end date and preferred execution window.
5
Select data objects and save.
Persists the scheduled export job in Salesforce.
Saving completes the configuration process.

Key Concept

Data Export Service Scheduling
Estimated Time:1m 0s
Question 4Question →

An enterprise administrator needs to bulk-import thousands of new child Service Contract records and automatically link them to existing parent Account records using Data Loader. The parent Account records already contain a unique custom External ID field named Legacy_Account_ID__c. What is the correct sequence of steps the administrator must follow to successfully map and relate the child records to parent Accounts using Data Loader?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with verifying parent record External IDs in Salesforce, preparing the child CSV file with parent External ID foreign keys, initializing the Data Loader Insert operation, mapping the CSV column to the Account:Legacy_Account_ID__c relationship reference field, and concluding with executing the operation and inspecting success/error logs.
The workflow requires establishing prerequisites first (ensuring parent External IDs exist in Salesforce), preparing the child CSV file with those external keys, configuring Data Loader for the child object insert, mapping the CSV key column to the related parent External ID syntax (Account:Legacy_Account_ID__c), and finally running the import while checking the execution log files.

Step-by-Step Solution

1
Ensure parent Account External IDs exist in Salesforce
Salesforce Accounts are properly indexed and ready for external key matching
Data Loader cannot resolve foreign key relationships if the target external identifier field is blank or missing on parent records.
2
Prepare child record CSV with parent External ID column
Source CSV contains accurate foreign key references for each child row
Data Loader relies on foreign key values in the import file to determine which Account each Service Contract belongs to.
3
Initialize Data Loader Insert wizard for Service Contract
Data Loader parses CSV headers and connects to the Service Contract object schema
Selecting the proper object and file establishes the baseline schema mapping context.
4
Map foreign key column to Account:Legacy_Account_ID__c
Field mapping establishes a relational lookup using the parent External ID
Data Loader syntax requires selecting the related object's External ID field (Account:Legacy_Account_ID__c) rather than standard Account ID.
5
Run operation and analyze output log files
Service Contract records are created in Salesforce linked to appropriate parent Accounts
Post-execution audit ensures all rows succeeded and errors are isolated for remediation.

Key Concept

Relating Child Records via External ID in Data Loader Mass Operations
Question 5Question →

An organization requires a bulk cleanup of 500,000 obsolete custom log records while maintaining strict data governance compliance. What is the correct sequence of administrative steps to safely back up the data and permanently purge the records using Salesforce native tools and Data Loader?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of operations is: 1) Generate and download a full offline backup using Data Export Service, 2) Assign the 'Bulk API Hard Delete' permission, 3) Export a CSV file containing the target Record IDs, 4) Execute a Hard Delete operation in Data Loader with Bulk API enabled, and 5) Monitor the Bulk API Job status page and review log files.
Enterprise data governance dictates that full offline backups must be generated before executing mass deletion jobs. Next, administrative permissions for 'Bulk API Hard Delete' must be granted. The administrator then extracts the exact Record IDs into a CSV file. Using Data Loader with the Bulk API, the Hard Delete operation is executed to bypass the Recycle Bin. Finally, auditing the Bulk API Monitoring page and success/error logs ensures complete processing verification.

Step-by-Step Solution

1
Perform data backup.
A complete data backup zip archive is created and stored offline.
Data governance policies require securing a complete backup before performing destructive mass operations.
2
Configure administrative security permissions.
The user is granted the 'Bulk API Hard Delete' system permission.
Hard delete capability is restricted by default and must be explicitly enabled on the user's profile or permission set.
3
Extract target record identifiers.
A CSV file containing the exact Record IDs of the records to purge is generated.
Data Loader mass deletion operations require a CSV file specifying the 15-character or 18-character Record IDs.
4
Run Hard Delete in Data Loader.
Target records are deleted immediately without being sent to the Recycle Bin.
Using Bulk API with Hard Delete enabled purges high-volume data asynchronously without filling the Recycle Bin storage.
5
Audit job execution.
Completion status and error logs are verified in Salesforce Setup.
Reviewing Bulk API job monitoring logs validates that all 500,000 records processed successfully without batch failures.

Key Concept

Mass Data Operations and Hard Deletion Sequence
Estimated Time:3m 0s
Question 6Question →

An administrator at Summit Logistics needs to configure a specialized sales pipeline for a new Consulting service line requiring custom opportunity stages. Place the following administrative steps in the correct sequence required to successfully set up and deploy this sales process.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of administrative steps is: 1) Create or update the stage picklist values on the Opportunity object, 2) Create a new Sales Process and select the appropriate stage picklist values, 3) Create a new Opportunity Record Type and link it to the newly created Sales Process, and 4) Assign the new Opportunity Record Type to the appropriate user profiles.
Configuring a custom sales process on the Opportunity object requires following a strict dependency sequence: custom stage picklist values must first exist on the Opportunity object, followed by creating the Sales Process to group those stages. Next, the Opportunity Record Type is created and linked to that Sales Process. Finally, access to the new Record Type must be granted via profile assignments or permission sets.

Step-by-Step Solution

1
Add necessary stage values to the Opportunity object.
Custom stage picklist values become available at the object level.
Sales Processes can only incorporate stages that already exist as picklist values on the Opportunity object.
2
Configure the Sales Process.
A specific sequence of opportunity stages is defined for the consulting business line.
The Sales Process determines which stage picklist values are available for opportunities using this process.
3
Create the Opportunity Record Type.
The Record Type is created and bound to the created Sales Process.
Opportunity Record Types require selecting a Sales Process to manage stage picklist display.
4
Assign Record Type access to users.
Target users gain access to create opportunities using the new sales process and record type.
Without profile or permission set assignment, users cannot view or select the new record type.

Key Concept

Opportunity Sales Process and Record Type configuration dependency chain
Question 7Question →

An administrator needs to customize the items available in the navigation bar for a custom Lightning App accessed via the Salesforce Mobile App. What is the correct sequence of steps to configure these navigation items in Setup?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order to customize navigation items for a Lightning App in the Salesforce Mobile App is: 1) Access App Manager in Setup, 2) Edit the desired Lightning App, 3) Select Navigation Items from App Settings, 4) Add items to the Selected Items list, and 5) Click Save.
Configuring mobile navigation for a Lightning App requires entering App Manager in Setup, editing the targeted Lightning App, selecting Navigation Items from the left-hand panel, choosing the required items into the Selected Items box, and saving the changes.

Step-by-Step Solution

1
Open Setup and search for App Manager.
The App Manager tool appears in the Quick Find results.
App Manager is the central hub for managing Lightning App configurations.
2
Find the relevant Lightning App and click Edit.
The Lightning App Builder settings menu opens.
App Settings must be edited to change navigation items.
3
Select the Navigation Items tab.
Dual listboxes showing Available Items and Selected Items are displayed.
This section manages which tabs/objects are included in the app.
4
Choose items and move them to Selected Items.
The navigation list reflects the chosen items in order.
Selected Items dictate the navigation items visible in the Salesforce Mobile App.
5
Save the configuration.
Changes take effect for all users assigned to the app.
Saving commits the changes to the app settings.

Key Concept

Customizing Lightning App Navigation for Salesforce Mobile
Question 8Question →

A Salesforce Administrator needs to execute a bulk hard delete of obsolete log records using Data Loader to ensure they bypass the Recycle Bin and free up storage immediately. Arrange the necessary configuration and execution steps in the correct chronological order.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with exporting target Record IDs into a CSV file, ensuring the required 'Bulk API Hard Delete' permission is assigned, enabling Bulk API settings in Data Loader for Hard Delete, and finally executing the operation while verifying the output logs.
To purge records permanently using Data Loader, an administrator must first identify and export the target Record IDs. Next, security administrative requirements must be met by ensuring the user has the 'Bulk API Hard Delete' permission. Then, Data Loader must be set up to use the Bulk API, which enables the Hard Delete option. Finally, running the process with the prepared CSV file completes the operation and allows verification via success logs.

Step-by-Step Solution

1
Extract Target Record IDs
A CSV file is generated containing the Record IDs of the obsolete records to be purged.
Data Loader operations require a CSV file with valid Salesforce Record IDs to target specific records for deletion.
2
Verify User Permissions
The user account possesses the 'Bulk API Hard Delete' system permission.
Salesforce restricts hard deletion capabilities; the Bulk API Hard Delete administrative permission must be active for the user performing the task.
3
Configure Data Loader for Hard Delete
Data Loader is configured to use Bulk API with Hard Delete enabled.
Hard deletion is only supported when Data Loader uses the Bulk API rather than the standard SOAP API.
4
Run Hard Delete and Audit Logs
The records are permanently removed from Salesforce without entering the Recycle Bin, verified via success log CSV.
Executing the operation processes the batch, and examining the success log verifies complete execution without errors.

Key Concept

Data Loader Mass Operations and Hard Delete Configuration
Estimated Time:1m 30s
Question 9Question →

A Service Cloud administrator at a global telecommunications company is auditing the automated processing sequence for incoming customer support tickets created via Web-to-Case. Arrange the following Salesforce case automation features in the exact order in which they are evaluated by the system upon case creation.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct execution order is: 1) System and custom Validation Rules, 2) Case Assignment Rules, 3) Case Auto-Response Rules, and 4) Case Escalation Rules.
Upon case creation, Salesforce executes automation in a predefined sequence: Validation Rules verify data integrity, Case Assignment Rules route ownership, Case Auto-Response Rules dispatch customer communications, and Case Escalation Rules set SLA escalation targets.

Step-by-Step Solution

1
Identify the data entry validation phase.
Validation Rules run first to confirm record data integrity before processing.
Salesforce validates all field inputs before running downstream record routing or automation.
2
Identify record routing and ownership assignment.
Case Assignment Rules evaluate next to determine owner assignment (User or Queue).
Ownership must be established prior to sending confirmation notifications or setting SLA timers.
3
Identify customer communication automation.
Case Auto-Response Rules evaluate third to send the customer an automated email.
Auto-response templates depend on case attributes and owner information established in prior steps.
4
Identify SLA timer and escalation configuration.
Case Escalation Rules evaluate fourth to establish escalation actions and timers.
Escalation logic relies on the finalized case owner, status, and business hours settings.

Key Concept

Salesforce Case Automation Order of Execution
Question 10Question →

A Salesforce Administrator needs to configure automated duplicate control for a custom object named Financial Account. The solution must block creation of duplicate records based on custom matching criteria and report duplicates when records are updated. In what exact order should the administrator perform these steps to successfully configure, activate, and verify the duplicate management setup?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence is: 1) Create the custom Matching Rule, 2) Activate the Matching Rule to compile matching keys, 3) Create the Duplicate Rule referencing the active Matching Rule and configuring Block/Report actions, 4) Activate the Duplicate Rule, and 5) Test record creation to verify enforcement.
The configuration of Salesforce Duplicate Management follows a strict dependency hierarchy: Matching logic must be defined (Matching Rule) and indexed (Matching Rule Activation) before enforcement rules can consume it (Duplicate Rule Creation & Activation), followed by end-to-end verification (Testing).

Step-by-Step Solution

1
Define Matching Criteria
Custom Matching Rule is created with specific field matching logic.
Matching rules define how duplicates are identified before any duplicate rule enforcement actions can be configured.
2
Activate Matching Rule
Salesforce generates indexing keys for duplicate detection.
Salesforce requires matching rules to be activated so that matching keys are indexed across existing and new records.
3
Configure Duplicate Rule
Duplicate Rule binds the matching rule to specific execution actions (Block on Create, Allow/Report on Edit).
Duplicate rules define what happens when a match is detected during record operations.
4
Activate Duplicate Rule
Duplicate Rule becomes live in the Salesforce organization.
Unactivated duplicate rules will not perform evaluation during data manipulation.
5
Verify duplicate enforcement
System blocks creation of a matching Financial Account record.
Testing validates that both the matching logic and enforcement actions function as required under business requirements.

Key Concept

Salesforce Duplicate Management Lifecycle & Key Indexing
Question 11Question →

An administrator needs to implement a custom sales pipeline for a newly established High-Volume Renewals team requiring specialized opportunity stages. What is the correct sequence of administrative steps to configure and deploy this custom sales pipeline?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of administrative steps is: 1) Add the required new Stage picklist values to the Opportunity object, 2) Create a new Sales Process and select the specific subset of Opportunity stages, 3) Create a new Opportunity Record Type and associate it with the Sales Process, and 4) Assign the new Opportunity Record Type and corresponding Page Layout to target user profiles.
Configuring custom opportunity stages in Salesforce follows a strict dependency order: master stage picklist values must be defined first so they are selectable in a Sales Process. Next, the Sales Process must be created to define the stage pipeline. Then, an Opportunity Record Type is created and assigned to that Sales Process. Finally, the Record Type and Page Layout are assigned to user profiles to enable end-user access.

Step-by-Step Solution

1
Add custom Stage picklist values to the Opportunity object
New stage values with defined Type, Probability, and Forecast Category are available in the master picklist.
Sales processes can only incorporate stages that already exist on the Opportunity object.
2
Create a custom Sales Process
A specific sequence of stages is defined for the High-Volume Renewal pipeline.
Opportunity Record Types for sales require a Sales Process to govern which stage picklist values are available.
3
Create an Opportunity Record Type linked to the Sales Process
The record type is created and bound to the customized stage pipeline.
Record types link the business process (Sales Process) to page layouts and profile access.
4
Assign the Record Type and Page Layout to user profiles
End users gain access to create and manage opportunities using the new sales process.
Without profile assignment, users cannot view or select the new record type when creating opportunities.

Key Concept

Sales Process and Record Type configuration dependency sequence in Salesforce
Question 12Question →

A Salesforce Administrator needs to configure a custom Service Level Agreement (SLA) management workflow for a support organization. What is the correct sequence of steps to configure and apply an Entitlement Process with Milestones to customer cases?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps is: 1) Create the required Milestone types in Setup; 2) Create a new Entitlement Process; 3) Add Milestones to the Entitlement Process and configure time triggers and Milestone Actions; 4) Activate the Entitlement Process; 5) Create an Entitlement record for the customer account and assign the activated Entitlement Process to it.
Configuring Entitlement Management in Salesforce follows a strict logical sequence: master Milestone types must exist before building an Entitlement Process; Milestones and actions are configured within the process draft; the process must be activated before assignment; and finally, the activated process is assigned to customer Entitlement records.

Step-by-Step Solution

1
Define Milestone Types
Milestone master records are created in Setup.
Milestone types (e.g., First Response, Resolution Time) must be created in Salesforce Setup before they can be selected within an Entitlement Process.
2
Create Entitlement Process
An Entitlement Process structure is defined.
The base Entitlement Process holds the overarching entry criteria, exit criteria, and business hours rules.
3
Configure Milestones and Milestone Actions
Specific SLA metrics and automated warning or violation actions are attached to the process.
Milestone types are added into the process alongside target timeframes, recurrence types, and workflow actions.
4
Activate the Entitlement Process
The Entitlement Process becomes active and ready for assignment.
Draft Entitlement Processes cannot be associated with Entitlement records; explicit activation is required.
5
Assign Process to Customer Entitlement
Cases linked to the Entitlement automatically run against the defined SLA Milestones.
Associating the activated Entitlement Process with customer-specific Entitlement records links incoming customer cases to the SLA rules.

Key Concept

Entitlement Process and Milestone Implementation Sequence
Question 13Question →

A Salesforce administrator needs to configure an automated weekly backup of standard and custom object records along with file attachments for compliance archiving using the native Data Export Service. What is the correct chronological sequence of steps the administrator must take in Setup to establish this recurring schedule?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence is: 1) Navigate to Setup, search 'Data Export', and click 'Schedule Export'; 2) Set scheduling parameters such as Frequency, Dates, and Start Time; 3) Configure file backup options for images, attachments, and files; 4) Select object checkboxes and click 'Save'.
To set up a scheduled data backup, an administrator first navigates to Setup > Data Export and selects 'Schedule Export'. Next, the administrator defines the frequency and time window parameters, configures file attachment inclusion options, and finally selects the standard/custom object data to include before saving the job.

Step-by-Step Solution

1
Open the Data Export setup tool.
Navigates to the native Data Export configuration screen.
All native scheduled data export definitions originate within the Data Export node in Setup.
2
Define export frequency and execution time.
Establishes when Salesforce will generate export zip files automatically.
The system requires time boundaries before object selections are made.
3
Select binary attachment export options.
Includes document attachments and CRM files in export archives.
Binary attachment options are configured prior to object table selections on the page layout.
4
Select data entities and save the schedule.
Commits the scheduled recurring export job to the system queue.
Final object selection completes the configuration process.

Key Concept

Data Export Service Scheduling
Question 14Question →

A Service Cloud administrator at a smart-home security company is auditing the system order of execution for incoming support tickets created via Web-to-Case. In what sequential order does Salesforce evaluate and execute the case automation rules and processes upon record creation?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of execution is: 1) Case Assignment Rules, 2) Case Auto-Response Rules, 3) Record-Triggered Flows and Workflow Rules, and 4) Case Escalation Rules.
In Salesforce, incoming cases follow a strict order of execution: Case Assignment Rules run first to set record ownership, followed immediately by Case Auto-Response Rules to send targeted confirmation emails. Afterwards, Record-Triggered Flows and Workflow Rules execute custom business logic, and finally Case Escalation Rules evaluate criteria to monitor SLAs and schedule future escalation actions.

Step-by-Step Solution

1
Determine initial record ownership routing.
Case Assignment Rules execute first.
Ownership (queue or individual user) must be established before automated customer notifications or workflow logic fire.
2
Determine automated customer response messaging.
Case Auto-Response Rules execute second.
Auto-response rules fire immediately following assignment to ensure confirmation emails reference the updated case context.
3
Execute custom business process logic.
Record-Triggered Flows and Workflow Rules execute third.
Custom field updates, tasks, and outbound messages are processed after standard system routing rules complete.
4
Evaluate Service Level Agreement (SLA) escalation criteria.
Case Escalation Rules evaluate fourth.
Escalation rules evaluate near the end of the order of execution to schedule time-based SLA actions based on the saved case attributes.

Key Concept

Salesforce Case Automation Order of Execution
Estimated Time:1m 30s
Question 15Question →

An administrator needs to deploy a customized mobile experience with specific navigation tabs for field representatives using the Salesforce Mobile App. Order the sequence of administrative steps required to build, configure, and expose this tailored Lightning App navigation experience to the targeted mobile users.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct administrative sequence begins with accessing App Manager to edit the custom Lightning App, configuring the Supported Form Factors to include 'Desktop and Phone', adding and ordering the desired items under Navigation Items, assigning the designated User Profiles under User Profiles settings, and finally directing users to select the Lightning App within the Salesforce Mobile App Launcher.
The proper administrative order requires modifying the Lightning App in App Manager, setting the form factor to include Phone, customizing navigation items, assigning user profiles, and having users select the app via the mobile App Launcher.

Step-by-Step Solution

1
Access App Manager in Setup
Opens configuration options for the Lightning App.
Customizing app-level mobile navigation begins in App Manager.
2
Set Supported Form Factors to include Phone
Enables the app for Salesforce Mobile App users.
Apps restricted to Desktop will not appear in the mobile App Launcher.
3
Select and sequence Navigation Items
Defines the exact navigation tabs available in the mobile app view.
Navigation Items dictate the mobile navigation bar content for that specific Lightning App.
4
Assign User Profiles
Grants app access to the designated target audience.
Users cannot view or switch to a Lightning App without profile assignment.
5
Select the Lightning App in Mobile App Launcher
Displays the custom tab navigation on the user's mobile device.
Users must actively switch to the configured app in the mobile app launcher to view its custom navigation layout.

Key Concept

Salesforce Mobile App Navigation and Custom Lightning App Deployment
Question 16Question →

A Salesforce Administrator needs to create an autolaunched flow that updates a group of related Case records when an Account status changes. To follow Salesforce automation best practices and prevent governor limit violations, in what order should the administrator arrange the Flow Builder elements?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of Flow Builder elements for a bulkified record processing pattern is: 1) Get Records to query records, 2) Loop to iterate through the collection, 3) Assignment to update field values on the current loop item, 4) Assignment to add the current loop item to a new output collection, and 5) Update Records after the loop path to perform a bulk update on the output collection.
Following Salesforce design standards, bulkified flow logic requires querying records first with Get Records, looping over the collection with a Loop element, updating field values on the loop item using an Assignment element, adding the updated item to an output collection with a second Assignment element, and executing a single Update Records element outside the loop container.

Step-by-Step Solution

1
Retrieve data using a Get Records element
The target Case records are stored in a collection variable
Data must be retrieved prior to iteration and field assignments.
2
Iterate through records using a Loop element
Each record in the collection is made available sequentially as a loop item
Looping allows operations to be applied to each individual record item.
3
Update record fields using a primary Assignment element
Field values on the current record item are updated in temporary memory
Field changes must be assigned to the record item variable inside the loop.
4
Collect modified records using a secondary Assignment element
The current modified record item is appended to a new collection variable
Building an updated collection enables a single bulkified DML call.
5
Commit updates to the database using an Update Records element outside the loop
All records in the collection are saved to Salesforce in one database call
Placing database write operations outside loop structures adheres to governor limit best practices.

Key Concept

Bulkified Flow Design and Element Order
Question 17Question →

An administrator is configuring a new Workflow Rule on the Opportunity object. Arrange the following steps in the correct chronological order for setting up and executing a Workflow Rule.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for configuring and activating a Workflow Rule is: first, define the target object and evaluation criteria; second, set the rule criteria filters or formula; third, add automated workflow actions; and fourth, activate the workflow rule.
Creating a Workflow Rule follows a logical administrative flow: specifying the object and evaluation timing, setting the rule criteria, assigning automated actions (such as field updates or email alerts), and finally activating the rule so it processes incoming record changes.

Step-by-Step Solution

1
Select object and evaluation criteria.
Establishes which record types and edit events trigger evaluation.
Evaluation settings are required at the start of rule creation.
2
Configure filter criteria or formula.
Defines the precise conditions required for the rule to evaluate to true.
Criteria must be set before actions can be associated with those conditions.
3
Configure associated actions.
Attaches field updates, email alerts, tasks, or outbound messages to the rule.
Actions define what work Salesforce automates when criteria are met.
4
Activate the rule.
Enables the rule for live record processing.
Inactive rules do not evaluate or execute actions on record changes.

Key Concept

Workflow Rule Configuration Sequence
Question 18Question →

A company requires an automated batch process to calculate the total contract value of all active child contracts linked to an account and update the parent account record. Order the Flow elements from first to last to accomplish this while maintaining bulkification best practices.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence is: Get Records element to query all active Contract records related to the Account -> Loop element to iterate over the collection of retrieved Contract records -> Assignment element to add the current Contract's amount to a running total variable -> Update Records element to update the parent Account with the final calculated total.
The proper sequence for bulkified record processing in Flow Builder is: retrieve records (Get Records), iterate through the records (Loop), perform in-memory variable calculations (Assignment inside the loop), and commit updates to the database once iteration finishes (Update Records).

Step-by-Step Solution

1
Query the dataset using Get Records.
Collection variable is populated with target Contract records.
Data must be retrieved before iteration can occur.
2
Begin iteration with a Loop element.
Flow iterates through each item in the collection variable sequentially.
Allows element-level operations on each item.
3
Aggregate values using an Assignment element inside the loop.
The running total variable accumulates values across all loop iterations.
In-memory variable manipulation avoids SOQL and DML limit violations.
4
Persist changes using an Update Records element after the loop completes.
Parent Account record is updated with the calculated total in a single DML operation.
Placing data operations outside the loop ensures compliance with Salesforce governor limits.

Key Concept

Flow Builder Bulkification and Data Manipulation Sequencing
Question 19Question →

An administrator at Northern Trail Outfitters needs to establish a specialized sales pipeline with customized opportunity stages for a newly launched Consulting Services division. What is the correct sequence of administrative steps required to configure and deploy this custom sales pipeline in Salesforce?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of administrative steps is: 1) Add any required new stage values to the Stage picklist field on the Opportunity object, 2) Create a new Sales Process and select the specific stages, 3) Create a new Opportunity Record Type and associate it with the Sales Process, and 4) Assign the new Record Type and Page Layout to the appropriate user profiles.
Configuring a new sales pipeline requires a specific dependency chain in Salesforce. First, stage picklist values must exist on the Opportunity object. Second, a Sales Process must be created to select which stages belong to this sales lifecycle. Third, an Opportunity Record Type must be created and linked to the Sales Process. Finally, access must be granted by assigning the Record Type and Page Layout to user profiles.

Step-by-Step Solution

1
Add custom picklist values to the Opportunity Stage field.
New stage values are available at the object level.
Sales Processes rely on pre-existing stage values on the Opportunity object.
2
Create the Sales Process.
A specific lifecycle subset of opportunity stages is configured.
Sales Processes determine which stage values appear in the stage picklist.
3
Create the Opportunity Record Type and associate the Sales Process.
The Record Type is linked to the designated Sales Process.
Opportunity Record Types require an existing Sales Process upon creation.
4
Assign the Record Type and Page Layout to Profiles.
Users receive authorization and page formatting for the new pipeline.
Profile assignments dictate record type accessibility and layout display.

Key Concept

Sales Process and Opportunity Record Type Setup Sequence
Question 20Question →

An administrator needs to build a Flow that updates a group of expired Asset records for a target Account and creates a single notification Task for the Account owner. To ensure the flow executes efficiently without exceeding Salesforce governor limits, in what sequential order should the administrator execute the Flow elements?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with retrieving the expired Asset records via a Get Records element, passing the collection into a Loop element, updating field values and adding records to a bulk collection via an Assignment element inside the loop, performing a single Update Records DML operation on the collection outside the loop, and finally creating the summary Task record outside the loop.
The correct order follows Salesforce Flow design best practices for bulkification. Data retrieval (Get Records) must occur first. Next, the collection is passed into a Loop element. Inside the loop, an Assignment element modifies field values in memory and appends the modified item to an output collection variable without executing DML. After the loop completes, a single Update Records element bulk-updates all Asset records at once. Finally, a Create Records element generates the summary Task.

Step-by-Step Solution

1
Query the target records using a Get Records element.
Stores all matching expired Asset records into a record collection variable.
Data must be retrieved from the database before it can be iterated or modified in memory.
2
Pass the collection variable to a Loop element.
Begins iteration over each individual Asset record in the collection.
Looping allows processing logic to be applied to each item sequentially.
3
Use an Assignment element inside the loop body.
Modifies record fields in memory and adds the updated loop item to a separate collection variable for bulk update.
Staging updates in memory prevents executing DML statements inside a loop, adhering to bulkification standards.
4
Place an Update Records element after the loop completes ('After Last Item').
Executes a single DML update statement for all modified Asset records in the collection.
Bulkifying DML outside the loop avoids hitting the SOQL/DML governor limit of 150 DML statements per transaction.
5
Execute a Create Records element outside the loop.
Creates a single Task record assigned to the Account owner.
Generates the required notification task after all Asset updates have successfully processed.

Key Concept

Bulkification in Flow Builder: Avoiding DML and SOQL elements inside loops
Page 1 / 7Next
All practice questions — Salesforce Certified Administrator | Examkin