All practice questions

1784 questions

Question 201Question

Apex Health Consulting requires field consultants to record client alignment sessions in Salesforce. Each session involves up to 35 client contacts, a single parent Opportunity, and multiple internal consultants who attend the meeting. Additionally, after meetings, team leaders create action items assigned to several team members at once. The administrator has enabled Shared Activities ('Allow Users to Relate Multiple Contacts to Tasks and Events'). Which two system behaviors should the administrator highlight when training the field consulting team on how Salesforce processes these activities?

Select all that apply

Show answer & explanation

Answer: A single Event can be linked to up to 50 Contacts while remaining related to only one Account or Opportunity record.; Assigning a single Task to a group or multiple individual users automatically creates an independent copy of the Task for each assigned user.

Answer

With Shared Activities enabled, a single Event can be linked to up to 50 Contacts while staying related to one primary record (such as an Opportunity), and assigning a Task to multiple users creates an independent copy of that Task for each user.
Enabling Shared Activities allows relating up to 50 Contacts to a single Task or Event, but the activity can still only link to one Account or Opportunity (WhatId). Furthermore, assigning a Task to multiple users creates individual task copies for each user, ensuring each assignee has their own actionable task item.

Step-by-Step Solution

1
Analyze Shared Activities limits for Contacts and related records.
Confirm that Shared Activities allows up to 50 Contacts per event or task, but limits the 'Related To' (WhatId) field to a single record like an Account or Opportunity.
Salesforce data architecture enforces a 1-to-many relationship for WhoId (Contacts) under Shared Activities, but retains a single WhatId link.
2
Analyze multi-user assignment behavior for Tasks versus Events.
Recognize that multi-user Task assignment creates distinct copies per user, whereas multi-user Event scheduling retains a single Event record with multiple attendees.
Tasks represent individual work items to be completed independently, while Events represent shared calendar items with an organizer and invitees.

Key Concept

Shared Activities capability limits and multi-user assignment behavior for Tasks vs Events
Question 202Question

A Salesforce administrator is asked to create a report that organizes open opportunities into groups based on their Stage and displays subtotal amounts for each stage group. Which report format should the administrator select to meet this requirement?

Show answer & explanation

Answer: Summary

Answer

Summary report format
Summary format allows records to be grouped by row values (such as Opportunity Stage) and provides automated subtotals for numeric fields across each group.

Step-by-Step Solution

1
Identify the grouping requirement
The requirement specifies grouping opportunity records by a single dimension (Stage) with subtotals.
Choosing the correct report format depends on how records need to be grouped and summarized.
2
Evaluate standard Salesforce report formats
Tabular provides no groupings; Matrix groups by rows and columns; Joined combines multiple report blocks; Summary groups by rows.
Summary format is the simplest standard format that supports single-level row grouping and field subtotals.

Key Concept

Selecting appropriate report formats based on grouping and summary requirements.
Question 203Question

A company recently restructured its business development team. A sales operations manager asks the administrator to reassign 350 open Lead records from a departing team member to a newly hired representative. Additionally, all open activities attached to these Leads must automatically shift to the new representative, while leaving closed activities untouched. Which feature or tool should the administrator utilize to accomplish this task efficiently without needing to prepare or update external CSV files?

Show answer & explanation

Answer: The native Mass Transfer Records wizard in Setup

Answer

The native Mass Transfer Records wizard in Setup is the correct solution because it enables administrators to mass reassign ownership of Leads directly in the user interface, with built-in criteria to automatically transfer open activities without requiring CSV file manipulation.
The Mass Transfer Records wizard in Setup is specifically built for reassigning ownership of standard objects (such as Leads, Accounts, and Contacts) in bulk directly through the UI. It includes native options to transfer open activities attached to those records without modifying CSV data.

Step-by-Step Solution

1
Identify the record count and requirements
350 Lead records need ownership transfer along with associated open activities, requiring no external file management.
Evaluating whether native setup tools can accomplish the task faster than API bulk tools.
2
Evaluate native Salesforce mass maintenance tools
The Mass Transfer Records tool supports standard objects like Leads, Accounts, and Opportunities, and provides checkboxes to transfer open activities.
Mass Transfer Records operates entirely within Setup without requiring CSV exports or external ID mapping.
3
Select the optimal tool
Mass Transfer Records in Setup is chosen as the most efficient solution.
It fulfills all functional criteria in a single step.

Key Concept

Mass Transfer Records Tool Capabilities
Question 204Question

An organization relies on the Salesforce Integration with Outlook and utilizes Lightning Email Templates for client communications. The sales manager requests that a specific senior sales representative be granted the ability to create, edit, and delete shared Lightning Email Templates in public folders. Standard sales representatives should continue to only view and use these shared templates without modification rights. What is the recommended administrative configuration to achieve this access requirement?

Show answer & explanation

Answer: Create a permission set with the 'Manage Public Lightning Email Templates' system permission enabled and assign it to the senior sales representative.

Answer

Create a permission set with the 'Manage Public Lightning Email Templates' system permission enabled and assign it to the senior sales representative.
The correct solution uses a dedicated Permission Set containing the 'Manage Public Lightning Email Templates' permission. This adheres to Salesforce security best practices by extending administrative template management capabilities strictly to the specified senior representative without changing profile permissions for standard sales representatives.

Step-by-Step Solution

1
Analyze access scope requirement
Identified that only one designated user needs elevated creation and editing privileges for public Lightning email templates, while other users on the same profile require read-only template access.
Applying functional access to selective users requires additive permissions rather than broad profile modifications.
2
Evaluate administrative mechanism for additive permissions
Determined that a Permission Set containing 'Manage Public Lightning Email Templates' is the correct Salesforce mechanism.
Permission Sets allow administrators to grant granular system capabilities to specific users without affecting the base Profile assigned to the broader team.
3
Verify integration compatibility
Confirmed that once the permission set is assigned, the user can manage public Lightning templates which seamlessly surface in the Salesforce Integration with Outlook interface.
Outlook Integration respects underlying Salesforce object permissions and user system rights.

Key Concept

Selective privilege elevation for Lightning Email Template management using Permission Sets.
Question 205Question

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 206Question

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 207Question

An administrator is setting up data quality controls for Lead records using validation rules. Which two statements correctly describe how validation rules function and affect data quality? (Select two)

Select all that apply

Show answer & explanation

Answer: Validation rules fire before a record is saved and display an error message if the formula criteria evaluate to true.; Validation rules can utilize functions like ISBLANK to detect whether required fields contain values.

Answer

Validation rules fire before a record is saved to block invalid data when the formula evaluates to true, and they can use functions like ISBLANK to ensure required fields contain values.
Validation rules execute prior to record save operations and stop saving if the formula condition evaluates to true. Administrators standardly use functions like ISBLANK within validation formulas to verify data completeness.

Step-by-Step Solution

1
Understand validation rule execution mechanics
Confirm that validation rules run prior to saving a record and prevent saving when the formula condition evaluates to true.
Validation rules exist to enforce data quality by preventing invalid data entries from reaching the database.
2
Identify key validation formula functions
Recognize that functions such as ISBLANK are standard for verifying that essential data fields are filled.
Checking for blank fields is a core mechanism for data completeness.

Key Concept

Validation rules verify data quality before record save using formula expressions.
Question 208Question

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 209Question

An administrator created a new Record Type named 'VIP Support' on the Case object and assigned the 'VIP Case Page Layout' to the Support Agent profile for this record type. However, users assigned to the Support Agent profile report that the 'Type' picklist field still displays picklist values that should be restricted for VIP cases. Additionally, users assigned a specific permission set report they cannot select the 'VIP Support' record type when creating new cases. Which two administrative actions should the administrator perform to resolve these issues? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Edit the 'Type' picklist settings directly under the 'VIP Support' Record Type configuration to specify the allowed values.; Update the assigned Profile or Permission Set settings to grant access to the 'VIP Support' Record Type.

Answer

The administrator must edit the 'Type' picklist settings under the 'VIP Support' Record Type to specify available values, and update the assigned Profile or Permission Set settings to grant access to the 'VIP Support' Record Type.
To restrict picklist values for a specific record type, an administrator must edit the picklist field settings directly under that Record Type's configuration in Object Manager. Additionally, for users to select a record type upon record creation, access to that Record Type must be enabled in their Profile or assigned Permission Set.

Step-by-Step Solution

1
Navigate to Object Manager > Case > Record Types > VIP Support.
Locate the picklists available for editing under the record type details.
Creating a record type does not automatically restrict picklist values; available values must be customized explicitly per record type.
2
Edit the 'Type' picklist field under the VIP Support record type to remove unneeded values.
Only selected values are displayed when users create or edit a VIP Support case.
This ensures users see only the relevant options for this specific business process.
3
Navigate to Profiles or Permission Sets assigned to the affected users and update Record Type Settings.
The 'VIP Support' record type becomes available for selection during record creation.
Users cannot create records of a specific record type unless assigned access via their Profile or Permission Set.

Key Concept

Page Layouts, Record Types, and Picklist Assignments
Estimated Time:1m 30s
Question 210Question

A Salesforce administrator is evaluating data utility options for four separate data maintenance requirements within an organization. Match each administrative requirement to the appropriate tool and configuration.

Click a left item, then click its matching right item

Items

Upserting 40,000 Contact records while enforcing built-in duplicate matching rules to prevent creating duplicate records.
Automating a scheduled nightly export of 200,000 Case records using background command-line execution.
Performing a hard delete on 15,000 obsolete custom object records so they bypass the Recycle Bin.
Importing 85,000 Opportunity records into Salesforce from a desktop graphical user interface.

Matches

Show answer & explanation

Answer

1. Upserting 40,000 Contact records with duplicate matching maps to Data Import Wizard.
2. Automating a scheduled nightly export of 200,000 Case records maps to Data Loader Command Line Interface (CLI).
3. Performing a hard delete on 15,000 custom object records maps to Data Loader Desktop Client with Bulk API enabled.
4. Importing 85,000 Opportunity records maps to Data Loader Desktop Client with Standard SOAP API enabled.
Each requirement aligns directly with standard Salesforce utility constraints: Data Import Wizard handles up to 50,000 Contacts with duplicate prevention; Data Loader CLI supports automated background scripts; Data Loader with Bulk API enables hard deletion; and Data Loader Desktop client handles Opportunities and large volumes (>50,000 records).

Step-by-Step Solution

1
Analyze tool constraints for record limits and object support.
Data Import Wizard is limited to 50,000 records and supports Contacts with duplicate detection, but does not support Opportunities.
Identify which task can be handled by browser-based tools versus desktop utilities.
2
Evaluate automation and command-line execution requirements.
Nightly automated execution requires Data Loader CLI configuration files.
Browser tools and desktop GUIs require manual user interaction and cannot be natively scheduled via CLI scripts.
3
Determine requirements for hard deletion.
Hard deletion requires Data Loader with Bulk API enabled.
Standard SOAP API and Data Import Wizard send deleted records to the Recycle Bin rather than permanently purging them.

Key Concept

Selecting between Data Import Wizard and Data Loader based on record volume, object support, automation needs, and operation type.
Question 211Question

An administrator is configuring a validation rule on the custom object Asset_Service_Contract__c to enforce data quality standards. Business requirements state that whenever a contract status is set to 'Active', the custom field Renewal_Date__c must not be left blank, and the custom text field Compliance_Audit_Code__c must strictly follow a specific format starting with 'AUD-' followed by exactly three alphanumeric characters (such as 'AUD-101' or 'AUD-A12'). Which TWO validation rule formula syntax configurations will correctly enforce these data quality requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: AND( ISPICKVAL(Status__c, 'Active'), OR( ISBLANK(Renewal_Date__c), NOT(REGEX(Compliance_Audit_Code__c, 'AUD-[A-Za-z0-9]{3}')) ) ); AND( TEXT(Status__c) = 'Active', OR( ISBLANK(Renewal_Date__c), NOT(REGEX(Compliance_Audit_Code__c, 'AUD-[A-Za-z0-9]{3}')) ) )

Answer

The two correct validation rule formulas evaluate the status picklist using either ISPICKVAL or TEXT conversion, combined with an OR block containing ISBLANK for the date field and a negated REGEX function for format enforcement.
The correct validation rules evaluate whether the contract status is set to Active using either ISPICKVAL or TEXT status evaluation, combined with an inner OR block that checks if the renewal date is missing or if the compliance audit code fails the regular expression format test. Because validation rules block saving when the formula evaluates to TRUE, negating the REGEX match ensures incorrectly formatted codes trigger the error.

Step-by-Step Solution

1
Identify the criteria for triggering a validation error in Salesforce.
Validation rule formulas display an error message when the expression evaluates to TRUE.
The rule must evaluate to TRUE when the contract is Active AND either the Renewal_Date__c is missing OR the Compliance_Audit_Code__c does not follow the required pattern.
2
Evaluate picklist testing methods.
Both ISPICKVAL(Status__c, 'Active') and TEXT(Status__c) = 'Active' are valid methods for inspecting picklist fields in formula fields.
Standard text equality operators require converting picklist values using the TEXT function.
3
Construct the logical conditions for invalid data entry.
Use OR( ISBLANK(Renewal_Date__c), NOT(REGEX(Compliance_Audit_Code__c, 'AUD-[A-Za-z0-9]{3}')) ).
An error should occur if either data quality requirement is violated independently.

Key Concept

Validation rule formulas return TRUE to block record saving, requiring logical OR constructs to enforce multiple independent data completeness and pattern conditions.
Estimated Time:2m 0s
Question 212Question

A Salesforce administrator is configuring a new Custom Report Type to analyze Accounts and their associated Contacts, ensuring that Accounts without any associated Contacts are also displayed in reports. Which two steps must the administrator take during setup to fulfill this requirement? (Select TWO answers.)

Select all that apply

Show answer & explanation

Answer: Select Accounts as the primary object for the custom report type.; Configure the object relationship so that primary object records may or may not have related secondary object records.

Answer

The administrator must select Accounts as the primary object and configure the object relationship such that primary object records ('A') may or may not have related secondary object records ('B').
To include primary object records regardless of whether related child records exist, the primary object must be defined as Accounts, and the relationship setting must be set to 'Each "A" record may or may not have related "B" records' (outer join).

Step-by-Step Solution

1
Identify the primary object
Accounts is established as Object A in the custom report type setup.
The primary object represents the main record type from which the report structure begins.
2
Define the object relationship join type
Select 'Each "A" record may or may not have related "B" records'.
This 'with or without' relationship ensures an outer join, ensuring Accounts display regardless of whether associated Contact records exist.

Key Concept

Custom Report Type Object Relationships (Inner vs. Outer Joins)
Question 213Question

A sales operations lead at a manufacturing company frequently updates standard product specification sheets stored in Salesforce. The sales team requires that external clients who already possess a public link to a specification sheet will automatically view the updated document without needing a new public link generated and sent to them. Which action should the Salesforce administrator recommend to fulfill this requirement?

Show answer & explanation

Answer: Upload the updated document using the 'Upload New Version' button on the existing Salesforce File record page.

Answer

Upload the updated document using the 'Upload New Version' button on the existing Salesforce File record page.
In Salesforce Files, selecting 'Upload New Version' on an existing ContentDocument record preserves the document's underlying record ID and associated public links. Anyone accessing the original link will seamlessly see the newest version without administrative intervention.

Step-by-Step Solution

1
Identify the core requirement
The requirement is to update the contents of a shared file while keeping the existing public shared link active and pointed to the new content.
Generating new public links requires redistribution to external clients, which creates operational friction.
2
Evaluate Salesforce Files versioning capabilities
Salesforce Files supports file versioning. Uploading a new version on the File detail page updates the document content without changing the File ID or breaking existing shared links.
The file link reference remains identical while pointing directly to the latest published version.

Key Concept

Salesforce Files Versioning and Public Links
Question 214Question

A system administrator is configuring a Custom Report Type to analyze Accounts and their assigned Assets for an executive audit. The report must include all Accounts regardless of whether they have associated Asset records. Additionally, management wants to include details from the User record of the Account Owner's Manager without creating redundant custom formula fields on the Account object. Which two administration steps should be performed on the Custom Report Type to fulfill these requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Define the object relationship between Accounts (primary) and Assets (secondary) using the 'Each "A" record may or may not have related "B" records' join setting.; Use the 'Add fields related via lookup' feature in the Custom Report Type field layout editor to reference and add fields from the Manager lookup relationship.

Answer

The correct steps are to set the object relationship between Accounts and Assets to 'Each "A" record may or may not have related "B" records' (outer join) and to use 'Add fields related via lookup' in the Custom Report Type layout editor to add the Account Owner's Manager fields.
To show parent records regardless of child record presence, a custom report type must use an outer join ('with or without' related records). Additionally, referencing fields from related objects across up to 4 lookup levels is supported directly in the Custom Report Type layout editor using the 'Add fields related via lookup' feature.

Step-by-Step Solution

1
Determine the required object relationship setting for Custom Report Types.
Configuring Accounts as primary and Assets as secondary with 'Each "A" record may or may not have related "B" records' creates an outer join, allowing Accounts without Assets to display.
An inner join would exclude any Account that does not currently possess associated Asset records.
2
Determine how to access fields from related objects without custom formula fields.
In the Custom Report Type Field Layout page, click 'Add fields related via lookup' to traverse up to 4 relationship levels (Account -> Owner -> Manager).
This exposes fields from lookup objects directly into report sections for end users without cluttering the object schema with formula fields.

Key Concept

Custom Report Type Object Relationships and Layout Navigation via Lookup
Question 215Question

A Salesforce Administrator is designing a new Customer Success Health Dashboard in Lightning Experience to display account renewal metrics and support ticket volumes across different customer tiers. The administrator plans to implement dashboard filters and visual components fed by custom reports. Which two statements accurately describe the design constraints and component requirements for this dashboard? (Select 2)

Select all that apply

Show answer & explanation

Answer: A maximum of 3 dashboard filters can be added to a single Lightning dashboard.; Chart components require their underlying source reports to be grouped by at least one row or column.

Answer

The correct statements are that a maximum of 3 dashboard filters can be added to a single Lightning dashboard, and chart components require their underlying source reports to be grouped by at least one row or column.
The correct statements reflect core Salesforce dashboard constraints: a Lightning dashboard supports a maximum of 3 filters, and visual chart components require source reports formatted with at least one grouping (Summary or Matrix) to render data metrics.

Step-by-Step Solution

1
Evaluate dashboard filter limits in Lightning Experience.
Salesforce enforces a strict platform governor limit allowing up to 3 interactive dashboard filters per dashboard.
This maintains performance and user interface integrity when dynamically re-querying underlying report components.
2
Evaluate source report format requirements for chart components.
Chart components (bar, line, donut, funnel, pie) require grouped data (Summary or Matrix report formats).
A tabular report without groupings cannot aggregate values into data series needed to generate visual chart axes or segments.
3
Analyze security implications of dynamic dashboards and report formula types.
Dynamic running users enforce individual security access for dashboard views and underlying record drill-downs. Summary formulas cannot evaluate ungrouped tabular reports.
Security and report calculation rules follow strict platform models.

Key Concept

Dashboard Design, Components, and Dynamic Filters
Question 216Question

CloudKicks uses a Private sharing model for Accounts. An administrator created a custom Matching Rule on Account (matching Account Name and Billing City) and activated a corresponding Duplicate Rule on Account. The Duplicate Rule specifies 'Allow' on Create with both 'Alert' and 'Report' enabled. During testing, sales representatives are still able to create duplicate Account records that match existing accounts in the system without receiving an alert prompt or generating duplicate record sets. The administrator verifies that the Matching Rule and Duplicate Rule are active and that the criteria match the test data. Which configuration adjustment must the administrator make to ensure duplicate accounts owned by other users trigger the alert and report actions?

Show answer & explanation

Answer: Modify the Duplicate Rule setting under User Pass-Through from 'Enforce sharing rules' to 'Bypass sharing rules'.

Answer

Modify the Duplicate Rule setting under User Pass-Through from 'Enforce sharing rules' to 'Bypass sharing rules'.
In Salesforce Duplicate Management, Duplicate Rules can be configured to either 'Enforce sharing rules' or 'Bypass sharing rules'. When set to 'Enforce sharing rules' in an organization with Private OWD, the matching engine only compares records the current user has access to. Changing the rule to 'Bypass sharing rules' enables the system to evaluate all records in the org for duplicates, triggering alerts and logging records to duplicate record sets without revealing confidential fields to unauthorized users.

Step-by-Step Solution

1
Identify the data access constraint affecting duplicate detection.
Since Account Organization-Wide Defaults (OWD) are set to Private, users cannot view Account records owned by other users unless shared.
By default, duplicate rules honor record-level security unless explicitly configured otherwise.
2
Evaluate the duplicate rule security settings.
If a duplicate rule is set to 'Enforce sharing rules', the matching engine only compares the record being created against records visible to the running user.
Hidden duplicate records owned by other users will be ignored during duplicate evaluation.
3
Determine the required administrative setting change.
Changing the duplicate rule configuration to 'Bypass sharing rules' allows the matching engine to search all records across the organization while maintaining existing user UI access boundaries.
This guarantees duplicate detection and reporting across all accounts regardless of owner.

Key Concept

Duplicate Rule Security & Sharing Rule Bypass
Question 217Question

A System Administrator at a solar energy equipment manufacturer needs to allow sales reps to launch an external order-tracking web application directly from an Opportunity record. The solution must dynamically pass the Opportunity's Account ID in the web URL parameters, and the link must be displayed directly inside the record detail section of the page layout alongside field data. Which configuration element should the administrator create on the Opportunity object to meet this requirement?

Show answer & explanation

Answer: A Custom Detail Page Link configured with the web URL and merge field tokens.

Answer

A Custom Detail Page Link configured with the web URL and merge field tokens.
Custom Detail Page Links are designed specifically to launch external URLs populated with dynamic Salesforce merge fields (such as Opportunity or Account parameters) and are placed inside the record detail section of page layouts.

Step-by-Step Solution

1
Analyze UI placement and dynamic URL parameter requirements.
The requirement requests displaying a link inside the record detail section while passing dynamic field parameters (Account ID) to an external URL.
Different user interface actions have specific layout capabilities and UI target locations on record pages.
2
Evaluate custom link functionality against custom buttons and quick actions.
Custom Detail Page Links support standard web URL targets with merge fields and are positioned on record detail sections of page layouts.
Quick actions and custom buttons appear in action bars or page headers and serve different action workflows.

Key Concept

Distinguishing between Custom Links, Custom Buttons, and Quick Actions based on Lightning Experience UI placement and URL parameter requirements.
Question 218Question

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 219Question

An enterprise sales department requires specific account managers to create, edit, and share standardized Lightning Email Templates directly within the Salesforce Integration with Outlook pane. The administrator must grant these permissions exclusively to this select group of account managers without expanding permissions for other users who share the standard Sales User profile. Which two administrative actions are required to fulfill these business requirements?

Select all that apply

Show answer & explanation

Answer: Create and assign a permission set that includes the 'Create Lightning Email Templates' permission to the designated account managers.; Grant 'Edit' or 'Manage' access to the designated account managers on the specific public email template folder where the templates will be stored.

Answer

The administrator must create a permission set with the 'Create Lightning Email Templates' permission for the specified users and grant appropriate folder-level permissions (Edit or Manage) on the public email template folder.
Granting the 'Create Lightning Email Templates' permission via a Permission Set ensures that only the required account managers gain template creation rights without affecting other users sharing the baseline profile. Additionally, Lightning email template access is governed by folder-level permissions, so granting 'Edit' or 'Manage' access on the destination public folder allows those users to contribute templates accessible through the integration pane.

Step-by-Step Solution

1
Identify the additive permission strategy
Determine that assigning a Permission Set with 'Create Lightning Email Templates' is the correct approach to avoid profile duplication.
Additive capabilities for sub-groups of users assigned to a common profile should always be granted via permission sets.
2
Configure template folder access controls
Grant explicit 'Edit' or 'Manage' access on the target Public Email Template Folder.
Sharing and management of Lightning Email Templates are strictly governed by folder permissions.

Key Concept

Lightning Email Template Permissions and Folder Sharing in Email Integrations
Question 220Question

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
PreviousPage 11 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin