All practice questions

1784 questions

Question 1241Question

A Salesforce Administrator needs to create an Account report that categorizes Accounts into specific size brackets based on Annual Revenue without creating custom fields on the Account object. Additionally, the report must only display Accounts that have at least one associated closed won Opportunity. Which two report features should the administrator use to satisfy these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Add a Bucket Field on the Annual Revenue field to define custom categories.; Add a Cross Filter to filter Accounts WITH Opportunities and apply secondary subfilters for the Stage.

Answer

The administrator should use a Bucket Field on the Annual Revenue field to group accounts into size categories without custom fields, and a Cross Filter set to Accounts WITH Opportunities to filter based on related opportunity criteria.
Bucket fields provide inline grouping of ranges (like Annual Revenue tiers) without schema updates, and Cross Filters evaluate related child object criteria (like Accounts with specific Opportunities). Together, these features satisfy both requirements natively inside the report builder.

Step-by-Step Solution

1
Identify the requirement for grouping records without schema changes.
Recognize that Bucket Fields allow grouping numerical ranges or picklist values directly within report builder.
Creating custom fields in Object Manager is avoided when report bucketing meets the categorization need.
2
Identify the requirement for filtering parent records by child record criteria.
Determine that a Cross Filter configured as 'Accounts WITH Opportunities' with subfilters for closed won stage isolates the target parent records.
Standard report filters cannot evaluate child record relationships directly without Cross Filters.

Key Concept

Report Bucketing and Cross Filters
Question 1242Question

An organization relies on time-dependent workflow rules to manage record escalations. Place the following steps in the correct chronological order detailing how Salesforce evaluates a record update, processes immediate and time-based workflow actions, and handles pending queue entries upon subsequent record changes.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological sequence begins with the record edit satisfying criteria, followed by immediate action execution, placing the action in the Time-Based Workflow queue, a subsequent record edit negating criteria, and finally the automatic removal of the pending action from the queue.
The lifecycle of workflow rules requires that record changes first satisfy rule criteria, which triggers immediate actions before registering time-dependent actions in the Time-Based Workflow queue. If a record is subsequently edited before the scheduled trigger date such that it no longer meets the rule criteria, Salesforce automatically cancels and removes the pending action from the queue.

Step-by-Step Solution

1
Identify the initial record trigger event.
The user update causes record fields to meet the workflow rule criteria.
Workflow evaluation initiates when record changes align with defined rule criteria under the specified evaluation criteria setting.
2
Determine immediate action execution.
Immediate workflow actions run synchronously during the save process.
Immediate actions fire during the active save transaction as soon as criteria are evaluated as met.
3
Trace time-dependent action scheduling.
The time-dependent action is added to the Time-Based Workflow queue with its scheduled trigger date.
Time-dependent actions enter the queue once immediate actions finish processing.
4
Analyze subsequent record state changes.
A subsequent edit causes the record field values to fail the rule criteria prior to the trigger date.
Record modifications can occur at any point while an action remains pending in the queue.
5
Determine queue clearing behavior.
Salesforce removes the pending action from the Time-Based Workflow queue.
For rules set to evaluate when created or edited to subsequently meet criteria, failing the criteria on subsequent edit automatically removes unexecuted items from the queue.

Key Concept

Time-Based Workflow Queue Lifecycle and Dynamic Cancellation Behavior
Question 1243Question

Match each Salesforce business requirement to the corresponding Process Builder capability or limitation.

Click a left item, then click its matching right item

Items

Automatically notify a Chatter group when a High-Value Opportunity is closed.
Automatically submit a Discount Request record for approval when the discount exceeds 20%.
Update the phone number on all child Contact records when the parent Account phone changes.
Delete an obsolete record automatically when a custom status field is updated to Expired.

Matches

Show answer & explanation

Answer

Posting Chatter updates matches 'Supported via the Post to Chatter action'; Approval requests match 'Supported via the Submit for Approval action'; Updating child records matches 'Supported via the Update Records action for related child records'; Deleting records matches 'Not supported in Process Builder (requires Flow Builder or Apex)'.
Process Builder provides native capabilities for creating/updating records (including related child records), submitting records for approval, and posting to Chatter feeds. However, deleting records is outside its functional capabilities and requires Flow Builder or Apex code.

Step-by-Step Solution

1
Evaluate standard action capabilities supported natively in Process Builder.
Posting to Chatter, submitting records for approval, and updating related child records are standard native actions in Process Builder.
Process Builder allows admins to configure cross-object record updates, Chatter notifications, and approval submissions declaratively.
2
Identify execution limitations of Process Builder.
Record deletion is not available as a standard action in Process Builder.
Deleting records requires tools with expanded data manipulation capabilities, such as Flow Builder or Apex triggers.

Key Concept

Process Builder Supported Actions and Platform Limitations
Question 1244Question

A Salesforce administrator at a global retail company needs to execute two distinct data management operations:

1. Update or insert 80,000 Contact records based on a unique External ID field.
2. Permanently remove (hard delete) 15,000 inactive custom object records named Archive_Log__c from the organization.

Which two statements specify the correct tool and operation required to satisfy these requirements? (Choose 2 options)

Select all that apply

Show answer & explanation

Answer: Data Loader must be used to perform an upsert operation for the 80,000 Contact records using the External ID.; Data Loader must be used to perform a hard delete operation for the 15,000 Archive_Log__c records.

Answer

Data Loader must be used for both operations: upserting the 80,000 Contact records using the External ID and performing a hard delete on the 15,000 Archive_Log__c records.
Data Loader is the appropriate tool for both tasks because Data Import Wizard is limited to 50,000 records per job and does not support record deletion or hard deletion. Data Loader easily handles up to 5,000,000 records and includes native support for upserting via External ID as well as hard deleting records.

Step-by-Step Solution

1
Evaluate record volume for the Contact import operation.
The operation involves 80,000 records, which exceeds the Data Import Wizard limit of 50,000 records.
Data Loader must be chosen for any import or upsert batch exceeding 50,000 records.
2
Evaluate operation capabilities for hard deleting records.
Hard deletion permanently removes records without sending them to the Recycle Bin.
Data Import Wizard does not support delete or hard delete operations; Data Loader is required for hard deletes.

Key Concept

Tool selection criteria between Data Import Wizard and Data Loader based on record volume limits and supported operation types (e.g., hard delete).
Question 1245Question

A Salesforce Administrator is designing a record-triggered flow to automate Case assignment. The flow must evaluate the Case Priority field and route high-priority cases down one execution path and normal-priority cases down a different path. Which Flow Builder element should the administrator add to branch the flow logic based on these field conditions?

Show answer & explanation

Answer: Decision element

Answer

The Decision element is used in Flow Builder to evaluate field conditions and branch the flow into multiple outcome paths.
The Decision element in Flow Builder evaluates logical expressions and routes the flow down different outcome paths based on whether criteria (such as Case Priority equal to 'High') are met.

Step-by-Step Solution

1
Identify the requirement to evaluate field values and create separate path execution logic.
Recognize that branching requires a logical evaluation element in Flow Builder.
Flow Builder uses specific logical control elements to direct execution flow based on criteria.
2
Compare Flow Builder logical and data elements.
Determine that the Decision element handles conditional branching by defining outcomes based on record field values.
Decision elements evaluate defined criteria (like Case Priority = 'High') to determine which path the flow should follow.

Key Concept

Flow Builder Decision Element and Logic Branching
Question 1246Question

Match each Salesforce email integration requirement to the corresponding administrative configuration action required to fulfill it.

Click a left item, then click its matching right item

Items

Allow sales representatives to view and insert public Lightning Email Templates directly from the Outlook Integration panel.
Automatically capture and log emails sent from Gmail to associated Salesforce Contacts and Opportunities without manual user intervention.
Enable a select group of sales managers to create and edit shared Lightning Email Templates in public folders, while standard reps can only use them.
Display custom Salesforce fields and specific related lists inside the side pane of the Gmail Integration interface.

Matches

Show answer & explanation

Answer

Viewing and inserting public Lightning templates matches assigning the 'Use Lightning Email Templates' permission and folder access; automated email background logging matches enabling Einstein Activity Capture; creating public templates matches granting the 'Manage Public Lightning Email Templates' permission; and customizing side panel components matches building custom Email Application Pane layouts.
Each requirement directly aligns with its corresponding administrative action: consuming public Lightning templates requires 'Use Lightning Email Templates' permission and folder access; automated email capture requires Einstein Activity Capture; creating shared templates requires 'Manage Public Lightning Email Templates' permission; and customizing the integration side panel layout requires configuring custom Email Application Pane layouts.

Step-by-Step Solution

1
Identify the template consumption permission requirement for the integration pane.
Determined that using Lightning templates in Outlook/Gmail requires the 'Use Lightning Email Templates' system permission alongside public folder access.
Without this permission and folder sharing access, users cannot access shared Lightning templates in the integration side panel.
2
Determine the tool for automated zero-touch email logging from Gmail.
Selected Einstein Activity Capture configuration.
Standard Gmail Integration requires manual logging per email, whereas Einstein Activity Capture syncs emails automatically.
3
Identify the administrative permission required for template management.
Selected the 'Manage Public Lightning Email Templates' permission set assignment for designated managers.
Restricting public folder creation to managers while allowing reps to consume templates requires separating management permissions from basic template usage permissions.
4
Determine how to customize the integration panel layout.
Selected Email Application Pane layout configuration in Setup.
Email Application Pane layouts determine which fields and Lightning components appear in the Gmail/Outlook side panel interface.

Key Concept

Salesforce Outlook and Gmail Integration Capabilities and Lightning Email Template Folder Permissions
Question 1247Question

An administrator creates and activates a custom Matching Rule on the Account object to identify duplicates based on Account Name and Tax Identification Number. However, when users save new Account records with matching values, Salesforce creates the records without displaying a warning or blocking the entry. What configuration step is missing?

Show answer & explanation

Answer: Creating and activating a Duplicate Rule that references the Matching Rule to enforce an Alert or Block action

Answer

Creating and activating a Duplicate Rule that references the Matching Rule is necessary to trigger duplicate alerts or blocks.
Matching Rules only specify how fields are evaluated to identify duplicates. To enforce duplicate prevention or warn users upon record creation, an administrator must configure and activate a Duplicate Rule that references the Matching Rule and specifies the desired action, such as Alert or Block.

Step-by-Step Solution

1
Understand the role of a Matching Rule.
Matching Rules define the exact field matching logic used to identify candidate duplicate records.
A Matching Rule alone does not perform any user-facing action during record creation or edit.
2
Understand the role of a Duplicate Rule.
Duplicate Rules determine what happens when duplicate records are identified, such as alerting the user or blocking the save operation.
An active Duplicate Rule linked to the Matching Rule is required for duplicate enforcement.

Key Concept

Matching Rules define HOW records are compared to find duplicates, while Duplicate Rules determine WHAT ACTION is executed when duplicates are detected.
Question 1248Question

An administrator at Universal Containers configures an approval process for high-value Opportunity records. However, sales managers report that sales representatives can still edit Opportunity field values while an approval request is pending. Which configuration step should the administrator check to prevent edits immediately when a record enters the approval process?

Show answer & explanation

Answer: Ensure that the Initial Submission Actions specify that the record is automatically locked upon submission.

Answer

The administrator must verify that the record is set to lock automatically within the Initial Submission Actions of the approval process.
When a record is submitted for approval in Salesforce, the default behavior specified in the Initial Submission Actions is to lock the record. This prevents non-administrator users from modifying field values while the approval is pending.

Step-by-Step Solution

1
Analyze the requirement for record locking during approval
Identify that pending approval records must be read-only for submitters
Prevent users from altering record details while manager approval is pending
2
Examine approval process configuration options
Determine that Initial Submission Actions control the record status upon submission
Initial Submission Actions take effect as soon as a user submits the record for approval
3
Verify standard Salesforce approval process behavior
Confirm record locking is configured under Initial Submission Actions
Locking the record ensures only system administrators (and designated approvers if configured) can edit the record while in approval

Key Concept

Approval Process Initial Submission Actions and Record Locking
Estimated Time:1m 30s
Question 1249Question

A System Administrator is configuring a Custom Report Type to support cross-departmental reporting between Accounts, Opportunities, and custom Delivery Schedules. Which TWO configurations or behaviors accurately describe Salesforce Custom Report Types?

Select all that apply

Show answer & explanation

Answer: Selecting 'Each record may or may not have related records' (with or without relationship) ensures parent records display in reports even if they have no related child records.; Administrators can add fields from objects related via lookup (up to four levels reference chain) to the Custom Report Type layout so users can include them in reports.

Answer

The correct configurations are: choosing 'Each record may or may not have related records' ensures parent records appear without child records, and administrators can add fields from related objects via lookup up to four levels deep into the Custom Report Type layout.
Selecting the 'with or without' option configures an outer join so that parent records display regardless of child record presence. Additionally, administrators can use the 'Add fields related via lookup' feature within the Custom Report Type layout editor to reference fields up to four lookup levels away.

Step-by-Step Solution

1
Analyze object relationship join options in Custom Report Types
Using the 'with or without' relationship acts as an outer join, allowing parent records to be displayed in reports even when related child records are missing.
Business reporting often requires identifying parent records (e.g., Accounts) that lack activity or child records (e.g., Opportunities).
2
Evaluate layout customization capability for referencing lookup objects
Administrators can click 'Add fields related via lookup' in the report layout editor to traverse up to 4 levels of lookup relationships.
This avoids creating redundant custom formula fields solely for reporting purposes.
3
Verify security enforcement and distractor statements
Salesforce security (OWD, sharing rules, profiles) is always strictly enforced in reports, and Custom Report Types support lookup relationships.
Report visibility never overrides underlying record-level security.

Key Concept

Custom Report Type Object Relationships and Layout Customization
Question 1250Question

A Salesforce Administrator is constructing an autolaunched flow to update a custom status field across a collection of inactive Partner Account records while strictly adhering to Salesforce governor limit best practices. Place the following flow execution steps in the correct order from first step to final step.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct execution order begins with executing a Get Records element to query the inactive Partner Account records into a collection variable, followed by iterating over the collection with a Loop element. Inside the loop, the first Assignment element modifies field values on the current loop item variable, and the second Assignment element adds that modified variable to a new output record collection variable. Finally, after the loop finishes, a single Update Records element executes on the output collection variable.
Salesforce design best practices require bulkifying flows by isolating database transactions (Get Records, Update Records) outside of loops. The process begins by retrieving records into a collection (Get Records), passing that collection into a Loop element, using an Assignment element to update the current record variable's fields, using another Assignment element to append the record variable to an output collection, and finally committing the output collection to the database using an Update Records element after the loop completes.

Step-by-Step Solution

1
Identify the data retrieval step.
Place the Get Records element first, outside of any loop structure.
SOQL queries must occur before looping to prevent executing data retrieval inside a loop, avoiding governor limits.
2
Initiate collection processing.
Place the Loop element second, receiving the record collection from the Get Records element.
Looping allows row-by-row processing of record items stored within the collection.
3
Modify the current record's field values.
Place the field value Assignment element as the first action inside the loop.
The temporary current item variable in the loop must have its field values set before it can be stored in the updated collection.
4
Stage the updated record into an output collection.
Place the collection Assignment element as the second action inside the loop.
Adding the modified item variable to a target output collection aggregates all updated records into a single collection variable.
5
Perform database commit.
Place the Update Records element last, connected to the 'After Last Item' path of the Loop element.
Executing DML once outside the loop commits all changes in bulk and consumes only one DML statement limit.

Key Concept

Bulkification and Flow Element Sequence
Question 1251Question

Zenith Wealth Management enforces a Private Organization-Wide Default (OWD) sharing model for Opportunities. A Salesforce administrator configures an executive performance dashboard stored in a shared folder accessible by all Sales Managers. The dashboard's running user is statically set to the Chief Commercial Officer (CCO). When a Sales Manager views the dashboard component, it displays 25,000,000intotalpipelinevalue.However,whentheSalesManagerclicksthecomponenttoopentheunderlyingsourcereport,thereportdisplaysonly25,000,000 in total pipeline value. However, when the Sales Manager clicks the component to open the underlying source report, the report displays only 4,500,000 in pipeline value. Which statement explains the primary cause of this discrepancy?

Show answer & explanation

Answer: The dashboard component calculates results using the record-level security of the static running user, while the source report executes using the security context of the logged-in user.

Answer

The dashboard component calculates results using the record-level security of the static running user, while the source report executes using the security context of the logged-in user.
When a dashboard is configured with a static running user, component metrics are calculated using that specified user's security access level (the CCO), allowing viewers to see summarized metrics they might not individually own. However, when a user clicks the component to open the source report, Salesforce runs the report using the logged-in user's security context, restricting record display to only what the user can access under OWD and sharing rules.

Step-by-Step Solution

1
Analyze how static dashboard running user settings affect component data visibility.
When a dashboard is configured with a static running user (such as the CCO), all users with folder view access see summary data aggregated according to the CCO's record access permissions ($25,000,000).
Static running users determine the security context used to calculate component metrics.
2
Analyze how source report execution handles user record permissions upon drill-down.
When clicking a dashboard component to view the source report, Salesforce runs the report under the logged-in user's own security context (Sales Manager).
Source reports always enforce individual record-level access based on OWD, sharing rules, and role hierarchy for the logged-in user ($4,500,000).
3
Identify the cause of the data discrepancy between the dashboard component and the source report.
The discrepancy occurs because the dashboard displays data using the CCO's access while the source report displays data using the logged-in Sales Manager's access.
This is standard platform behavior when using static running users on objects with restricted sharing.

Key Concept

Static dashboard components render data according to the designated running user's security context, whereas underlying source reports always execute based on the logged-in user's security access.
Question 1252Question

An administrator needs to build an autolaunched flow that processes nightly updates for a custom object named Service Contract. For each active Service Contract record, the flow must iterate over all related Line Item records (linked via a lookup relationship), calculate the total contracted value using an Assignment element, and set a custom Status field on each Line Item to 'Archived'. The solution must process thousands of records efficiently without hitting SOQL or DML governor limits. Which design pattern correctly utilizes Flow Builder elements and logic to meet these requirements?

Show answer & explanation

Answer: Execute a Get Records element before the loop to retrieve all related Line Items into a record collection, use an Assignment element inside the loop to accumulate line values and add updated Line Item records to a secondary collection variable, and execute a single Update Records element on the secondary collection outside the loop.

Answer

The correct design executes a Get Records element before entering the loop to fetch child Line Items into a collection, uses Assignment elements within the loop to update record variables and build a secondary update collection, and then performs a single Update Records operation on the collection after exiting the loop.
Bulkification is mandatory when designing flows in Salesforce. Performing data operations (Get Records, Create Records, Update Records, Delete Records) outside of loops ensures that all queries and database commits are executed in single batch calls rather than repeated per item, adhering strictly to transaction governor limits.

Step-by-Step Solution

1
Query records efficiently
All child Line Item records are retrieved in a single SOQL query before any iteration occurs.
Executing data queries outside loops prevents reaching the limit of 100 SOQL queries per transaction.
2
Iterate and modify in-memory variables
The flow loops through the collection, uses an Assignment element to sum values, updates field values in memory, and adds the modified record variable to a new Record Collection variable.
In-memory variable manipulation does not consume database governor limits.
3
Commit changes in a bulkified operation
A single Update Records element processes the entire modified Record Collection variable after the loop finishes.
Executing a single DML operation outside the loop ensures the flow stays well within the 150 DML statements governor limit.

Key Concept

Bulkification in Flow Builder (Data operations outside loops)
Estimated Time:2m 0s
Question 1253Question

An administrator at Aether Logistics needs to configure a specialized sales workflow with tailored opportunity stages for a newly formed Government Contracts division. Place the administrative configuration steps in the correct chronological order to make these custom stages accessible to the sales team.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of administrative steps is: First, add the required stage values to the Opportunity Stage picklist field; second, create a Sales Process and select the active stages for the process; third, create an Opportunity Record Type associated with the Sales Process; fourth, assign the new Record Type and page layout to the appropriate user profile.
The correct implementation sequence follows Salesforce dependency rules. Stage picklist values must first be created on the Opportunity object. Next, a Sales Process must be defined to select which of those stages belong to the business process. Third, an Opportunity Record Type is created and assigned to the Sales Process (as Opportunity record types derive stage values strictly from a Sales Process). Finally, the Record Type and layout are assigned to the relevant user profiles to grant access.

Step-by-Step Solution

1
Add stage picklist values on the Opportunity object
The new stage names, probabilities, and type designations exist in the master Stage picklist.
Sales Processes cannot include stages that do not yet exist in the master Opportunity picklist.
2
Create the Sales Process
A defined Sales Process containing only the subset of stages needed for Government Contracts is established.
Opportunity Record Types rely on a Sales Process to control available stage picklist values.
3
Create the Opportunity Record Type
The Record Type is linked directly to the newly created Sales Process.
An Opportunity Record Type cannot be saved without associating it with an existing Sales Process.
4
Grant access via Profile assignments
Users assigned to the Government Contracts profile can create and edit records using the new process.
Record Types and page layouts must be mapped to profiles to grant visibility and interface access.

Key Concept

Sales Process and Opportunity Record Type Setup Sequence
Estimated Time:1m 30s
Question 1254Question

A Service Cloud administrator at a SaaS company is implementing case automation to streamline customer support. The requirements specify that newly created cases must be assigned to designated regional queues based on customer location, an automated confirmation email using custom templates must be sent immediately to the submitting contact, and cases with a Priority of 'High' that remain unassigned or open after 4 hours must trigger a manager alert and transfer ownership to Tier 2 Support.

Which two statements accurately describe how Salesforce case automation rules should be configured to satisfy these requirements? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Case Assignment Rules determine initial ownership based on case attributes, whereas Case Escalation Rules use time-based criteria to reassign unresolved cases and notify stakeholders.; Only one Case Assignment Rule and one Case Escalation Rule can be active at a time, but each rule can contain multiple prioritized rule entries.

Answer

The correct statements are that Case Assignment Rules handle initial ownership based on attributes while Escalation Rules evaluate time-based criteria for reassignment, and that only one Case Assignment Rule and one Case Escalation Rule can be active simultaneously (each containing multiple ordered rule entries).
Case Assignment Rules establish initial case ownership based on record criteria when cases are created, while Case Escalation Rules execute time-based actions such as reassigning unresolved cases to queues or notifying managers after a specified duration. Additionally, Salesforce restricts configuration to a single active Assignment Rule and a single active Escalation Rule at any point in time, requiring administrators to build multiple rule entries within those active rules.

Step-by-Step Solution

1
Analyze the automation requirements for initial routing versus SLA tracking
Initial queue routing requires Case Assignment Rules, while time-elapsed reassignment (4 hours) requires Case Escalation Rules.
Assignment rules run upon case creation to set ownership, whereas escalation rules track open cases against time thresholds.
2
Evaluate Salesforce administrative limits regarding active rule structures
Salesforce allows only one active Assignment Rule and one active Escalation Rule per object, though each active rule container holds multiple prioritized rule entries.
Multiple active rules of the same type cannot coexist; administrators organize complex logic by sequencing rule entries within the single active rule.
3
Identify misconceptions regarding Escalation and Auto-Response capabilities
Escalation rules do not perform initial assignment on creation, and Auto-Response rules only send email templates without altering ownership.
Confusing functional capabilities between assignment, escalation, and auto-response rules leads to improper automation design.

Key Concept

Distinct roles and active limitations of Case Assignment, Auto-Response, and Escalation Rules
Question 1255Question

CloudScale Software operates two distinct business divisions: Software Subscriptions and Professional Services. The Professional Services sales team requires a customized sales pipeline with specific Opportunity stage picklist values and win probabilities that differ from the standard sales pipeline. The administrator has already created the new stage picklist values on the Opportunity object.

Which sequence of administrative steps must the administrator perform to make the customized sales pipeline available to the Professional Services sales team?

Show answer & explanation

Answer: Create a new Sales Process for Professional Services, select the desired stage values, create an Opportunity Record Type linked to the Sales Process, and assign the Record Type to the appropriate profiles.

Answer

Create a new Sales Process for Professional Services, select the desired stage values, create an Opportunity Record Type linked to the Sales Process, and assign the Record Type to the appropriate profiles.
To implement customized Opportunity stages for a distinct sales team, an administrator must first create a Sales Process to select the specific stages and probabilities needed. Next, an Opportunity Record Type must be created and linked to that Sales Process. Finally, the Record Type is assigned to the appropriate user profiles.

Step-by-Step Solution

1
Create a custom Sales Process
Defines the subset of Opportunity stage picklist values specific to the Professional Services sales cycle.
Salesforce requires a Sales Process to govern which Opportunity stages are visible and active for a particular business pipeline.
2
Create an Opportunity Record Type linked to the Sales Process
Associates the newly created Sales Process with a distinct Opportunity record type.
Record types allow different page layouts and picklist values to be displayed to users, and for Opportunities, the record type must be tied to a specific Sales Process.
3
Assign the Opportunity Record Type to User Profiles
Grants users with the Professional Services profile access to create and manage opportunities using the new sales process.
Profile assignment determines which record types are available to users when creating new records.

Key Concept

Opportunity Sales Processes and Record Type Linkage
Question 1256Question

A System Administrator is configuring a Record-Triggered Flow on the Case object that executes when a Case status is updated to 'Escalated'. The requirement states that for every escalated case, all associated open Work Order records must have their Priority set to 'Urgent' and an escalation timestamp recorded. To ensure the flow operates efficiently without exceeding governor limits during bulk updates, which TWO flow design elements and logic patterns must the administrator use? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Use an Assignment element inside the loop to append each modified Work Order record to a Record Collection Variable, followed by a single Update Records element placed after the loop path.; Utilize a single Get Records element prior to the loop element to retrieve the collection of related Work Order records matching the criteria.

Answer

The administrator must use an Assignment element inside the loop to accumulate modified records into a collection variable and perform a single Update Records element after the loop, as well as execute a single Get Records element prior to entering the loop.
To adhere to Salesforce governor limits and best practices for flow bulkification, data retrieval (Get Records) must occur before entering a loop, and data modification (Update Records) must occur once after the loop completes using a collection variable. Accumulating record updates into a record collection using an Assignment element inside the loop allows a single DML operation to update all child records simultaneously.

Step-by-Step Solution

1
Identify query bulkification requirements prior to iteration.
Place a single Get Records element before the loop to retrieve all open Work Order records into a collection.
Prevents executing SOQL queries inside the loop, avoiding SOQL query governor limits.
2
Modify records in memory within the loop.
Use an Assignment element inside the loop to set field values and add the updated record to a target Record Collection Variable.
Prepares updated values in heap memory without triggering individual database DML calls.
3
Commit changes in a bulkified operation after loop exit.
Place a single Update Records element after the loop path finishes, passing the Record Collection Variable.
Executes one DML update statement for the entire set of records, respecting DML governor limits.

Key Concept

Flow Bulkification and Governor Limits in Flow Builder
Question 1257Question

An administrator is reviewing the execution lifecycle of a record submitted to a standard Salesforce approval process. Place the following stages of the approval process in the correct order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order from first to last is: Initial Submission Actions execute and the record is locked → Step Entry Criteria are evaluated to determine routing for the approval step → The assigned approver reviews and approves the request → Final Approval Actions execute and the record is unlocked.
When a record enters an approval process, Salesforce first executes Initial Submission Actions (such as locking the record). Next, it evaluates the Step Entry Criteria to route the record to the correct approver. The approver then acts on the request, and upon approval, Salesforce executes Final Approval Actions (such as field updates and record unlocking).

Step-by-Step Solution

1
Identify the initial submission stage.
Initial Submission Actions run automatically when submission occurs, locking the record against unauthorized edits.
Securing the record is the first operational step of any approval process upon entry.
2
Evaluate approval step entry criteria.
Salesforce checks if the record meets the specific requirements defined for Step 1.
Entry criteria evaluation determines if the record enters the step or bypasses it.
3
Process human or automated approval decisions.
The designated approver responds by approving the record.
User approval progresses the process toward final resolution.
4
Execute post-approval completion actions.
Final Approval Actions execute, updating status fields and unlocking the record.
Final actions wrap up the workflow upon complete approval of all required steps.

Key Concept

Salesforce Approval Process Execution Lifecycle
Question 1258Question

A Salesforce Administrator at an agricultural machinery distributor is building a central performance dashboard in Lightning Experience to monitor opportunity sales pipelines and customer support cases across different territories. The administrator plans to add dashboard filters so regional managers can filter components by Region and Industry.

Which two considerations must the administrator keep in mind when configuring these dashboard components and dynamic filters? (Select 2)

Select all that apply

Show answer & explanation

Answer: A maximum of 3 dashboard filters can be added to a single Lightning dashboard.; Source reports must contain at least one grouping to be used as data sources for chart components.

Answer

The correct statements are that a maximum of 3 dashboard filters can be added to a single Lightning dashboard, and that source reports must contain at least one grouping to be used as data sources for chart components.
The options specifying that a single Lightning dashboard supports a maximum of 3 filters and that source reports require at least one grouping for chart components are correct. Salesforce limits each dashboard to 3 dynamic filters. Furthermore, dashboard charts require grouped report data (Summary, Matrix, or Joined reports) to render categories and metrics.

Step-by-Step Solution

1
Evaluate the platform limits for Lightning dashboard filters.
Salesforce allows a maximum of 3 dashboard filters per dashboard.
This is a fixed platform constraint for Lightning Experience dashboards.
2
Analyze source report requirements for dashboard chart components.
Reports must be formatted with at least one grouping (Summary, Matrix, or Joined report) to serve as source data for charts.
Charts rely on grouped data to plot axes, categories, and summary values.
3
Review security and filter mapping options.
Filters map to report fields (not restricted to summary formulas) and do not grant record-level access beyond user permissions.
User record access is controlled by OWD, sharing rules, and object permissions.

Key Concept

Dashboard design component requirements and dynamic filter limits
Question 1259Question

A Salesforce administrator at a global logistics firm is configuring data quality controls on the custom object Shipment_Manifest__c. Match each business requirement with the formula pattern that correctly implements the logic while adhering to Salesforce formula evaluation best practices.

Click a left item, then click its matching right item

Items

Prevent edits to Delivery_Notes__c unless Status__c is currently set to 'In Transit'.
Require Driver_License_Number__c to be populated whenever Carrier_Type__c is set to 'Internal'.
Prevent users from decreasing the Declared_Value__c on existing records, while allowing any initial value upon record creation.
Enforce a 5-digit numeric format on Postal_Code__c whenever it is created or updated, ensuring blank values do not trigger false positives if optional.

Matches

Show answer & explanation

Answer

Each business requirement is matched with its corresponding formula pattern based on standard Salesforce formula function mechanics: restricting Delivery_Notes__c edits matches the pattern using ISCHANGED and ISPICKVAL status verification; mandatory Driver_License_Number__c matches the ISPICKVAL and ISBLANK pattern; restricting Declared_Value__c decreases matches the NOT(ISNEW()) and PRIORVALUE comparison pattern; and Postal_Code__c formatting matches the REGEX pattern combined with ISBLANK and context checks.
Matching each business requirement requires selecting functions aligned with field data types and transaction contexts. ISCHANGED and PRIORVALUE apply to modified existing values, ISNEW isolates record creation context, ISPICKVAL handles picklist evaluation, and combining ISBLANK with REGEX prevents null-handling errors during pattern enforcement.

Step-by-Step Solution

1
Analyze status-restricted field modification requirements.
Edits to Delivery_Notes__c must trigger a validation error if Status__c is not 'In Transit'.
ISCHANGED(Delivery_Notes__c) paired with NOT(ISPICKVAL(Status__c, 'In Transit')) captures modifications attempted outside the permitted picklist status.
2
Analyze conditional field population rules.
Driver_License_Number__c must evaluate true (error state) when blank if Carrier_Type__c equals 'Internal'.
ISPICKVAL assesses picklist values safely without text cast issues, and ISBLANK accurately detects empty text inputs.
3
Analyze field value reduction restrictions on existing records.
The rule must trigger only on existing record updates where the newly submitted value is less than the prior saved value.
NOT(ISNEW()) prevents execution during record creation, while PRIORVALUE(Declared_Value__c) provides the historical comparison baseline.
4
Analyze pattern format validation with null handling.
Regex format matching should execute on creation or edit, but skip evaluation when optional fields are left blank.
NOT(ISBLANK(Postal_Code__c)) guards against false positive validation errors on empty optional inputs while REGEX enforces exact 5-digit formatting.

Key Concept

Validation Rule Function Mechanics and Data Quality Guardrails
Question 1260Question

A Salesforce administrator at a healthcare organization needs to import 45,000 Contact records into Salesforce. The import process must trigger active workflow rules and automatically prevent duplicate record creation based on matching email addresses. Which tool should the administrator use to fulfill these requirements?

Show answer & explanation

Answer: Data Import Wizard, because it supports up to 50,000 records for standard objects like Contacts and includes built-in duplicate matching features.

Answer

Data Import Wizard should be used because it handles up to 50,000 records for supported standard objects like Contacts and includes native duplicate prevention.
The choice stating that Data Import Wizard should be used is correct because the import volume (45,000 records) is within its 50,000 limit, Contacts are a supported standard object, and Data Import Wizard provides native duplicate prevention options using field matching.

Step-by-Step Solution

1
Evaluate record volume limits
The batch of 45,000 records is within the 50,000 record capacity limit of the Data Import Wizard.
Data Import Wizard is capped at 50,000 records, while Data Loader handles up to 5,000,000 records.
2
Verify object support
Contacts are a standard object supported by the Data Import Wizard.
Data Import Wizard supports Accounts, Contacts, Leads, Solutions, Campaign Members, and all custom objects.
3
Assess duplicate prevention requirements
Data Import Wizard provides built-in duplicate matching on fields like Email.
Data Loader does not perform automatic duplicate checking during record insertion.

Key Concept

Selecting between Data Import Wizard and Data Loader based on record volume limits (50,000 vs 5,000,000), standard object support, and built-in duplicate prevention capabilities.
PreviousPage 63 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin