All practice questions

1784 questions

All types1,784 Multiple choice918 Multiple select587 Matching142 Ordering137

A Salesforce Administrator is building an autolaunched flow to process failed Equipment Audit records for a manufacturing facility. When an audit fails, the flow must retrieve all related child Audit Item records, set their status to 'Requires Re-inspection', and increment their internal inspection count by 1. The solution must handle high-volume updates efficiently without hitting transaction governor limits. Which Flow Builder design logic should the administrator implement?

Execute a Get Records element outside the loop, iterate through the retrieved collection, update field values using an Assignment element to append modified records to a new collection variable, and execute a single Update Records element outside the loop.

Iterate through the retrieved collection using a Loop element, and place an Update Records element inside the loop to commit field changes immediately for each Audit Item record.

Create a Roll-Up Summary field on the parent Equipment Audit object linked via a lookup relationship to automatically calculate and push the status change to child Audit Item records.

Use an Assignment element inside the loop to update the status field without assigning the updated picklist value to the Audit Item record type configuration.

Show answer & explanation

Answer: Execute a Get Records element outside the loop, iterate through the retrieved collection, update field values using an Assignment element to append modified records to a new collection variable, and execute a single Update Records element outside the loop.

Answer

The correct approach enforces Salesforce bulkification design standards. Using a Get Records element before the loop fetches all necessary records in a single query. Modifying field values with Assignment elements within the loop operates strictly in-memory. Appending updated items to a new record collection variable allows a single Update Records element placed after the loop to perform a bulk DML update, staying well within governor limits.

Step-by-Step Solution

Query records outside the loop

Use a single Get Records element to store all target child Audit Item records in a record collection variable.

Prevents issuing multiple SOQL queries inside loop iterations.

Iterate and modify using memory operations

Pass the collection into a Loop element. Inside the loop, use an Assignment element to update the field values on the loop current item, then use a second Assignment element to add the current item to a output record collection variable.

Assignment elements perform in-memory variable transformations without invoking database DML transactions.

Commit database updates bulkified

Connect the loop exit path to a single Update Records element configured to update the output record collection variable.

Consumes only one DML limit for the entire batch of updated child records.

Key Concept

Flow Bulkification and Logic Elements

Question 302Question →

A Salesforce Administrator at a medical device manufacturer is building a report on Account records to support an upcoming service contract renewal campaign. The operational leadership team has specified two primary requirements:
1. Group Accounts into three custom volume tiers ('Enterprise', 'Mid-Market', and 'Small Business') based on the standard Account Source picklist values without modifying schema or adding custom fields.
2. Filter the report to display Accounts that have related active Service Contracts, but do NOT have any open high-priority Support Cases.

Which TWO configuration choices or platform constraints must the administrator account for when building this report? (Select TWO.)

Select all that apply

Bucket fields can be defined on Picklist, Text, or Numeric fields to group values into custom categories directly within the report builder.

Cross Filters allow filtering parent Accounts with Service Contracts (subfiltered by Status = Active) and Cross Filters without Cases (subfiltered by Priority = High and Status != Closed).

A Bucket Field can evaluate data from parent and child relationship objects simultaneously using standard summary formula calculations.

A single Cross Filter block can query up to five distinct child objects at the same time without needing separate filter entries.

Show answer & explanation

Answer: Bucket fields can be defined on Picklist, Text, or Numeric fields to group values into custom categories directly within the report builder.; Cross Filters allow filtering parent Accounts with Service Contracts (subfiltered by Status = Active) and Cross Filters without Cases (subfiltered by Priority = High and Status != Closed).

Answer

The administrator must utilize a Bucket Field on the Account Source picklist field to categorize accounts into custom tiers without schema modifications, and apply dual Cross Filters (Accounts WITH Service Contracts subfiltered by Status, and Accounts WITHOUT Cases subfiltered by Priority and Status) to satisfy the filtering criteria.

The correct options accurately identify that Bucket Fields can be created directly on picklist fields to categorize values without modifying object schema, and that complex parent-child criteria require combining 'WITH' and 'WITHOUT' Cross Filters with specific subfilters.

Step-by-Step Solution

Evaluate the bucketing requirement

Confirm that Bucket Fields support Picklist fields directly in report builder without adding custom fields on the Account object.

Bucket fields provide an inline report-level transformation tool for Picklist, Text, and Number fields.

Evaluate the relationship filtering requirement

Configure two separate Cross Filters: one for 'Accounts WITH Service Contracts' (subfiltered by Active status) and another for 'Accounts WITHOUT Cases' (subfiltered by High priority open cases).

Salesforce reports require distinct Cross Filters to specify separate WITH and WITHOUT child object logic.

Verify feature limits and invalid configurations

Rule out using bucket fields for cross-object summary logic or expecting a single cross filter block to evaluate multiple child objects simultaneously.

Bucket fields operate row-by-row on single fields, and each Cross Filter evaluates only one related child object.

Key Concept

Report Bucketing and Cross Filter Logic

Question 303Question →

A Salesforce System Administrator at Universal Containers is tasked with configuring a Matrix Report on closed Support Cases. The report is grouped by Support Tier (rows) and Closed Month (columns). The Vice President of Support has defined two specific reporting requirements:

1. Calculate the elapsed time in days between CreatedDate and ClosedDate for each individual case record displayed in the report details.
2. Calculate the percentage contribution of each Support Tier's case volume relative to the total case volume of the respective Closed Month column.

Which configuration strategy should the administrator execute to satisfy both requirements within the report builder?

Create a Row-Level Formula to calculate elapsed days for each individual record, and create a Summary Formula utilizing the PARENTGROUPVAL function to calculate the column percentage contribution.

Create a Summary Formula using RowCount to evaluate elapsed days for each individual record, and create a Row-Level Formula using PARENTGROUPVAL to compute the monthly column percentage contribution.

Create a Roll-Up Summary field on the Account object to compute elapsed days for each individual case, and create a Summary Formula using the PREVGROUPVAL function to compute the monthly column percentage contribution.

Create a Row-Level Formula to calculate the elapsed days for each individual record, and create a second Row-Level Formula to aggregate case volume percentages across the report grouping levels.

Show answer & explanation

Answer: Create a Row-Level Formula to calculate elapsed days for each individual record, and create a Summary Formula utilizing the PARENTGROUPVAL function to calculate the column percentage contribution.

Answer

Create a Row-Level Formula to calculate elapsed days for each individual record, and create a Summary Formula utilizing the PARENTGROUPVAL function to calculate the column percentage contribution.

Row-level formulas evaluate record-by-record data, which is necessary to calculate the difference between CreatedDate and ClosedDate for each individual case record. Summary formulas operate on aggregated data at group or grand summary levels; specifically, PARENTGROUPVAL allows comparing a specific subgroup's row count against a parent column grouping total in a matrix report.

Step-by-Step Solution

Determine the formula type required for evaluating record-level field differences.

Row-Level Formula selected for calculating elapsed days per individual case record.

Row-level formulas execute calculations on every individual record line item in the report dataset.

Determine the formula type and function required for parent group percentage contributions in a matrix layout.

Summary Formula utilizing PARENTGROUPVAL selected.

PARENTGROUPVAL allows a summary formula to reference aggregate values at higher parent grouping levels (e.g., column total) to derive percentage contributions of subgroups.

Synthesize both formula configurations within the report builder options.

Row-level formula handles line-item duration while Summary formula with PARENTGROUPVAL handles parent column percentage.

Combines individual record processing with multi-level matrix summary analytics.

Key Concept

Row-Level Formula vs. Summary Formula PARENTGROUPVAL Matrix Aggregation

Estimated Time:3m 0s

Question 304Question →

A Salesforce Administrator at Horizon Travel Support is configuring a Lightning Service Console application for Tier 2 customer support agents. The support manager requests that whenever an agent opens a Case record from an associated Account record view, the Case record must automatically open as a subtab under the parent Account primary tab rather than opening as an independent workspace primary tab. Which console configuration setting should the administrator adjust in App Manager to meet this requirement?

Configure Navigation Rules for the Lightning Console app in App Manager to set Case as a subtab of Account.

Create a custom Permission Set granting Console Navigation Override access and assign it to Tier 2 agents.

Modify the Component Visibility rules on the Case Lightning Record Page using Dynamic Forms in Lightning App Builder.

Set up a Case Assignment Rule entry that automatically reassigns subtab cases to the Tier 2 support queue.

Show answer & explanation

Answer: Configure Navigation Rules for the Lightning Console app in App Manager to set Case as a subtab of Account.

Answer

Configure Navigation Rules for the Lightning Console app in App Manager to set Case as a subtab of Account.

In Salesforce Lightning Console apps, Navigation Rules configured within App Manager dictate how records open within the workspace. By setting Case records to open as subtabs of Account records, the system ensures that opening a related Case from an Account record view nests the Case neatly under the corresponding Account primary tab.

Step-by-Step Solution

Navigate to Setup and search for App Manager.

App Manager displays all installed and custom Lightning applications.

Console application settings, including tab structures and navigation rules, are managed centrally within App Manager.

Locate the Lightning Service Console app and select Edit from the action menu.

App Settings navigation panel opens.

Allows editing configuration details specific to the target console app.

Select Navigation Rules, find the Case object, and set its parent relationship so it opens as a subtab of Account.

When agents navigate to a Case from an Account in the console, the Case automatically docks as a subtab beneath that Account.

Navigation Rules explicitly define primary tab and subtab relationships for related objects within Lightning Console applications.

Key Concept

Lightning Service Console Navigation Rules Configuration

Question 305Question →

An organization sets the Organization-Wide Default (OWD) sharing setting for the Opportunity object to Private. A Salesforce administrator builds an executive pipeline dashboard stored in a shared dashboard folder that all sales representatives can view. The dashboard is explicitly configured to run as a static user—the Vice President of Sales—who possesses full 'View All' data access across all corporate opportunities.

When a regional sales representative views the dashboard, the dashboard components calculate and display aggregate pipeline totals across all global territories ( $15\text{M}$ ). However, when the same sales representative clicks on a component to drill down into the underlying source report, the resulting report displays only $500{}000$ , consisting strictly of records owned by or shared directly with that sales representative.

Which statement accurately explains the cause of this data discrepancy between the dashboard components and the opened source report?

Dashboard components calculate and display aggregated data based on the security access of the static running user, whereas opening the underlying source report evaluates record accessibility using the logged-in user's own security permissions.

The dynamic dashboard feature automatically overrides source report folder access and applies role hierarchy filtering whenever a viewer holds a lower role than the specified running user.

Folder access granted on the dashboard level implicitly elevates the logged-in user's record visibility on component summaries, but source report folders require explicit 'Manage' access to view records outside the user's territory.

The Vice President's Field-Level Security (FLS) overrides record sharing rules for dashboard visualizations, while the sales representative's profile settings restrict formula fields on the source report.

Show answer & explanation

Answer: Dashboard components calculate and display aggregated data based on the security access of the static running user, whereas opening the underlying source report evaluates record accessibility using the logged-in user's own security permissions.

Answer

Dashboard components evaluate data using the security context of the static running user, while navigating to the source report runs the report under the security context of the logged-in user.

The correct explanation accurately distinguishes between how dashboard components and source reports evaluate data security. A static running user dictates the security context for rendering component metrics, allowing viewers to see aggregate data based on the running user's access (in this case, the VP's 'View All' access). However, when a user clicks the component to open the underlying source report, Salesforce enforces standard record security for the logged-in viewer, restricting report rows to only those records accessible under the sales representative's Private OWD access.

Step-by-Step Solution

Analyze the dashboard security configuration context.

The dashboard runs under a static running user (VP of Sales) who has 'View All' permissions on Opportunities.

Static running users determine the data visibility context for all component summaries displayed on the dashboard grid.

Evaluate the underlying source report execution context upon user drill-down.

When the sales representative clicks the component, Salesforce executes the source report using the logged-in user's security context.

Source reports always enforce the logged-in viewer's security credentials, Organization-Wide Defaults (OWD), role hierarchy permissions, and sharing rules regardless of the dashboard's static running user setting.

Compare component summary values against report drill-down values.

The component reflects the VP's

15M global total, while the source report filters results to the representative's

500,000 private allocation.

This behavioral separation between component execution context and source report execution context causes the observed discrepancy.

Key Concept

Static Dashboard Running User vs. Source Report Execution Context

Question 306Question →

A Salesforce administrator at a subscription services company needs to import $30{}000$ records into a custom object named Subscription__c. The operation requires preventing duplicate records by matching on an External ID field. Company IT security policies restrict the installation of desktop client software on administrative workstations. Which data management tool should the administrator select to fulfill these requirements?

Data Import Wizard, because it operates via the web browser, supports up to

50{}000

custom object records, and enables matching by External ID.

Data Loader desktop client, because the Data Import Wizard cannot perform record matching or deduplication using External ID fields.

Data Loader web application, because the Data Import Wizard is restricted exclusively to importing standard objects such as Accounts and Contacts.

Data Import Wizard, because it allows automated bulk background exports up to

5{}000{}000

records without user session management.

Show answer & explanation

Answer: Data Import Wizard, because it operates via the web browser, supports up to $50{}000$ custom object records, and enables matching by External ID.

Answer

Data Import Wizard, because it operates via the web browser, supports up to

50{}000

custom object records, and enables matching by External ID.

The correct answer specifies Data Import Wizard because it is entirely web-based (satisfying the constraint against installing desktop software), natively supports up to

50{}000

records for all custom objects, and provides built-in matching using External ID fields to prevent duplicates.

Step-by-Step Solution

Evaluate record volume and environment constraints.

The requirement involves

30{}000

records (within the

50{}000

limit of Data Import Wizard) and specifies that no desktop software can be installed.

Data Loader requires installing a desktop client application, whereas Data Import Wizard is accessible directly through the Salesforce setup browser UI.

Verify object support for the target entity.

The target object is a custom object (Subscription__c). Data Import Wizard fully supports all custom objects.

Custom objects are supported up to

50{}000

records in Data Import Wizard.

Confirm duplicate handling capability.

Data Import Wizard natively supports matching existing records by External ID to perform upsert operations and prevent duplicates.

External ID matching is a standard feature when mapping fields in the Data Import Wizard.

Key Concept

Selecting between Data Import Wizard and Data Loader based on client installation requirements, record volume limits (

50{}000

), object type support, and External ID matching capabilities.

Question 307Question →

A sales manager needs a report listing all Account records that currently do not have any associated active Opportunities. Which report filter feature should the administrator use to filter Accounts based on the presence or absence of related child records?

Cross Filter using the 'without' relationship operator

Summary Formula evaluating child record counts

Roll-Up Summary Field filter on the parent Account object

Field filter with the 'includes' operator on the Opportunity field

Show answer & explanation

Answer: Cross Filter using the 'without' relationship operator

Answer

Cross Filter using the 'without' relationship operator

Cross Filters allow administrators to filter report results by comparing parent records against related child objects using 'with' or 'without' operators.

Step-by-Step Solution

Identify the core requirement

The requirement is to display parent Account records based on the absence of related child Opportunity records.

Standard field filters evaluate individual field criteria on target records, but relationship cross-object filtering requires specialized filtering functionality.

Evaluate available Salesforce reporting features

Cross Filters enable reports to include or exclude parent records based on relationships to child objects (e.g., Accounts WITH or WITHOUT Opportunities).

Using a Cross Filter with 'Accounts WITHOUT Opportunities' directly satisfies the business requirement.

Key Concept

Cross Filters in Salesforce Reports

Question 308Question →

Pinnacle Financial Operations is launching a new Advisory Services division alongside its existing Asset Management business. The Advisory Services sales team requires a custom sales pipeline with unique opportunity stages, probabilities, and forecast categories that differ from the standard sales pipeline. Which TWO administrative actions must the Salesforce administrator perform to fulfill this setup?

Select all that apply

Create a new Sales Process to select and map the specific opportunity stages required for the Advisory Services pipeline.

Create a new Opportunity Record Type for Advisory Services and associate it with the newly created Sales Process.

Assign the custom opportunity stage picklist values directly to the new Opportunity Record Type edit page without defining a Sales Process.

Configure profile-level field security to display the designated opportunity stages exclusively for Advisory Services user profiles.

Show answer & explanation

Answer: Create a new Sales Process to select and map the specific opportunity stages required for the Advisory Services pipeline.; Create a new Opportunity Record Type for Advisory Services and associate it with the newly created Sales Process.

Answer

The administrator must create a dedicated Sales Process containing the appropriate opportunity stages, and assign that Sales Process to a newly created Opportunity Record Type.

To support separate sales pipelines with distinct opportunity stages, administrators must first create a Sales Process containing the desired stage values. Second, a new Opportunity Record Type must be created and linked to that Sales Process. This ensures that users creating opportunities with that record type follow the correct stage progression.

Step-by-Step Solution

Define Opportunity Stages and Sales Process

A customized Sales Process is established containing only the stage picklist values, probabilities, and forecast categories needed for Advisory Services.

Opportunity stage picklists on standard object fields are global, but a Sales Process filters which stages apply to a given pipeline.

Create Opportunity Record Type and Link Sales Process

The Opportunity Record Type links page layouts and business process rules to the designated Sales Process.

An Opportunity Record Type cannot function without a Sales Process association to govern stage picklist values.

Key Concept

Sales Processes and Opportunity Stages

Question 309Question →

A Finance Operations Lead wants to evaluate revenue metrics for closed-won opportunities. The report must display aggregated monetary totals grouped simultaneously by Fiscal Quarter along the rows and Sales Region across the columns, including subtotals for both dimensions and an overall grand total. Which report format should a Salesforce Administrator select to meet this requirement?

Summary report format

Matrix report format

Tabular report format

Joined report format

Show answer & explanation

Answer: Matrix report format

Answer

Matrix report format

The Matrix report format is specifically designed to summarize numerical data across two independent dimensions simultaneously—grouping records by rows (such as Fiscal Quarter) and by columns (such as Sales Region)—and providing subtotals and grand totals for both axes.

Step-by-Step Solution

Analyze the reporting requirement

Identified the need to group Opportunity data across two distinct axes simultaneously (Fiscal Quarter on rows, Sales Region on columns).

Determining the required axes for grouping dictates which report format is structurally compatible.

Evaluate standard Salesforce report format capabilities

Matrix format natively supports two-dimensional grouping across rows and columns with cross-tabulated subtotals and grand totals.

Tabular formats do not support grouping, Summary formats only support row groupings, and Joined formats are meant for combining multiple report blocks.

Select the optimal format

Choose Matrix report format.

It fulfills the two-dimensional grouping and cross-tabulation requirements efficiently.

Key Concept

Selecting Report Formats (Matrix vs. Summary vs. Tabular vs. Joined)

Estimated Time:1m 0s

Question 310Question →

An operations manager requests that a follow-up Task be automatically assigned to a supervisor whenever an existing Case is modified and its status changes to 'Escalated'. The task should only trigger when the record is changed to meet this condition, not on subsequent edits while it remains escalated. Which evaluation criteria should be configured on the Workflow Rule?

Created, and any time it's edited to subsequently meet criteria

Created, and every time it's edited

Created

Updated, but not created

Show answer & explanation

Answer: Created, and any time it's edited to subsequently meet criteria

Answer

Created, and any time it's edited to subsequently meet criteria

The setting 'Created, and any time it's edited to subsequently meet criteria' evaluates rule criteria only when a record is newly created or when an edit changes the record from not meeting the criteria to meeting them. This prevents redundant task generation on edits where the record was already in an escalated state.

Step-by-Step Solution

Analyze the requirement for workflow rule execution frequency.

The automation must fire only when a record state changes to meet criteria, not during subsequent edits.

Evaluating record state transitions prevents repeated task generation on unchanged criteria states.

Identify the corresponding Salesforce Workflow Rule evaluation criteria.

'Created, and any time it's edited to subsequently meet criteria' checks for condition transition.

This specific setting triggers actions only when an edit causes a record to meet criteria after previously not meeting them.

Key Concept

Workflow Rule Evaluation Criteria

Question 311Question →

A regional sales manager asks the Salesforce administrator to grant two senior account executives the ability to create and edit shared Lightning Email Templates in public folders for the entire sales team, while standard sales representatives should only be able to select and send emails using these templates from the Gmail Integration pane. How should the administrator fulfill this requirement following Salesforce security best practices?

Create and assign a permission set containing the 'Manage Public Lightning Email Templates' system permission to the two senior account executives.

Modify the standard Sales User profile to grant the 'Manage Public Lightning Email Templates' permission to all sales team members.

Assign a custom profile with the 'Modify All Data' system permission to the senior account executives.

Clone the standard Sales User profile, enable the 'Create Lightning Email Templates' permission, and reassign the senior account executives to this new profile.

Show answer & explanation

Answer: Create and assign a permission set containing the 'Manage Public Lightning Email Templates' system permission to the two senior account executives.

Answer

Create and assign a permission set containing the 'Manage Public Lightning Email Templates' system permission to the two senior account executives.

The option advocating for a permission set containing the 'Manage Public Lightning Email Templates' permission is correct. Using a permission set adheres to Salesforce best practices by granting elevated administrative capabilities only to the two designated senior account executives while preserving the standard Sales User profile for the rest of the team.

Step-by-Step Solution

Analyze access requirements for email template management

Senior executives require administrative access to create and manage shared public templates, whereas standard reps only require access to view and use templates.

Salesforce security best practices mandate restricting template creation/editing permissions to authorized users.

Determine the appropriate security mechanism for additive permissions

Use a Permission Set rather than creating or modifying User Profiles.

Permission sets allow administrators to grant specialized permissions to selective users without impacting the base profile of all team members.

Identify the exact system permission required for public template management

Select the 'Manage Public Lightning Email Templates' permission.

This permission specifically grants the capability to create, edit, and delete Lightning email templates stored in public folders.

Key Concept

Lightning Email Template Permissions and Folder Access Management

Estimated Time:1m 15s

Question 312Question →

A Salesforce administrator is tasked with preventing duplicate Lead records based on custom criteria. What is the correct sequence of steps the administrator must perform to configure and enforce custom duplicate management?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with creating the custom Matching Rule criteria, followed by activating the Matching Rule, creating the Duplicate Rule referencing the active Matching Rule, and finally setting the enforcement actions and activating the Duplicate Rule.

To set up duplicate control, an administrator must first define the matching criteria via a Matching Rule. Next, the Matching Rule must be activated so Salesforce can process the logic. Then, a Duplicate Rule is created to reference the active Matching Rule. Finally, enforcement actions (Block or Allow/Alert) are configured and the Duplicate Rule is activated to take effect.

Step-by-Step Solution

Build the Matching Rule definition

Defines which fields (e.g., Email, Phone) and matching algorithms are used to identify duplicate records.

You must establish the identification logic before enforcing any behavior.

Activate the Matching Rule

Makes the matching criteria available for selection in Duplicate Rules.

Salesforce prevents unactivated matching rules from being selected inside duplicate rules.

Create the Duplicate Rule

Associates the activated matching rule with the target object.

Duplicate rules control the user experience and execution context when a match occurs.

Configure actions and activate the Duplicate Rule

Enforces blocking or alerting upon record creation/edit.

The duplicate rule does not actively prevent or report duplicates until it is enabled/activated.

Key Concept

Order of configuration for Salesforce Matching Rules and Duplicate Rules

Question 313Question →

Apex Global Operations wants to provide regional sales managers with insights into their team's opportunity performance while maintaining strict data security. The administrator is evaluating whether to configure a static dashboard using the VP of Sales as the running user or to set up a dynamic dashboard where the running user is set to 'the logged-in user'. Which two statements accurately describe the security and data visibility implications of these dashboard running user settings? (Select 2 options)

Select all that apply

When configured as a dynamic dashboard, data displayed in components is restricted to what the logged-in user has access to based on Organization-Wide Defaults, role hierarchy, and sharing rules.

Configuring a static dashboard with the VP of Sales as the running user grants viewing users the ability to drill down and edit underlying records that they otherwise cannot access.

Dynamic dashboards allow logged-in users to override organization-wide defaults and export detailed report data for records outside their assigned territory.

A static dashboard set to run as the VP of Sales allows all users with access to the dashboard folder to view aggregated data on components, even for records those users cannot individually access.

Setting a dynamic dashboard automatically overrides folder access settings, granting all internal users view access to the dashboard regardless of folder permissions.

Show answer & explanation

Answer: When configured as a dynamic dashboard, data displayed in components is restricted to what the logged-in user has access to based on Organization-Wide Defaults, role hierarchy, and sharing rules.; A static dashboard set to run as the VP of Sales allows all users with access to the dashboard folder to view aggregated data on components, even for records those users cannot individually access.

Answer

The correct statements are that dynamic dashboards restrict displayed data strictly to what the logged-in user has access to based on OWD and sharing permissions, and static dashboards allow viewers to see summarized component metrics based on the static running user's access level without granting direct access to the underlying records.

In Salesforce, dynamic dashboards execute using the logged-in user's context, displaying only data they have security access to view. Conversely, static dashboards display component data calculated using the designated running user's context, allowing viewers to see aggregated totals while continuing to enforce standard record-level sharing when users attempt to access underlying records.

Step-by-Step Solution

Analyze static running user security behavior

Components display data according to the running user's data security context (e.g., VP of Sales), allowing viewers to see aggregate metric totals without elevating their permissions to view or edit individual underlying records.

Static running user configurations determine component data visibility at the dashboard level while preserving underlying record sharing controls.

Analyze dynamic running user security behavior

Components dynamically recalculate data based on the logged-in viewer's security credentials, adhering to OWD, role hierarchy, and sharing rules.

Dynamic dashboards ensure that users only see data they are explicitly authorized to view.

Evaluate folder access vs. running user settings

Folder sharing determines who can open the dashboard, while running user settings determine what data is displayed inside the dashboard.

Folder access and running user settings operate independently as distinct layers of dashboard security.

Key Concept

Dashboard Running User and Data Security

Question 314Question →

Apex Global Logistics uses a custom object named Vendor_Evaluation__c to conduct performance reviews on third-party suppliers. Business policy mandates that general employees must only be able to view and edit Vendor_Evaluation__c records that they personally own. However, managers must automatically gain access to all evaluation records owned by their subordinates in the role hierarchy. Which configuration should the administrator implement to satisfy these access requirements?

Set the Organization-Wide Default (OWD) for Vendor_Evaluation__c to Private, and leave the Grant Access Using Hierarchies checkbox selected.

Set the Organization-Wide Default (OWD) for Vendor_Evaluation__c to Private, and deselect the Grant Access Using Hierarchies checkbox.

Set the Organization-Wide Default (OWD) for Vendor_Evaluation__c to Public Read-Only, and assign a Permission Set to restrict viewing access for non-owners.

Create a Profile that restricts view access to records owned by other users, and assign this profile to all non-manager employees.

Show answer & explanation

Answer: Set the Organization-Wide Default (OWD) for Vendor_Evaluation__c to Private, and leave the Grant Access Using Hierarchies checkbox selected.

Answer

Set the Organization-Wide Default (OWD) for the custom object to Private while keeping the 'Grant Access Using Hierarchies' setting enabled.

Setting the Organization-Wide Default (OWD) to Private restricts baseline record access so users can only view and edit records they own. For custom objects, the 'Grant Access Using Hierarchies' option is checked by default, which ensures that managers higher in the role hierarchy automatically inherit access to records owned by their direct and indirect reports.

Step-by-Step Solution

Determine the baseline record access requirement.

Since non-owners should not view other users' records, the Organization-Wide Default (OWD) must be set to Private.

OWD establishes the most restrictive baseline access level for all users in the organization.

Evaluate role hierarchy access behavior for custom objects.

Ensure 'Grant Access Using Hierarchies' remains checked for Vendor_Evaluation__c.

By default, custom objects have 'Grant Access Using Hierarchies' enabled, allowing users above record owners in the role hierarchy to access the records.

Key Concept

Organization-Wide Defaults (OWD) and Role Hierarchy Access

Question 315Question →

A Salesforce administrator at a maritime shipping firm needs to convert an existing Lookup relationship field on the custom object Cargo_Container__c to a Master-Detail relationship with the Vessel__c object to enable summary reporting. When attempting to convert the field data type in Object Manager, Salesforce prevents the change. Which action must the administrator take to successfully complete the data type conversion?

Populate the Lookup field on all existing Cargo_Container__c records so that no record contains a null value.

Create a Roll-Up Summary field directly on the Vessel__c object referencing the existing Lookup relationship.

Configure Lead custom field mapping to link the Cargo_Container__c field to the Vessel__c object.

Assign the Lookup field to all available Record Types on the Cargo_Container__c object layout.

Show answer & explanation

Answer: Populate the Lookup field on all existing Cargo_Container__c records so that no record contains a null value.

Answer

The administrator must populate the Lookup field on all existing child records (Cargo_Container__c) so that no record contains a blank/null value before converting the field data type to a Master-Detail relationship.

In Salesforce, converting a Lookup relationship to a Master-Detail relationship requires that every existing record on the detail custom object has a populated value in the lookup field. If any record has a null value, the system blocks the conversion to maintain mandatory relationship integrity.

Step-by-Step Solution

Identify the data type conversion prerequisites for Salesforce relationship fields.

Converting a Lookup relationship to a Master-Detail relationship requires that all existing records on the detail object contain a valid parent record reference.

Master-Detail relationships strictly enforce data integrity, requiring mandatory parent references on all child records.

Audit existing records on the child object (Cargo_Container__c).

Locate records where the Vessel__c lookup field is blank.

If any child record lacks a value, Salesforce blocks the data type conversion.

Populate missing values and complete the conversion.

Update all blank lookup fields with valid Vessel__c record references and convert the data type in Object Manager.

Once all child records are populated, Salesforce permits changing the relationship type to Master-Detail.

Key Concept

Converting Lookup Relationships to Master-Detail Relationships

Question 316Question →

A Salesforce administrator at a freight logistics company is configuring custom fields on a parent Freight_Shipment__c object and a child Package__c object. The administrator needs to display the total calculated weight of all associated packages directly on the Freight_Shipment__c detail page. However, when attempting to create a new custom Roll-Up Summary field on the parent object, the option is unavailable because the objects are currently connected via a Lookup relationship. Which field configuration step is required to enable the Roll-Up Summary data type on the parent object?

Convert the relationship on the Package object from a Lookup relationship to a Master-Detail relationship.

Configure Lead Custom Field Mapping to link the child object weight field directly to the parent object.

Assign the existing Lookup field to all available Record Types on the child object.

Delete all existing detail records on the child object so the system enables roll-up capabilities on the Lookup relationship.

Show answer & explanation

Answer: Convert the relationship on the Package object from a Lookup relationship to a Master-Detail relationship.

Answer

Convert the relationship on the child Package object from a Lookup relationship to a Master-Detail relationship.

Roll-Up Summary fields calculate metrics such as SUM, COUNT, MIN, or MAX from child records, but in declarative Salesforce setup, they can only be created on the master object of a Master-Detail relationship. Converting the lookup field on the child Package object to a Master-Detail relationship fulfills this system prerequisite.

Step-by-Step Solution

Identify the data requirement

The requirement calls for summarizing child record data (Package weight) on a parent record (Freight Shipment).

Roll-Up Summary fields calculate COUNT, SUM, MIN, or MAX of related records.

Evaluate relationship prerequisite for Roll-Up Summary fields

Roll-Up Summary fields can only be created on the master object in a Master-Detail relationship.

Standard Lookup relationships do not enforce the strict parent-child hierarchy required for automatic roll-up calculations.

Determine the necessary configuration change

Convert the existing Lookup relationship field on the Package object to a Master-Detail relationship.

Once converted to a Master-Detail relationship, the Roll-Up Summary field option becomes available on the parent Freight Shipment object.

Key Concept

Master-Detail vs. Lookup Relationship Roll-Up Summary Capabilities

Question 317Question →

A company defined several official company holiday records in Salesforce. However, case escalation rules are still advancing and triggering actions on those holiday dates for cases associated with the APAC Support schedule. What configuration step must the administrator take to ensure the holidays suspend case escalation timers for APAC Support?

Add the created holiday records to the APAC Support Business Hours schedule.

Change the Organization Default Time Zone setting to match the APAC regional time zone.

Create a Case Assignment Rule to route new cases to an off-hours queue on designated holiday dates.

Update the default Web-to-Case owner settings to suspend submission processing during holidays.

Show answer & explanation

Answer: Add the created holiday records to the APAC Support Business Hours schedule.

Answer

Add the created holiday records to the APAC Support Business Hours schedule.

In Salesforce, creating a holiday record in Setup does not automatically apply it to every schedule. An administrator must explicitly associate the holiday record with each relevant Business Hours schedule (such as APAC Support). Once associated, Salesforce pauses escalation rules and milestone resolution clocks during the specified holiday dates.

Step-by-Step Solution

Identify how Salesforce processes Business Hours and Holidays.

Recognize that creating a Holiday record in Setup is a standalone step.

Holiday records do not automatically apply across all business hours schedules in an org.

Determine the necessary administrative link between Business Hours and Holidays.

Associate the Holiday records with the specific APAC Support Business Hours entry.

When a holiday is linked to a Business Hours schedule, Salesforce automatically subtracts holiday hours from escalation calculations and milestone targets.

Key Concept

Holiday Association with Business Hours

Question 318Question →

An administrator at Cloud Kicks needs to restrict access to a sensitive custom field, Executive_Notes__c, on the Account object. All members of the Account Management team share a custom profile that grants access to Account records. However, only two team leads require access to view and edit Executive_Notes__c. This field must remain completely hidden from all other Account Management team members across reports, list views, search results, and API integrations. Which solution meets these security requirements while following Salesforce administrative best practices?

Set Field-Level Security for Executive_Notes__c to remove Read and Edit access on the base Account Management profile, then assign a Permission Set granting Read and Edit access to the two team leads.

Hide the Executive_Notes__c field on the Account Lightning Record Page by applying Dynamic Forms component visibility rules targeted at the team leads' user roles.

Clone the Account Management profile to create a dedicated Team Lead profile with Read and Edit access to Executive_Notes__c, and reassign the two team leads to this new profile.

Add the corporate network IP range to Organization-Wide Network Access to enforce profile-level field visibility rules for Executive_Notes__c across API connections.

Show answer & explanation

Answer: Set Field-Level Security for Executive_Notes__c to remove Read and Edit access on the base Account Management profile, then assign a Permission Set granting Read and Edit access to the two team leads.

Answer

Field-Level Security (FLS) controls field access universally across all Salesforce tools, including reports, list views, search results, and API integrations. Removing access on the shared base profile and granting access to specific users via a Permission Set adheres to the principle of least privilege while maintaining a clean, scalable profile architecture.

Step-by-Step Solution

Determine the required security level across interfaces.

Field-Level Security (FLS) is identified as the required security mechanism because access must be restricted across UI, API, reports, and list views.

Page Layouts and Dynamic Forms component visibility only affect record detail UI pages, whereas FLS enforces security at the platform database level.

Configure baseline profile access.

Remove Read and Edit permissions for Executive_Notes__c on the shared Account Management profile.

This establishes a restrictive baseline for all users assigned to the profile.

Grant elevated access to specific users.

Create a Permission Set with Read and Edit access to Executive_Notes__c and assign it to the two team leads.

Permission Sets allow administrators to grant additive permissions without creating duplicate profiles for minor permission variations.

Key Concept

Field-Level Security and Permission Sets vs. Profiles

Question 319Question →

An administrator at a manufacturing company needs to grant three inventory specialists the ability to edit a custom field named 'Safety Inspection Date' on the Asset object. These three specialists are assigned to a baseline profile shared by fifty other warehouse team members who must not be granted access to edit this field. Which administrative action adheres to Salesforce security best practices to meet this requirement?

Create a Permission Set that grants Read and Edit access to the Safety Inspection Date field, and assign it to the three inventory specialists.

Create a new custom Profile with Edit access to the field, and reassign the three inventory specialists to this new Profile.

Modify the existing baseline Profile to grant Edit access to the field, then remove field visibility from page layouts assigned to the remaining fifty team members.

Clone the baseline Profile, grant Edit access to the field in the cloned Profile, and reassign all fifty other warehouse team members to the cloned Profile.

Show answer & explanation

Answer: Create a Permission Set that grants Read and Edit access to the Safety Inspection Date field, and assign it to the three inventory specialists.

Answer

Create a Permission Set that grants Read and Edit access to the Safety Inspection Date field, and assign it to the three inventory specialists.

The correct approach is to create a Permission Set granting Read and Edit access to the Safety Inspection Date field and assign it directly to the three inventory specialists. In Salesforce, profiles set the minimum baseline permissions, while permission sets are used to grant additive permissions to specific users without modifying their baseline profile or creating redundant profiles.

Step-by-Step Solution

Analyze the baseline access requirements and user assignments.

Identified that fifty-three users share the same baseline profile, but only three users need additional field-level edit permissions.

Salesforce security best practices require keeping profiles minimal for broad baseline access and extending privileges additively.

Evaluate the mechanism for granting additive permissions.

Determine that a Permission Set allows selective assignment of field-level security (Read and Edit) to specific users without altering profile assignments.

Permission sets grant additive permissions flexibly across users sharing different or identical profiles.

Select the correct administrative action.

Creating a Permission Set for the custom field and assigning it to the three specialists fulfills the requirement securely and efficiently.

Avoids profile proliferation and ensures other warehouse team members maintain restricted access.

Key Concept

Using Permission Sets to grant additive field-level permissions to specific users without creating redundant profiles.

Estimated Time:1m 30s

Question 320Question →

A Salesforce administrator is tasked with updating the organization-wide security baseline so that user accounts lock out after five consecutive failed login attempts. Which location in Setup should the administrator access to configure this default requirement?

Password Policies

Session Settings

Network Access

Permission Sets

Show answer & explanation

Answer: Password Policies

Answer

Password Policies in Setup

Password Policies in Setup is the centralized management menu for organization-wide default password security options, including maximum invalid login attempts, lockout duration, and password expiration rules.

Step-by-Step Solution

Identify the administrative requirement.

The requirement is to set an organization-wide default for maximum failed login attempts leading to account lockout.

Lockout rules and password restrictions at the organization level are controlled by Password Policies.

Determine the correct Setup area for organization-wide password defaults.

Access Setup and search for Password Policies.

Organization defaults for password complexity, expiration, and login lockouts are managed globally under Password Policies in Setup.

Key Concept

Organization-wide Password Policies control default account lockout limits and password security parameters.

PreviousPage 16 / 90Next

All practice questions

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept