All practice questions

1784 questions

All types1,784 Multiple choice918 Multiple select587 Matching142 Ordering137

Support agents at Ursa Major Solar report that after sending an initial outbound response email to customers on high-priority cases, the 'First Response' milestone countdown timer remains active on the case feed and eventually triggers a violation action. Which configuration action should the administrator perform to ensure the milestone timer stops when the response is sent?

Create an automated Flow to update the Completion Date on the Case Milestone record when the response email is sent.

Configure a Case Escalation Rule action to reset the SLA timer whenever an Email Message record is created.

Add a before-save Record-Triggered Flow on the Entitlement Process object to recalculate target business hours.

Modify the Case Record Type picklist settings to change the Milestone Status field default to 'Completed'.

Show answer & explanation

Answer: Create an automated Flow to update the Completion Date on the Case Milestone record when the response email is sent.

Answer

The administrator should create an automated Flow to update the Completion Date field on the Case Milestone record when the response email is sent.

In Salesforce Entitlement Management, milestone countdown timers continue until the Completion Date on the corresponding Case Milestone record is populated. Because outbound email activity does not automatically complete a milestone out of the box, an administrator must create automation, such as a Record-Triggered Flow, to mark the milestone as completed upon email dispatch.

Step-by-Step Solution

Identify the mechanism required to complete Case Milestones in Salesforce Service Cloud.

Recognize that sending an email or updating a case does not auto-complete a milestone without configured record automation.

Salesforce relies on the Completion Date field on the Case Milestone object being populated to stop the milestone timer.

Evaluate the appropriate automation tool to update the Case Milestone record.

Determine that a Record-Triggered Flow on Email Message or Case can find the related Case Milestone and set its Completion Date.

Flow is the standard declarative automation mechanism for executing record updates when criteria (e.g., sending an outbound email) are met.

Key Concept

Completing Case Milestones using Record Automation

Question 142Question →

A Salesforce administrator needs to select the correct utility for several distinct data operations across the organization. Match each operational data requirement on the left with the most appropriate tool or capability on the right.

Click a left item, then click its matching right item

Show answer & explanation

Answer

Matching pairs: 1) Importing 30,000 Accounts with workflow and duplicate rules matches Data Import Wizard. 2) Hard deleting 10,000 Cases bypassing Recycle Bin matches Data Loader (GUI with 'Use Bulk API' and 'Hard Delete' setting). 3) Automated nightly export of 200,000 Opportunities matches Data Loader CLI (Command Line Interface). 4) Upserting 120,000 Custom Object records via External ID matches Data Loader (GUI with Bulk API enabled).

Each requirement correctly aligns with tool limits and feature sets: Data Import Wizard is limited to 50,000 records and supports duplicate checking and workflow triggers; Data Loader supports up to 5,000,000 records, hard deletion via Bulk API, command-line automation, and export operations.

Step-by-Step Solution

Evaluate record volumes and standard feature requirements for import.

30,000 Accounts is under the 50,000 limit for Data Import Wizard, which specifically supports Accounts, duplicate checking, and workflow automation triggering.

Data Import Wizard is the best fit for browser-based imports under 50k records requiring duplicate prevention.

Evaluate hard delete requirements.

Only Data Loader supports delete and hard delete operations. Hard delete requires Bulk API enabled and special user permissions.

Data Import Wizard cannot delete records.

Evaluate automated scheduled operations and export requirements.

Data Loader CLI allows command-line parameters to be run automatically by operating system schedulers. Data Import Wizard does not support exports or automated scheduling.

Unattended automated data tasks require Data Loader CLI.

Evaluate large volume upsert requirements (>50,000 records).

120,000 records exceeds the Data Import Wizard limit of 50,000 records. Data Loader with Bulk API must be used.

Data Loader supports up to 5 million records and optimizes performance for >50k batches via Bulk API.

Key Concept

Selecting between Data Import Wizard and Data Loader based on record volume limits, operation types (import/export/delete/hard delete), duplicate detection, and automation capabilities.

Estimated Time:2m 0s

Question 143Question →

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

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with exporting target Record IDs into a CSV file, ensuring the required 'Bulk API Hard Delete' permission is assigned, enabling Bulk API settings in Data Loader for Hard Delete, and finally executing the operation while verifying the output logs.

To purge records permanently using Data Loader, an administrator must first identify and export the target Record IDs. Next, security administrative requirements must be met by ensuring the user has the 'Bulk API Hard Delete' permission. Then, Data Loader must be set up to use the Bulk API, which enables the Hard Delete option. Finally, running the process with the prepared CSV file completes the operation and allows verification via success logs.

Step-by-Step Solution

Extract Target Record IDs

A CSV file is generated containing the Record IDs of the obsolete records to be purged.

Data Loader operations require a CSV file with valid Salesforce Record IDs to target specific records for deletion.

Verify User Permissions

The user account possesses the 'Bulk API Hard Delete' system permission.

Salesforce restricts hard deletion capabilities; the Bulk API Hard Delete administrative permission must be active for the user performing the task.

Configure Data Loader for Hard Delete

Data Loader is configured to use Bulk API with Hard Delete enabled.

Hard deletion is only supported when Data Loader uses the Bulk API rather than the standard SOAP API.

Run Hard Delete and Audit Logs

The records are permanently removed from Salesforce without entering the Recycle Bin, verified via success log CSV.

Executing the operation processes the batch, and examining the success log verifies complete execution without errors.

Key Concept

Data Loader Mass Operations and Hard Delete Configuration

Estimated Time:1m 30s

Question 144Question →

A Salesforce Administrator needs to configure a data model to link a custom Sponsor__c object with a custom Event__c object. A single sponsor can support multiple events, and an event can be supported by multiple sponsors. Additionally, management needs roll-up summary fields on both Event__c and Sponsor__c to track total funding raised per event and total contributions per sponsor.

Which two actions must the administrator take to fulfill these business requirements? (Select 2 answers)

Select all that apply

Create a custom junction object containing a Master-Detail relationship field to Event__c and another Master-Detail relationship field to Sponsor__c.

Create custom Roll-Up Summary fields on both the Event__c and Sponsor__c objects that aggregate data from the custom junction object records.

Create a custom junction object containing two Lookup relationship fields pointing to Event__c and Sponsor__c, then create Roll-Up Summary fields on the parent objects.

Configure a Lookup relationship field on Event__c pointing to Sponsor__c and rely on record deletion to clear detail records without cascading.

Show answer & explanation

Answer: Create a custom junction object containing a Master-Detail relationship field to Event__c and another Master-Detail relationship field to Sponsor__c.; Create custom Roll-Up Summary fields on both the Event__c and Sponsor__c objects that aggregate data from the custom junction object records.

Answer

The administrator must create a custom junction object with two Master-Detail relationships pointing to Event__c and Sponsor__c, and then create Roll-Up Summary fields on both parent objects to aggregate values from the junction records.

To implement a many-to-many relationship in Salesforce while supporting native Roll-Up Summary fields on both related objects, an administrator must create a custom junction object with two Master-Detail relationship fields (one for each parent object). This allows both parent objects to act as masters to the junction object, enabling Roll-Up Summary fields on both Event and Sponsor records.

Step-by-Step Solution

Identify the data modeling pattern required for many-to-many relationships.

Recognize that linking two objects in a many-to-many relationship requires a custom junction object.

Direct lookup or master-detail relationships only support one-to-many patterns.

Determine the required relationship field types on the junction object to support roll-up calculations.

Choose Master-Detail relationships for both master objects on the junction object.

Roll-up summary fields are only available on the master object of a Master-Detail relationship.

Configure the Roll-Up Summary fields on both parent objects.

Roll-up fields on Event__c and Sponsor__c successfully summarize values stored on the detail junction records.

Parent objects in Master-Detail relationships inherit roll-up capabilities from their child records.

Key Concept

Many-to-Many Relationships and Roll-Up Summary Field Requirements

Question 145Question →

A Salesforce administrator at a subscription management company needs to import $42{}000$ custom $Subscription\_\_c$ records. The operation requires preventing duplicate records during import by matching on an External ID field, opting out of triggering active Workflow Rules during record creation, and executing the job via a browser-based UI without downloading desktop software. Which administration tool meets all of these requirements?

Data Import Wizard, because it supports up to

50{}000

records, operates in a browser, allows workflow rule suppression, and matches on External ID for custom objects.

Data Loader, because Data Import Wizard cannot match records based on External ID fields during an upsert or insert operation.

Data Loader, because Data Import Wizard is limited to a maximum volume of

10{}000

records per import batch for custom objects.

Data Import Wizard, but workflow rules will automatically trigger because workflow suppression is only supported when using Data Loader.

Show answer & explanation

Answer: Data Import Wizard, because it supports up to $50{}000$ records, operates in a browser, allows workflow rule suppression, and matches on External ID for custom objects.

Answer

Data Import Wizard, because it supports up to

50{}000

records, operates in a browser, allows workflow rule suppression, and matches on External ID for custom objects.

The correct answer identifies the Data Import Wizard as the appropriate tool because the record volume (

42{}000

) is under the

50{}000

wizard limit, it runs entirely within the web browser without installing desktop software, it supports deduplication using External IDs for custom objects, and it provides a setting to suppress workflow rules during data creation.

Step-by-Step Solution

Evaluate record volume requirement

The target volume is

42{}000

records, which is under the

50{}000

record limit of the Data Import Wizard.

Data Import Wizard handles up to

50{}000

records, whereas Data Loader handles up to

5{}000{}000

records.

Evaluate application architecture and user interface constraint

The requirement specifies using a browser-based UI without installing desktop applications.

Data Import Wizard is natively built into the Salesforce web application setup, while Data Loader requires a client desktop application download.

Evaluate workflow suppression and duplicate matching criteria

Data Import Wizard allows matching custom object records by External ID and explicitly provides a checkbox to suppress workflow rules and processes.

Data Loader automatically fires active workflows and processes without an native option to suppress them in the client interface.

Key Concept

Data Import Wizard vs Data Loader Capabilities and Tool Selection

Question 146Question →

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

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct execution order is: 1) System and custom Validation Rules, 2) Case Assignment Rules, 3) Case Auto-Response Rules, and 4) Case Escalation Rules.

Upon case creation, Salesforce executes automation in a predefined sequence: Validation Rules verify data integrity, Case Assignment Rules route ownership, Case Auto-Response Rules dispatch customer communications, and Case Escalation Rules set SLA escalation targets.

Step-by-Step Solution

Identify the data entry validation phase.

Validation Rules run first to confirm record data integrity before processing.

Salesforce validates all field inputs before running downstream record routing or automation.

Identify record routing and ownership assignment.

Case Assignment Rules evaluate next to determine owner assignment (User or Queue).

Ownership must be established prior to sending confirmation notifications or setting SLA timers.

Identify customer communication automation.

Case Auto-Response Rules evaluate third to send the customer an automated email.

Auto-response templates depend on case attributes and owner information established in prior steps.

Identify SLA timer and escalation configuration.

Case Escalation Rules evaluate fourth to establish escalation actions and timers.

Escalation logic relies on the finalized case owner, status, and business hours settings.

Key Concept

Salesforce Case Automation Order of Execution

Question 147Question →

An administrator configures a new Record Type named 'Renewals' on the Contract object and assigns the 'Renewal Layout' page layout to the Customer Support Profile for this record type. After deployment, users assigned to the Customer Support Profile report that while the layout section structure is correct, the 'Contract Status' picklist field still displays legacy options like 'Draft' and 'In Approval' rather than the required 'Renewal Pending' and 'Renewed' values.

Which configuration step should the administrator perform to resolve this issue?

Edit the picklist values available for the 'Contract Status' field directly within the 'Renewals' Record Type detail page.

Create a permission set that explicitly grants field-level picklist access for 'Renewal Pending' and 'Renewed' to the Customer Support Profile.

Configure Dynamic Forms component visibility rules on the Lightning Record Page to display the missing picklist values.

Add the new picklist values directly to the 'Renewal Layout' page layout field properties panel.

Show answer & explanation

Answer: Edit the picklist values available for the 'Contract Status' field directly within the 'Renewals' Record Type detail page.

Answer

Edit the picklist values available for the 'Contract Status' field directly within the 'Renewals' Record Type detail page.

When a new Record Type is created, available picklist values must be configured for each picklist field on the Record Type detail page. Assigning a page layout only updates the visual arrangement of fields, not the available picklist values.

Step-by-Step Solution

Navigate to Object Manager and select the Contract object.

Accesses the object configuration settings.

Record Type picklist assignments are configured at the object level.

Select Record Types, click on 'Renewals', and locate 'Picklists Available for Editing'.

Displays all editable picklists for the 'Renewals' Record Type.

Creating a record type inherits master picklist values until explicitly configured.

Edit the 'Contract Status' picklist to remove legacy values and move 'Renewal Pending' and 'Renewed' to Selected Values.

Ensures only the desired picklist values are displayed when creating or editing records of this record type.

Picklist value availability per record type must be explicitly assigned within the record type settings.

Key Concept

Record Type Picklist Value Assignment

Question 148Question →

A Salesforce administrator is implementing data quality controls across various objects in an organization. Match each business requirement with the correct validation rule formula expression designed to enforce that data quality requirement.

Click a left item, then click its matching right item

Show answer & explanation

Answer

Matching pairings: Preventing modifications to Discount Percentage after Closed Won matches AND(ISPICKVAL(PRIORVALUE(StageName), 'Closed Won'), ISCHANGED(Discount_Percentage__c)); Validating Tax ID format matches AND(NOT(ISBLANK(Tax_ID__c)), NOT(REGEX(Tax_ID__c, '[A-Z]{2}[0-9]{6}'))); Requiring Phone for Hot Leads matches AND(ISPICKVAL(Rating, 'Hot'), ISBLANK(Phone)); Enforcing Target Completion Date after CreatedDate matches Target_Completion_Date__c < DATEVALUE(CreatedDate).

Each validation formula expression correctly models the specific business requirement using Salesforce formula functions: PRIORVALUE and ISCHANGED monitor field edits relative to previous values; REGEX combined with NOT(ISBLANK) validates pattern compliance; ISPICKVAL combined with ISBLANK enforces mandatory inputs; and DATEVALUE normalizes DateTime fields for comparison.

Step-by-Step Solution

Analyze requirement 1 (preventing changes after stage completion)

Identified that PRIORVALUE(StageName) checks historical state before edit, and ISCHANGED(Discount_Percentage__c) detects field edits.

Validation rules evaluate to TRUE to block saving; checking PRIORVALUE ensures past stage state is evaluated.

Analyze requirement 2 (pattern matching on populated text fields)

Identified REGEX for format matching and NOT(ISBLANK()) to skip blank entries.

Regular expressions allow precise pattern criteria matching such as two uppercase letters followed by six numbers.

Analyze requirement 3 (conditionally required fields based on picklist value)

Identified ISPICKVAL for picklist evaluation combined with ISBLANK for detecting null/missing phone values.

Validation rules trigger when formula condition evaluates to TRUE, meaning Rating is 'Hot' AND Phone is blank.

Analyze requirement 4 (date field comparison against system creation date)

Identified DATEVALUE function to convert CreatedDate (DateTime) to Date for direct comparison with Target_Completion_Date__c.

Date and DateTime fields cannot be compared directly without type conversion using DATEVALUE.

Key Concept

Salesforce Validation Rule Formula Functions and Data Quality Enforcement

Question 149Question →

An administrator at Zenith Financial Partners enables 'Allow Users to Relate Multiple Contacts to Tasks and Events' (Shared Activities) in Activity Settings so that advisors can log joint client meetings. Which statement accurately describes the system capabilities and relationship limits when logging a single event record?

The event can be related to up to 50 contacts in the Name field, but can only be related to 1 non-contact record in the Related To field.

The event can be related to up to 50 different Account records simultaneously in the Related To field, provided the accounts belong to the same parent hierarchy.

The system automatically creates 50 distinct event record copies, assigning one standalone copy to each associated contact.

The event can be related to an unlimited number of contacts, but the Related To field becomes disabled once more than one contact is added.

Show answer & explanation

Answer: The event can be related to up to 50 contacts in the Name field, but can only be related to 1 non-contact record in the Related To field.

Answer

The event can be related to up to 50 contacts in the Name field, but can only be related to 1 non-contact record in the Related To field.

When 'Allow Users to Relate Multiple Contacts to Tasks and Events' (Shared Activities) is enabled, Salesforce permits associating up to 50 contacts or leads to a single task or event through the Name field (WhoId), with one marked as the primary contact. The Related To field (WhatId) continues to support association with only one non-contact record, such as an Account, Opportunity, or Case.

Step-by-Step Solution

Identify the feature being referenced in Activity Settings.

The feature is Shared Activities ('Allow Users to Relate Multiple Contacts to Tasks and Events').

Understanding the specific feature scope is required to evaluate system limits.

Evaluate relationship field parameters (WhoId vs. WhatId limits).

WhoId (Name field) supports up to 50 Contacts or Leads with one designated primary Contact. WhatId (Related To field) supports exactly 1 record (e.g., Account, Opportunity, Case).

Salesforce architecture allows multi-entity association only for person objects (Contacts/Leads) on tasks and events, while maintaining a single relationship to business objects.

Key Concept

Shared Activities Limits (WhoId vs WhatId)

Question 150Question →

An administrator needs to automatically update the custom field 'Contract_Status__c' on a custom object record 'Vendor_Contract__c' when it is created, prior to the record being saved to the database. Which flow trigger option should the administrator choose for optimal execution performance?

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

A Record-Triggered Flow configured for Actions and Related Records (After-Save)

A Schedule-Triggered Flow scheduled to run every night

A Platform Event-Triggered Flow triggered upon contract creation

Show answer & explanation

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

Answer

A Record-Triggered Flow configured for Fast Field Updates (Before-Save) is the correct choice because it updates fields on the triggering record before database commit without triggering additional DML operations.

Fast Field Updates (Before-Save) run directly before the record is saved to the database, making them significantly faster and highly efficient for updating fields on the record that launched the flow.

Step-by-Step Solution

Analyze the business requirement

The requirement is to update a field on the triggering record ('Vendor_Contract__c') at the time of creation before it is saved to the database.

Understanding whether the update targets the same record or related records determines the trigger timing.

Evaluate flow trigger types

Fast Field Updates (Before-Save) run immediately before record insertion/update and allow modifying the triggering record directly without triggering extra database write cycles.

Salesforce optimal design principles specify Before-Save record-triggered flows for same-record updates.

Key Concept

Selecting optimal Record-Triggered Flow execution timing (Before-Save vs After-Save)

Question 151Question →

An administrator is optimizing system performance for high-volume creation of custom Equipment Maintenance records. Analysis reveals that when an Equipment Maintenance record is inserted, an existing automation updates the 'Next Service Date' and 'Maintenance Status' fields on that same triggering record. Currently, this process uses an after-save Record-Triggered Flow with an explicit Update Records element. Which modification should the administrator make to optimize execution time and minimize database DML operations?

Reconfigure the Record-Triggered Flow to run Fast Field Updates (before-save) and remove the explicit Update Records element.

Keep the Record-Triggered Flow configured for Actions and Related Records (after-save) but set the explicit Update Records element to execute asynchronously.

Replace the automation with a Schedule-Triggered Flow that queries newly inserted Equipment Maintenance records hourly and updates them in a loop.

Convert the logic into a Record-Triggered Flow running after-save with system validation rules enabled to handle same-record field assignment.

Show answer & explanation

Answer: Reconfigure the Record-Triggered Flow to run Fast Field Updates (before-save) and remove the explicit Update Records element.

Answer

Reconfigure the Record-Triggered Flow to run Fast Field Updates (before-save) and remove the explicit Update Records element.

Configuring the Record-Triggered Flow to execute Fast Field Updates (before-save) applies updates directly to the `$Record` global variable before the record is saved to the database. Salesforce automatically commits these values during the save operation, eliminating the need for an explicit Update Records element and significantly reducing execution time and governor limit consumption.

Step-by-Step Solution

Analyze the automation requirement

The requirement is to update fields on the triggering record itself during creation.

Determining whether updates target the triggering record versus related records dictates optimal flow trigger type.

Evaluate Salesforce Order of Execution and flow optimization guidelines

Fast Field Update (before-save) record-triggered flows execute up to 10 times faster than after-save flows because changes are applied directly to the $Record variable prior to database commit.

Before-save flows do not require an explicit Update Records element or additional DML statements.

Select the optimal flow trigger design

Configuring the flow for Fast Field Updates (before-save) and removing the explicit Update Records element fulfills all performance and functional requirements.

It eliminates additional DML calls, saves system resources, and avoids unnecessary re-evaluation of save order elements.

Key Concept

Record-Triggered Flow Optimization (Fast Field Updates vs. Actions and Related Records)

Question 152Question →

An administrator at Astra BioTech is optimizing the Lightning Sales Console to improve sales representative workflow efficiency. The sales management team wants a solution that allows reps to automate repetitive multi-step record actions—such as updating record statuses and logging call details in one click—while also providing persistent access to tools like Notes and History from anywhere within the console app.

Which two tools or features should the administrator configure to meet these business requirements? (Select 2 options)

Select all that apply

Macros configured within the Lightning Sales Console app layout

Utility Bar items added to the Lightning Console App configuration

Sales Process mapping to link Lead status values directly to Opportunity stages without lead conversion

Custom Lead Field Mapping applied directly within the Standard Price Book entries

Show answer & explanation

Answer: Macros configured within the Lightning Sales Console app layout; Utility Bar items added to the Lightning Console App configuration

Answer

The administrator should implement Macros within the Lightning Sales Console app layout and add Utility Bar items to the Lightning Console App configuration.

Configuring Macros automates multi-step repetitive record actions such as field updates and activity logging within the console. Adding components like Notes and History to the Utility Bar provides persistent, universal access across all console workspace tabs.

Step-by-Step Solution

Identify the requirement for automating repetitive multi-step tasks

Recognize that Macros in Lightning Sales Console enable single-click execution of repetitive tasks like field updates and logging calls.

Macros directly address the requirement for streamlining repetitive workflow actions.

Identify the requirement for persistent access to productivity components

Select the Utility Bar in the Lightning App Builder / App Manager settings for the console app.

The Utility Bar remains fixed at the bottom of the screen, allowing instant access to tools like Notes and History regardless of the page open.

Key Concept

Sales Console Productivity Enhancements (Macros and Utility Bar)

Question 153Question →

A customer support manager wants to view a report of open cases grouped by Case Reason along the rows and by Priority along the columns to analyze case volume in a grid layout. Which report format should the Salesforce administrator select to fulfill this requirement?

Matrix

Summary

Tabular

Joined

Show answer & explanation

Answer: Matrix

Answer

Matrix

The Matrix report format is specifically designed to group records by both rows and columns simultaneously, creating a two-dimensional grid ideal for summarizing metrics like case counts across two categorical fields.

Step-by-Step Solution

Identify the reporting requirements

The requirement specifies grouping data across two dimensions: rows (Case Reason) and columns (Priority).

Understanding group structure dictates the necessary Salesforce report format.

Evaluate Salesforce report formats

Matrix format supports simultaneous row and column groupings to form a grid view.

Tabular has no groupings, Summary only groups by rows, and Joined combines separate report blocks.

Key Concept

Selecting appropriate Salesforce report formats (Tabular, Summary, Matrix, Joined) based on grouping requirements.

Question 154Question →

An administrator needs to ensure that whenever an Opportunity stage is set to 'Closed Won', the custom field 'Payment_Method__c' must not be left blank. Which validation rule formula correctly enforces this requirement?

AND(ISPICKVAL(StageName, "Closed Won"), ISBLANK(Payment_Method__c))

AND(ISPICKVAL(StageName, "Closed Won"), Payment_Method__c = "")

OR(ISPICKVAL(StageName, "Closed Won"), ISBLANK(Payment_Method__c))

AND(NOT(ISPICKVAL(StageName, "Closed Won")), ISBLANK(Payment_Method__c))

Show answer & explanation

Answer: AND(ISPICKVAL(StageName, "Closed Won"), ISBLANK(Payment_Method__c))

Answer

The validation rule formula using AND(ISPICKVAL(StageName, "Closed Won"), ISBLANK(Payment_Method__c)) correctly enforces the data quality requirement.

Validation rules prevent saving a record when the formula returns TRUE. Combining ISPICKVAL(StageName, 'Closed Won') with ISBLANK(Payment_Method__c) inside an AND() function ensures that if the Opportunity is marked as 'Closed Won' and the payment method is missing, the validation rule triggers and displays the error message.

Step-by-Step Solution

Identify the required logic conditions for triggering the validation error

The validation rule must evaluate to TRUE when StageName is 'Closed Won' AND Payment_Method__c is blank.

Salesforce validation rules display an error message when the formula expression returns true.

Select the proper functions for picklist evaluation and null checking

Use ISPICKVAL() to evaluate picklist fields like StageName and ISBLANK() to evaluate whether Payment_Method__c contains a value.

Direct text comparison operators are restricted on picklists, and ISBLANK() is the standard function for checking null/blank values.

Combine conditions using the logical AND operator

AND(ISPICKVAL(StageName, "Closed Won"), ISBLANK(Payment_Method__c))

Both conditions must simultaneously be met to trigger the validation error.

Key Concept

Validation Rule Logic and Null Checking with ISBLANK

Question 155Question →

A Salesforce Administrator is configuring a Custom Report Type to analyze Customer Service operations. Management needs to report on all Cases, including those without any associated Work Orders, while also displaying detailed technician fields from the related Service Resource lookup object on the Work Order. Which two configuration steps must the administrator execute within the Custom Report Type layout and object relationship setup to satisfy these requirements? (Select TWO)

Select all that apply

Define the relationship between Case (Primary Object) and Work Order (Secondary Object) using the 'Each record "A" may or may not have related "B" records' option.

Use the 'Add fields related via lookup' feature on the Custom Report Type field layout to include fields from the Service Resource object.

Set the default report layout format to 'Matrix' directly within the Custom Report Type general settings tab.

Create a Roll-Up Summary field on the Case object to count Work Orders so unlinked records can be categorized using a row-level formula.

Configure the running user setting on the Custom Report Type to bypass Organization-Wide Defaults for non-work-order Cases.

Show answer & explanation

Answer: Define the relationship between Case (Primary Object) and Work Order (Secondary Object) using the 'Each record "A" may or may not have related "B" records' option.; Use the 'Add fields related via lookup' feature on the Custom Report Type field layout to include fields from the Service Resource object.

Answer

To satisfy the reporting requirements, the administrator must configure the object relationship as 'Each record "A" may or may not have related "B" records' and utilize the 'Add fields related via lookup' feature in the Custom Report Type layout editor.

The correct requirements are met by establishing a left outer join ('with or without' relationship) between Case and Work Order so that Cases lacking related Work Orders remain in the report. Additionally, using 'Add fields related via lookup' in the Custom Report Type field layout enables access to fields on referenced lookup objects (up to four levels away, such as Service Resource) without modifying the core object hierarchy of the report type.

Step-by-Step Solution

Determine the join requirement between Case and Work Order.

Identified that an outer join is required so that Cases without Work Orders are retained in the report output.

Choosing 'Each record A must have at least one related B record' would perform an inner join, filtering out Cases that do not have Work Orders.

Configure object relationship in Custom Report Type setup.

Set relationship to 'Each record "A" may or may not have related "B" records'.

This enforces the required left outer join structure at the report type level.

Identify how to bring fields from the indirect lookup object (Service Resource) into the field layout.

Navigated to the Field Layout editor of the Custom Report Type and selected 'Add fields related via lookup'.

This avoids creating unnecessary object relationship tiers while exposing indirect lookup fields to end users in the report builder.

Key Concept

Custom Report Type Object Relationships and Layout Field Customization

Question 156Question →

Horizon Fleet Services uses a Private Organization-Wide Default (OWD) sharing model for Cases. The Director of Customer Service requests a dashboard that allows regional service managers to view real-time case metrics. However, each manager must only see case records that they own or have explicit sharing access to. Currently, when regional managers open the dashboard, they are seeing aggregated company-wide metrics across all regions. Which two configurations should the Salesforce administrator perform to resolve this issue? (Select 2 options)

Select all that apply

Configure the dashboard running user setting to 'Run as the viewing user'.

Grant 'View' access on the dashboard folder to the regional service managers.

Change the Organization-Wide Defaults for the Case object from Private to Public Read-Only.

Assign the 'View All Data' permission to the regional service manager profiles.

Add a custom filter on the underlying source report specifying 'Run as Logged-In User'.

Show answer & explanation

Answer: Configure the dashboard running user setting to 'Run as the viewing user'.; Grant 'View' access on the dashboard folder to the regional service managers.

Answer

To ensure that regional managers only see metrics for cases they have permissions to view, the administrator must configure the dashboard running user setting to 'Run as the viewing user' (making it a dynamic dashboard) and ensure the regional managers have 'View' access to the dashboard folder.

Configuring the dashboard to 'Run as the viewing user' (a dynamic dashboard) ensures that data displayed in dashboard components is calculated using the security context and record access of whoever is logged in and viewing the dashboard. Additionally, sharing the dashboard folder with 'View' permissions enables those users to locate and run the dashboard while respecting their individual record-level access control.

Step-by-Step Solution

Identify the root cause of the unauthorized data exposure on the dashboard.

The dashboard was configured with a static running user (such as an executive or administrator with broad data access), which causes components to display data according to that static user's security permissions.

Static running users evaluate component security for all viewers based on the running user's OWD and sharing permissions.

Update the dashboard security settings to enforce dynamic user access.

Configuring the dashboard running user property to 'Run as the viewing user' ensures that metrics are calculated dynamically according to each individual logged-in user's record visibility.

Dynamic dashboards honor the viewing user's Organization-Wide Defaults, role hierarchy, and sharing rules.

Verify dashboard folder sharing permissions.

Granting 'View' access on the shared dashboard folder ensures that the intended regional service managers can access and render the dynamic dashboard.

Folder access governs who can access the dashboard file itself, independent of the record-level security within the underlying data.

Key Concept

Dynamic Dashboard Security and Running User Configuration

Estimated Time:1m 30s

Question 157Question →

A Salesforce administrator needs to implement automation solutions that run completely in the background without user interaction whenever a record is created or updated. Which two declarative automation tools should the administrator consider for this requirement?

Select all that apply

Record-Triggered Flow

Autolaunched Flow (No Trigger)

Screen Flow

Approval Processes Initial Submission Action

Show answer & explanation

Answer: Record-Triggered Flow; Autolaunched Flow (No Trigger)

Answer

The administrator should select Record-Triggered Flow and Autolaunched Flow (No Trigger).

Record-Triggered Flows automatically run in the background when records are created or updated. Autolaunched Flows also execute without a user interface and run headlessly when invoked by automated triggers.

Step-by-Step Solution

Analyze the automation requirements.

The requirement specifies non-interactive background execution on record changes.

Determining user interaction and trigger type is essential for automation tool selection.

Evaluate candidate tools against constraints.

Record-Triggered Flows and Autolaunched Flows operate headlessly in the background, whereas Screen Flows require UI interaction.

Choosing headless flow types ensures the process executes silently without interrupting the user experience.

Key Concept

Selecting declarative automation tools based on trigger mechanism and user interface requirements.

Question 158Question →

A Salesforce Administrator is configuring an operations dashboard to track key metrics across several departments. The Operations Director asks the administrator to add interactive filters so users can dynamically refine the dashboard by Region, Industry, Rating, and Account Type. When attempting to add the fourth filter criterion, the system prevents the administrator from adding it. Which limit constraint explains why the administrator cannot add the fourth filter?

A Salesforce dashboard can have a maximum of 3 dashboard filters configured at one time.

Dashboard filters can only be created if the running user has system administrator profile permissions.

The source reports used in the dashboard components must originate from a single custom report type to support more than 2 filters.

Dashboard filters override individual record-level security and are restricted when viewing data as a dynamic running user.

Show answer & explanation

Answer: A Salesforce dashboard can have a maximum of 3 dashboard filters configured at one time.

Answer

A Salesforce dashboard allows a maximum of 3 dashboard filters to be added per dashboard.

In Salesforce, each dashboard can support up to a maximum of 3 dashboard filters. When an administrator reaches this limit, additional filter fields cannot be added regardless of object types or permissions.

Step-by-Step Solution

Identify the requested configuration requirement

The user requested adding 4 distinct interactive filters (Region, Industry, Rating, and Account Type) to a single dashboard.

Understanding what the administrator is attempting to configure helps pinpoint which governor limit applies.

Evaluate standard Salesforce Lightning dashboard limits

Salesforce enforces a maximum limit of 3 dashboard filters per dashboard (with each filter allowing up to 50 filter options).

Determining standard platform capabilities confirms why the fourth filter cannot be added.

Key Concept

Dashboard Dynamic Filter Limits

Question 159Question →

A support director needs a unified view that presents all Account records in Salesforce alongside their associated Support Cases, ensuring that Accounts remain visible even if they have zero related Cases. In addition, the report must display key metrics from related Work Orders in a side-by-side structure grouped by Account Name. Which combination of Custom Report Type configuration and report format selection satisfies these requirements?

Create a Custom Report Type with Accounts as the primary object and Cases as the secondary object using 'Each A record may or may not have related B records' (outer join), then build a Joined Report that pairs this report type block with an Accounts with Work Orders report type block.

Create a Custom Report Type with Accounts as the primary object and Cases as the secondary object using 'Each A record must have at least one related B record' (inner join), and configure a Summary Report grouped by Account Name and Work Order Status.

Use a standard Cases report type, write a summary formula to evaluate record-by-record Work Order values, and apply a Matrix Report format grouped by Account Name on rows and Case Priority on columns.

Create a standard Accounts with Cases report type, configure a dynamic dashboard running user security setting to expose hidden records, and select a tabular report format with cross-object formula fields.

Show answer & explanation

Answer: Create a Custom Report Type with Accounts as the primary object and Cases as the secondary object using 'Each A record may or may not have related B records' (outer join), then build a Joined Report that pairs this report type block with an Accounts with Work Orders report type block.

Answer

Create a Custom Report Type using an outer join ('Each A record may or may not have related B records') between Accounts and Cases, and build a Joined Report format to place the Accounts with Cases block alongside an Accounts with Work Orders block grouped by Account Name.

The correct choice configures a Custom Report Type with an outer join ('Each A record may or may not have related B records'), ensuring Accounts without associated Cases are retained in the report results. Additionally, choosing a Joined Report format enables the administrator to combine two separate report type blocks (Accounts with Cases and Accounts with Work Orders) side-by-side, grouped by the shared Account Name field.

Step-by-Step Solution

Determine the required object relationship logic for Accounts and Cases.

Configuring the Custom Report Type relationship as 'Each A record may or may not have related B records' ensures Accounts without Cases appear in report results.

Standard report types use inner joins ('with' relationship), which automatically exclude parent records that lack child records.

Determine the correct report format for multi-object side-by-side analysis.

Selecting the Joined Report format allows the report to contain up to 5 distinct report blocks based on different report types.

Neither Summary nor Matrix report formats can display metrics from separate unrelated child relationships (Cases vs. Work Orders) in parallel blocks.

Apply the common grouping field across report blocks.

Group both blocks by the common field 'Account Name'.

Joined reports require a shared principal grouping field across blocks to align data side-by-side.

Key Concept

Custom Report Type Object Relationships and Joined Report Format Selection

Question 160Question →

A Salesforce administrator at Cloud Scale Logistics is setting up activity tracking for account management teams. The teams host joint quarterly business reviews involving multiple client stakeholders from different divisions, and multiple internal representatives are assigned action items following each meeting.

When configuring Tasks, Events, and Shared Activities, which two considerations and system behaviors must the administrator keep in mind? (Choose 2)

Select all that apply

Enabling Shared Activities allows users to relate a single Task or Event to up to 50 Contacts via the Name field, while still relating it to a single primary record via the Related To field.

Enabling Shared Activities allows users to relate a single Task directly to up to 50 distinct Account records simultaneously using the Related To field.

Assigning a single Task to multiple users creates individual, independent copies of the Task for each assigned user rather than a single shared record.

Assigning a Task to multiple users creates a single master Task record that automatically updates and closes for all assigned users as soon as one user completes it.

Show answer & explanation

Answer: Enabling Shared Activities allows users to relate a single Task or Event to up to 50 Contacts via the Name field, while still relating it to a single primary record via the Related To field.; Assigning a single Task to multiple users creates individual, independent copies of the Task for each assigned user rather than a single shared record.

Answer

The administrator must remember that Shared Activities permits relating up to 50 Contacts to a single Task or Event while maintaining a single parent Account link, and that assigning a Task to multiple users generates individual, independent task copies for each user.

Enabling Shared Activities allows users to relate up to 50 Contacts (or Leads) to a single Task or Event via the Name field, while keeping a single parent record link in the Related To field. Additionally, assigning a task to multiple users creates separate, independent copies of the task for each user.

Step-by-Step Solution

Analyze Shared Activities capabilities and limits regarding object relationships.

Confirm that Shared Activities expands the Name (WhoId) lookup to up to 50 Contacts or Leads, but leaves the Related To (WhatId) lookup limited to a single record (e.g., one Account).

Salesforce Activity architecture enforces a 1-to-1 relationship between an Activity and its WhatId parent record.

Analyze multi-user task assignment behavior.

Confirm that assigning a task to multiple individual assignees or groups creates distinct task records for each assignee.

Independent copies allow each team member to manage and complete their own work item separately.

Key Concept

Shared Activities limits (up to 50 Contacts via WhoId) and independent Task creation behavior for multi-user assignments

Estimated Time:2m 0s

PreviousPage 8 / 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