Examkin

All practice questions

1784 questions

All types1,784Multiple choice918Multiple select587Matching142Ordering137
Question 1281Question →

A Salesforce Administrator at AeroJet Logistics is tasked with configuring a new custom Lightning Service Console application for the tier-1 support desk. The console application must utilize tab-based navigation, include the Omni-Channel utility item in the bottom bar, define Account records as primary tabs with Case records opening as subtabs, and be assigned to the Support Specialist profile. In what sequence should the administrator perform the configuration steps within the Lightning App Wizard in Setup?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for configuring the Lightning Service Console application in the Lightning App Wizard is: 1) Launch the wizard in App Manager and enter app details, 2) Select Console Navigation under App Options, 3) Add the Omni-Channel component on the Utility Items screen, 4) Configure navigation rules for primary tabs and subtabs, and 5) Assign the app to the Support Specialist profile on the User Profiles screen.
When configuring a Service Console app using Salesforce Setup's App Manager, the wizard follows a strict multi-step sequence: defining basic app details, selecting the Console Navigation option, configuring utility bar items like Omni-Channel, setting tab and subtab navigation rules, and finally assigning profile access to target users.

Step-by-Step Solution

1
Initiate Lightning App Creation
App Manager opens the wizard where basic details like name, developer name, and branding are entered.
Creating a new Lightning app requires initializing the application metadata first.
2
Set App Options and Navigation Style
The navigation style is locked into Console Navigation instead of Standard Navigation.
Choosing Console Navigation determines the layout architecture for tabs, subtabs, and split views.
3
Configure Utility Bar Components
The Omni-Channel utility widget is placed in the console application bottom bar.
Utility items are configured after general app settings to supply background productivity tools.
4
Set Tab Navigation Rules
Account records open as primary tabs, while Case records open as subtabs underneath their parent Account tab.
Navigation rules dictate record relationship hierarchy inside the console workspace.
5
Assign Profile Access
The app is granted and made visible to users with the Support Specialist profile.
Profile assignment controls user visibility and security access to the newly built console app.

Key Concept

Lightning Service Console App Wizard Sequence
Question 1282Question →

An organization requires an approval process for custom Project records. Each Project record specifies a custom lookup field named 'Project Advisor' (pointing to the User object). When a Project is submitted for approval, the approval request must be routed directly to the specific user designated in that record's 'Project Advisor' field. Which configuration option should the administrator select in the approval step assignment?

Show answer & explanation

Answer: Select 'Related User' as the approver type and choose the 'Project Advisor' field.

Answer

Select 'Related User' as the approver type and choose the 'Project Advisor' field.
In Salesforce approval processes, setting the step approver to 'Related User' enables dynamic routing by referencing any User lookup field located on the record submitted for approval, such as a custom 'Project Advisor' field.

Step-by-Step Solution

1
Identify the requirement for dynamic approver assignment based on a record custom lookup field.
Recognize that the approver varies per record depending on the value stored in 'Project Advisor'.
Static user assignment or static queue assignment will not satisfy per-record dynamic routing.
2
Evaluate standard Salesforce Approval Step assignment options.
Determine that the 'Related User' option specifically allows selecting standard or custom user lookup fields present on the object being submitted.
'Related User' dynamically evaluates the lookup field on the target record at the moment of step entry.

Key Concept

Dynamic Approval Routing via Related User Lookup Fields
Estimated Time:1m 30s
Question 1283Question →

A Salesforce Administrator is configuring automated business processes for Opportunity management using Process Builder. When an Opportunity record reaches the 'Closed Won' stage, several actions must be triggered immediately.

Which of the following actions can be performed directly as native immediate actions in Process Builder without calling Apex code or invoking a Flow? (Select TWO answers.)

Select all that apply

Show answer & explanation

Answer: Create a new custom Renewal Opportunity record and populate fields using values from the triggering Opportunity.; Submit the triggering Opportunity record into an active approval process.

Answer

Process Builder can directly create new records and submit records for approval. It cannot delete records or perform outbound web service callouts without calling additional tools like Flow or Apex.
Process Builder natively provides built-in action types to create new records and submit records for approval directly from the process canvas without needing custom code or sub-flows.

Step-by-Step Solution

1
Evaluate native Process Builder immediate action types
Confirm that 'Create a Record' and 'Submit for Approval' are standard built-in action types in Process Builder.
Process Builder supports native immediate actions such as creating records, updating records, posting to Chatter, sending email alerts, submitting for approval, and triggering quick actions.
2
Evaluate platform capabilities and limitations for complex operations
Identify that record deletion and outbound web service callouts are not available as standard Process Builder actions.
Deleting records requires Flow Builder (using a Delete Records element) or Apex. Making external HTTP REST callouts requires Apex code with @InvocableMethod or an outbound integration framework.

Key Concept

Process Builder Native Capabilities and Platform Limitations
Question 1284Question →

A global logistics firm is deploying the Salesforce Integration with Outlook for its dispatch operations team. The manager requests that dispatchers be able to organize Lightning Email Templates into shared folders and access public template folders directly from the Outlook integration pane. Which two administrative actions must the Salesforce administrator take to fulfill these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Enable Folders and Enhanced Sharing for Email Templates in Salesforce Setup.; Assign a permission set containing the Manage Public Lightning Email Templates system permission to users who need folder sharing management capabilities.

Answer

The administrator must enable Folders and Enhanced Sharing for Email Templates in Setup and assign a permission set with the Manage Public Lightning Email Templates system permission to users managing template folders.
Enabling 'Folders and Enhanced Sharing' in Setup provides the infrastructure for organizing Lightning Email Templates into shared folders, while assigning a Permission Set with 'Manage Public Lightning Email Templates' gives designated users administrative rights over public folder sharing.

Step-by-Step Solution

1
Identify the required feature settings for public folder sharing of Lightning Email Templates.
Recognize that 'Folders and Enhanced Sharing' must be enabled in Setup to move beyond private or unfiled public folders.
Enhanced sharing provides folder-level security and permission management for Lightning Email Templates.
2
Determine the correct administrative permission model for granting folder management permissions.
Select the 'Manage Public Lightning Email Templates' system permission via a Permission Set rather than modifying user Profiles.
Permission sets adhere to the principle of least privilege by providing additive permissions without cluttering profile definitions.

Key Concept

Lightning Email Template Folder Sharing and Permissions
Estimated Time:1m 30s
Question 1285Question →

An administrator at Apex Global Solutions is configuring a complex multi-step Approval Process for high-value Quote records. Arrange the following execution stages in the exact order Salesforce performs them when a record is submitted for approval until final resolution.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct execution order is: 1) Evaluate overall approval process record entry criteria, 2) Execute Initial Submission Actions (lock record and send notifications), 3) Evaluate Step 1 entry criteria and assign approver, 4) Approver approves Step 1 to execute Step 1 Approval Actions, and 5) Evaluate Step 2 entry criteria, skip step if criteria are unmet, and execute Final Approval Actions.
The correct order follows Salesforce's standard execution lifecycle for approval processes: overall entry criteria evaluation occurs first, followed by Initial Submission Actions (such as record locking), then Step 1 criteria evaluation and assignment, Step 1 approval action execution upon approval, and finally evaluation of Step 2 entry criteria leading to Final Approval Actions when criteria are not met.

Step-by-Step Solution

1
Evaluate overall approval process entry criteria
Salesforce verifies if the submitted Quote record meets the top-level criteria to enter the approval process.
If entry criteria are not met, the record cannot enter the approval workflow.
2
Execute Initial Submission Actions
The record is locked by default, and initial submission email alerts or field updates are performed.
Initial submission actions establish the initial state of the record during evaluation.
3
Evaluate Step 1 entry criteria and assign approver
Salesforce checks Step 1 entry conditions and routes the approval request to the designated user or queue.
Each step maintains its own entry criteria and assignment logic.
4
Process Step 1 approval decision
The approver approves the request, which triggers Step 1 specific approval actions.
Step approval actions execute before moving on to evaluate subsequent approval steps.
5
Evaluate Step 2 criteria and finalize approval
Step 2 entry criteria fail, causing Salesforce to execute configured 'else' behavior (Approve record) and fire Final Approval Actions.
Final approval actions perform final field updates, send final notifications, and unlock the record.

Key Concept

Approval Process Order of Execution and Step Evaluation Lifecycle
Estimated Time:2m 0s
Question 1286Question →

A Service Cloud administrator at an aviation maintenance enterprise is setting up automated case handling for urgent Aircraft-on-Ground (AOG) inquiries created via Web-to-Case. To ensure proper case processing, in what order does Salesforce execute case automation rules and processes upon record creation?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of execution upon Case creation is: Case Assignment Rules evaluate to set ownership, followed by Case Auto-Response Rules to send customer emails, then Record-Triggered Flows/Workflow Rules for after-save processing, and finally Case Escalation Rules to set up SLA escalation timers.
In the standard Salesforce order of execution for Case creation, case-specific automation rules execute in a strict sequence: Assignment Rules run first to set ownership, Auto-Response Rules run second to send auto-reply emails to submitters, Record-Triggered Flows and Workflow Rules execute third to perform custom logic/field updates, and Escalation Rules evaluate fourth to schedule SLA time-based escalation actions.

Step-by-Step Solution

1
Identify the initial case routing step in Salesforce order of execution.
Case Assignment Rules execute first to assign case ownership to the correct queue or user.
Ownership must be established before sending auto-responses or evaluating further automation.
2
Determine the step that generates customer notification upon case creation.
Case Auto-Response Rules execute second.
Auto-response rules rely on the assignment results to choose the appropriate email template and sender address.
3
Identify when standard process automation (Flows/Workflows) runs.
Record-Triggered Flows and Workflow Rules execute after Auto-Response rules.
Process automation acts on the saved record state after standard case creation rules complete.
4
Identify when SLA escalation monitoring is scheduled.
Case Escalation Rules execute last among the case automation rules.
Escalation criteria are evaluated after all initial field updates and assignment steps are finalized.

Key Concept

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

Veloce Fleet Technologies is introducing a new subscription-based telemetry sales unit alongside its existing custom vehicle engineering services. The telemetry sales team requires a streamlined 4-stage sales pipeline (Qualification, Evaluation, Contracting, Closed Won/Lost), whereas the engineering team uses an 8-stage pipeline. The administrator creates a new Opportunity record type named 'Telemetry Sales', but sales representatives report that all 12 active organizational opportunity stages still appear when creating records. Which administrative action is required to ensure that only the 4 specified opportunity stages are available for the Telemetry Sales record type?

Show answer & explanation

Answer: Create a new Sales Process containing only the 4 required stages, and assign it to the Telemetry Sales record type.

Answer

Create a new Sales Process containing only the 4 required stages, and assign it to the Telemetry Sales record type.
In Salesforce Core Administration, Opportunity Stages are tied to business processes via a Sales Process. To display a specific subset of opportunity stages on a given record type, an administrator must first create a Sales Process containing those stages and then link that Sales Process when creating or configuring the Opportunity record type.

Step-by-Step Solution

1
Create a Sales Process
A dedicated Sales Process defines the specific subset of Opportunity Stages used for this business unit.
Opportunity stage values are unique standard picklists tied directly to Sales Processes rather than standard record type picklist administration.
2
Associate the Sales Process with the Record Type
The Telemetry Sales record type displays only the 4 selected stages in the Sales Process.
A record type on the Opportunity object requires a Sales Process assignment to determine which stage picklist values are available to users.

Key Concept

Sales Processes and Opportunity Stage Picklist Management
Estimated Time:1m 30s
Question 1288Question →

When bulkifying a flow to process multiple records, an administrator uses a Loop element to iterate over a record collection. Which Flow Builder element should be placed inside the loop to modify field values on the current record item in memory prior to updating the database outside the loop?

Show answer & explanation

Answer: Assignment element

Answer

The Assignment element is the correct choice to update field values on record variables in memory inside a loop.
The Assignment element sets or updates values in flow variables and record fields strictly within transaction memory. This allows administrators to prepare updated record values inside a loop, collect them into a collection variable, and perform a single Update Records operation after the loop finishes.

Step-by-Step Solution

1
Identify the constraint
Operations inside a loop must avoid database interactions (SOQL/DML) to prevent reaching governor limits.
Salesforce enforces strict limits on DML statements per transaction.
2
Select the appropriate in-memory element
Use an Assignment element to modify variable or field values during loop iteration.
Assignment elements modify data in temporary memory without committing changes directly to the database.

Key Concept

Flow Bulkification and Assignment Elements
Question 1289Question →

An administrator is configuring an approval process for custom discount requests on Opportunity records. Which TWO standard automated actions can be added as Initial Submission Actions within the approval process? (Choose 2 options.)

Select all that apply

Show answer & explanation

Answer: Send an Email Alert to notify the opportunity owner's manager; Execute a Field Update to change the approval status field on the record

Answer

The correct automated actions are sending an Email Alert and executing a Field Update.
Salesforce approval processes allow administrators to configure four standard automated actions: Email Alerts, Field Updates, Tasks, and Outbound Messages. Therefore, sending an email alert and executing a field update are both valid initial submission actions.

Step-by-Step Solution

1
Identify the standard automated actions supported by Salesforce Approval Processes.
Salesforce approval processes support four standard types of actions: Task, Email Alert, Field Update, and Outbound Message.
Approval processes allow automated actions at various stages, including Initial Submission, Approval Steps, Final Approval, and Final Rejection.
2
Evaluate the choices against the four standard approval actions.
Email Alerts and Field Updates belong to the standard approval actions. Direct record creation and record deletion are not supported as standard approval actions.
Complex actions like creating records must be handled via Flow or Apex, not standard approval action types.

Key Concept

Standard Approval Actions
Question 1290Question →

A Salesforce Administrator at a global logistics firm is configuring an Account report to support an executive review of strategic client accounts. The executive team requires the report to list Accounts meeting all of the following requirements:
1. The Account Type must be either 'Technology Partner' OR the Annual Revenue must exceed 10,000,000.2.TheAccountRatingmustNOTbe′Inactive′.3.TheAccountMUSThaveatleastonerelatedOpportunitythatis′ClosedWon′withanAmountgreaterthan10,000,000. 2. The Account Rating must NOT be 'Inactive'. 3. The Account MUST have at least one related Opportunity that is 'Closed Won' with an Amount greater than 100,000.

The report builder currently has three standard field filters defined:
1. Type equals Technology Partner
2. Annual Revenue greater than 10000000
3. Rating not equal to Inactive

Which configuration of Filter Logic and Cross Filters should the administrator apply to meet the requirements correctly?

Show answer & explanation

Answer: Set the filter logic to (1 OR 2) AND 3, and add a Cross Filter configured as 'Accounts with Opportunities' filtered by Stage equals Closed Won AND Amount greater than 100000.

Answer

Set the filter logic to (1 OR 2) AND 3, and add a Cross Filter configured as 'Accounts with Opportunities' filtered by Stage equals Closed Won AND Amount greater than 100000.
The requirement asks for Accounts that satisfy (Type = 'Technology Partner' OR Annual Revenue > 10M)whilesimultaneouslyrequiringRating!=′Inactive′.Encapsulatingfilters1and2withinparenthesesas(1OR2)AND3correctlyreflectsthislogic.Furthermore,determiningwhetheranAccountpossessesrelatedOpportunityrecordsmeetingspecificcriteria(Stage=ClosedWonandAmount>10M) while simultaneously requiring Rating != 'Inactive'. Encapsulating filters 1 and 2 within parentheses as (1 OR 2) AND 3 correctly reflects this logic. Furthermore, determining whether an Account possesses related Opportunity records meeting specific criteria (Stage = Closed Won and Amount > 100k) requires a Cross Filter ('Accounts with Opportunities') with nested sub-filters.

Step-by-Step Solution

1
Analyze the Boolean logical requirements for the primary Account object field filters.
Requirements state that Type equals 'Technology Partner' OR Annual Revenue > $10,000,000 must be grouped together, and the result must be combined with Rating != 'Inactive'.
Without parenthesizing (1 OR 2), standard operator precedence would evaluate AND before OR, causing logic flaws.
2
Formulate the correct Boolean filter logic string.
The filter logic must be configured explicitly as (1 OR 2) AND 3.
This guarantees that an account matching either attribute (Type or Revenue) must also have a Rating other than Inactive.
3
Determine how to enforce the related object requirement (Accounts with Closed Won Opportunities > $100,000).
Add a Cross Filter on the Account report: 'Accounts with Opportunities', with secondary sub-filters: Stage equals Closed Won AND Amount > 100000.
Cross filters allow filtering parent records based on the presence, absence, or field values of related child records.

Key Concept

Report Filter Logic & Cross Filters
Question 1291Question →

A Salesforce Administrator is designing an autolaunched flow to update all child Contact records whenever a parent Account's status changes. To adhere strictly to bulkification best practices and prevent hitting governor limits, in what precise order should the administrator execute the Flow Builder elements?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct bulkified sequence begins by getting child Contact records into a collection, iterating through them with a Loop element, updating field values on the current item with an Assignment element, appending that item to a secondary collection with another Assignment element, and finally executing a single Update Records DML operation outside the loop.
The design pattern for bulkified Flow processing requires data retrieval (Get Records) prior to entering a loop, in-memory updates and staging (Assignment elements) inside the loop, and a single bulk write operation (Update Records) after the loop path completes.

Step-by-Step Solution

1
Retrieve child records before iteration
Child contacts are fetched in a single SOQL query call into a record collection.
Placing a Get Records element inside a loop causes governor limit violations (SOQL 101).
2
Iterate over the retrieved record collection
The flow evaluates one Contact record variable at a time in memory.
Looping allows row-by-row field assignment processing without database overhead.
3
Assign new field values
The current item variable in the loop receives updated values.
In-memory variable assignment does not consume DML governor limits.
4
Add updated item to target update collection
The secondary collection variable collects all staged updates.
Staging modified records in a secondary collection allows for a single bulk DML statement after iteration completes.
5
Perform DML update after loop execution finishes
All Contact updates persist to the database in a single transaction.
Executing DML outside the loop avoids hitting the 150 DML statements governor limit.

Key Concept

Bulkification in Flow Builder
Question 1292Question →

A Salesforce Administrator is constructing an autolaunched flow that iterates through a collection of Case records, updates the Case status, and generates a follow-up Task for each Case. Which TWO design practices must the administrator implement within Flow Builder to ensure bulkification and avoid hitting governor limits? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Use an Assignment element inside the loop to add modified Case records to a record collection variable, then execute a single Update Records element outside the loop.; Use an Assignment element inside the loop to populate Task record details into a record collection variable, then invoke a single Create Records element outside the loop.

Answer

The correct practices are using an Assignment element inside the loop to stage updated Case records in a record collection variable before performing a single Update Records call outside the loop, and using an Assignment element inside the loop to populate Task records into a collection variable before performing a single Create Records call outside the loop.
Bulkification in Flow Builder requires keeping database operations (SOQL queries and DML operations) outside of loop containers. Using Assignment elements within the loop allows the administrator to manipulate values and construct record collections in memory. Once all iterations complete, single DML elements (Update Records and Create Records) execute against the staged collection variables in a single transaction call.

Step-by-Step Solution

1
Analyze data manipulation and retrieval requirements within the flow loop
Identified that Case updates and Task creations must process multiple items in a collection.
Flows processing collections must adhere to Salesforce bulkification patterns to stay within transaction governor limits.
2
Evaluate record collection management using Assignment elements
Staging modifications and new records in collection variables inside the loop allows batch processing.
Assignment elements perform in-memory operations which do not count against DML or SOQL limits.
3
Place database operations (DML elements) outside the loop container
Single Create Records and Update Records elements process the entire collection at once.
Executing DML elements outside the loop consumes only one DML statement per collection batch.

Key Concept

Flow Bulkification and Loop Best Practices
Question 1293Question →

An administrator needs to automatically update a field on an Opportunity record whenever the Opportunity is created or updated, prior to the record being saved to the database. No other records or external systems need to be updated. Which flow configuration should the administrator select?

Show answer & explanation

Answer: Record-Triggered Flow configured for Fast Field Updates (Before-Save)

Answer

Record-Triggered Flow configured for Fast Field Updates (Before-Save)
Configuring a Record-Triggered Flow for Fast Field Updates (Before-Save) is the recommended best practice for updating fields on the record that launched the flow. It updates the record values before they are committed to the database, offering optimal performance.

Step-by-Step Solution

1
Identify the automation requirement target and timing.
The requirement is to update fields on the triggering Opportunity record itself before it is saved to the database.
Updates to the triggering record prior to database commit should be handled efficiently without additional DML operations.
2
Evaluate Salesforce flow trigger types.
Fast Field Updates (Before-Save Record-Triggered Flows) are optimized specifically for same-record updates before database save.
Before-save flows run up to 10 times faster than after-save flows because they do not cause extra database writes or trigger secondary order of execution steps.

Key Concept

Fast Field Updates vs. Actions and Related Records in Record-Triggered Flows
Question 1294Question →

A Salesforce Administrator at OmniTech Solutions is configuring a custom Lightning Service Console app for the customer support team. The business requirement states that when support agents open a Contact record from a related Case record, the Contact record must automatically open as a subtab under the parent Case primary tab rather than opening as a separate primary tab. Which configuration setting in the App Manager should the administrator adjust to satisfy this requirement?

Show answer & explanation

Answer: Configure Navigation Rules under the App Options in the App Manager to set Contact records to open as subtabs of Case.

Answer

Configure Navigation Rules under the App Options in the App Manager to set Contact records to open as subtabs of Case.
In Salesforce Lightning Console apps, Navigation Rules (configured in App Manager) explicitly define whether related records open as primary workspace tabs or subtabs under a parent record. Setting Contact records to open as subtabs of Case ensures agents remain focused on the primary Case context.

Step-by-Step Solution

1
Navigate to Setup and open App Manager.
Access the list of all configured Lightning and Classic apps in the org.
Console application settings, including tab behavior, are maintained centrally within the App Manager.
2
Edit the Lightning Service Console app and select Navigation Rules.
Open the navigation rule settings panel for workspace primary tabs and subtabs.
Navigation Rules determine whether related object records open independently as primary tabs or nested as subtabs under a parent record.
3
Set Contact records to open as subtabs of Case and save the changes.
Whenever an agent opens a Contact from a Case record, it automatically nests under that Case primary tab.
This directly fulfills the business requirement for streamlined console navigation and case workspace management.

Key Concept

Service Console Navigation Rules
Question 1295Question →

A Salesforce administrator at a telecommunications provider needs to load 65,000 Opportunity records from an external billing system into Salesforce. Which tool should the administrator use to perform this operation?

Show answer & explanation

Answer: Data Loader, because Opportunities are not supported by the Data Import Wizard and the record volume exceeds 50,000.

Answer

Data Loader should be used because Opportunities are not supported by the Data Import Wizard and the record volume exceeds 50,000.
Data Loader is required because the Data Import Wizard cannot import Opportunity records and has a maximum limit of 50,000 records per job, whereas 65,000 records are being loaded.

Step-by-Step Solution

1
Evaluate record volume requirements
The requirement specifies 65,000 records. Data Import Wizard is limited to 50,000 records, whereas Data Loader supports up to 5,000,000 records.
Record volume dictates tool selection boundaries in Salesforce data management.
2
Evaluate object support requirements
The requirement specifies the Opportunity object. Data Import Wizard supports Accounts, Contacts, Leads, Solutions, Campaign Members, and custom objects, but does NOT support Opportunities.
Object compatibility is a primary criterion when choosing between Data Import Wizard and Data Loader.
3
Select the correct data utility tool
Data Loader satisfies both the object requirement (Opportunities) and the volume requirement (65,000 records).
Only Data Loader meets both criteria for this administrative task.

Key Concept

Data Import Wizard vs Data Loader selection criteria based on record volume and object support.
Estimated Time:1m 0s
Question 1296Question →

An administrator at Ursa Major Solar is creating a report on Accounts to evaluate whether each individual record meets a specific threshold based on its Annual Revenue field. The calculated output must be displayed directly on each detail row in the report without creating a custom field on the Account object schema. Which reporting feature should the administrator use to fulfill this requirement?

Show answer & explanation

Answer: Create a row-level formula in the report builder to evaluate the Annual Revenue of each record.

Answer

Create a row-level formula in the report builder to evaluate the Annual Revenue of each record.
Row-level formulas in Salesforce reports allow administrators to write logic that evaluates each individual record row in the report dataset, satisfying the requirement without creating custom fields on the Account object.

Step-by-Step Solution

1
Identify the evaluation scope required by the scenario.
The requirement calls for a calculation executed on each individual detail row in the report.
Record-by-record logic requires a row-level formula rather than an aggregate summary formula.
2
Determine the appropriate Salesforce report feature.
A row-level formula in the report builder evaluates field logic row by row without adding custom fields to the underlying object schema.
This directly solves the business requirement while adhering to object customization constraints.

Key Concept

Distinction between row-level formulas and summary formulas in Salesforce reports
Question 1297Question →

Apex Global is setting up duplicate handling on the Account object. The operations team requires that when sales representatives manually create duplicate Account records, Salesforce should warn the user and log the entry in a duplicate record report without preventing creation. Conversely, when external system integrations insert Account records via the API under an Integration User profile, duplicate creation must be strictly prevented. Which TWO configurations within Salesforce Duplicate Management are required to fulfill these business requirements?

Select all that apply

Show answer & explanation

Answer: Configure a Duplicate Rule with the Action on Create set to Allow, selecting both the Alert and Report options.; Configure a separate Duplicate Rule with Rule Conditions filtering for the Integration User profile that sets the Action on Create to Block.

Answer

The administrator must configure a Duplicate Rule with Action on Create set to Allow (with Alert and Report enabled) for manual record creation, and configure a second Duplicate Rule using Rule Conditions for the Integration User profile with Action on Create set to Block.
In Salesforce Duplicate Management, Matching Rules define the criteria used to identify duplicate records (e.g., matching Account Name and Billing Address). Duplicate Rules determine the outcome when duplicates are detected. Setting Action on Create to Allow with Alert and Report allows users to proceed after seeing a prompt while logging the activity. Adding Rule Conditions to a Duplicate Rule allows administrators to enforce a strict Block action specifically for automated integration profiles.

Step-by-Step Solution

1
Distinguish between Matching Rule responsibilities and Duplicate Rule responsibilities.
Matching Rules establish the comparison criteria (e.g., exact or fuzzy matching on fields), whereas Duplicate Rules dictate what action is taken when duplicates are found.
Action enforcement options (Block vs. Allow/Alert/Report) exist solely within Duplicate Rules.
2
Configure duplicate handling for standard manual creation.
Set Action on Create to Allow and enable the Alert and Report checkboxes on the primary Account Duplicate Rule.
This alerts the user and logs duplicate entries in reporting data without halting record creation.
3
Configure conditional duplicate handling for integration users.
Create a targeted Duplicate Rule filtered by Profile equals Integration User using Rule Conditions, setting Action on Create to Block.
Rule Conditions allow administrators to vary action enforcement based on executing user attributes or record criteria.

Key Concept

Matching Rules define duplicate identification criteria, while Duplicate Rules enforce action responses (Allow, Block, Alert, Report) and execute conditional evaluation logic based on user criteria.
Question 1298Question →

An administrator at Northern Trail Outfitters is designing an automated solution on the custom object Equipment_Maintenance__c. Whenever an equipment maintenance record is created or updated to a status of 'Under Repair', three custom fields on that same triggering record must be calculated and populated before the record is saved to the database. The requirement explicitly specifies that no external calls, notifications, or modifications to related records should take place. Which flow type and trigger configuration should the administrator select to implement this automation with optimal performance?

Show answer & explanation

Answer: A Record-Triggered Flow configured for Fast Field Updates (Before-Save).

Answer

A Record-Triggered Flow configured for Fast Field Updates (Before-Save) is the correct choice.
Record-Triggered Flows configured for Fast Field Updates (Before-Save) execute before the record is saved to the database. They update values on the triggering record directly in memory without requiring an explicit Update Records DML element, making them significantly faster and optimized for same-record field updates.

Step-by-Step Solution

1
Analyze the automation requirements.
The automation requires field updates exclusively on the triggering record before it is committed to the database.
Identifying the target record (same triggering record vs. related records) determines the trigger timing.
2
Compare flow trigger options (Before-Save vs. After-Save).
Before-Save flows (Fast Field Updates) modify $Record values in memory 10 times faster than after-save updates.
Before-Save flows avoid extra DML database writes and prevent re-triggering the order of execution.
3
Select the optimal flow type and trigger configuration.
Choose Record-Triggered Flow with Fast Field Updates.
Fast Field Updates fulfill same-record modification requirements efficiently without extra overhead.

Key Concept

Selecting Fast Field Updates (Before-Save) vs. Actions and Related Records (After-Save) in Record-Triggered Flows
Estimated Time:1m 30s
Question 1299Question →

When a user submits a record for approval in Salesforce, which action is automatically executed by the system as part of the default initial submission behavior?

Show answer & explanation

Answer: The submitted record is locked to prevent edits during the approval process.

Answer

The submitted record is locked to prevent edits during the approval process.
When a record enters an approval process, Salesforce automatically locks the record by default during initial submission. This prevents standard users from making modifications to the record while it is undergoing review.

Step-by-Step Solution

1
Identify the standard system actions executed when a record enters an approval process.
Recognize that Salesforce automatically locks the record upon initial submission by default.
Record locking ensures that users cannot modify field values while the record is waiting for approval evaluation.

Key Concept

Approval Process Initial Submission Actions and Record Locking
Question 1300Question →

A Salesforce Administrator at an automotive dealership group is configuring a central sales and service performance dashboard in Lightning Experience. The dashboard incorporates components based on both Lead and Service Appointment custom reports. To allow regional managers to refine the dashboard metrics by geographic territory and timeframe, the administrator plans to add dynamic dashboard filters. Which two requirements and capabilities must the administrator consider when implementing these dashboard filters? (Select 2)

Select all that apply

Show answer & explanation

Answer: A maximum of 3 filters can be added to a single Lightning dashboard.; Fields used for filtering must be explicitly mapped for each source report if the equivalent fields differ across objects.

Answer

The correct requirements are that a maximum of 3 filters can be added to a single Lightning dashboard, and fields used for filtering must be explicitly mapped for each source report when the objects differ.
Salesforce enforces a standard limit of 3 dynamic filters per Lightning dashboard. Additionally, when dashboard components rely on source reports built from different objects, the administrator must map the filter to equivalent fields on each object so the filter applies correctly across all components.

Step-by-Step Solution

1
Identify system limits for Lightning dashboard filters
Confirm that Salesforce limits each dashboard to a maximum of 3 dashboard filters.
This is a hard platform governor limit for dashboard configuration.
2
Determine how dashboard filters operate across multi-object source reports
Recognize that field mapping is required when source reports draw from different objects (e.g., Leads vs. Service Appointments).
Each report component must know which specific field to filter on when a user selects a filter value.
3
Evaluate security and grouping constraints
Verify that dashboard filters respect existing security models and do not override source report grouping rules required for charts.
Filters only slice existing report data; they do not alter sharing rules or report structure prerequisites.

Key Concept

Lightning Dashboard Filters and Field Mapping
PreviousPage 65 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin