All practice questions

1784 questions

Question 121Question

A Salesforce Administrator is designing a custom data model to track software releases using a custom object named Software_Release__c and individual deployment tasks using a custom object named Deployment_Task__c. The business requirement states that deleting a Software_Release__c record must automatically delete all associated Deployment_Task__c records. Additionally, management requires a real-time aggregate calculation of total deployment hours directly on the Software_Release__c record. Which relationship configuration should the administrator implement on the Deployment_Task__c object to meet these requirements?

Show answer & explanation

Answer: Create a Master-Detail relationship field on Deployment_Task__c referencing Software_Release__c.

Answer

Create a Master-Detail relationship field on the Deployment_Task__c object referencing the Software_Release__c object.
Establishing a Master-Detail relationship on the child custom object (Deployment_Task__c) that references the parent (Software_Release__c) satisfies both business criteria. It automatically cascades deletions from master to detail records and unlocks the ability to build declarative Roll-Up Summary fields on the master object to sum total deployment hours.

Step-by-Step Solution

1
Analyze deletion requirements
Master-Detail relationships natively enforce cascading deletion, ensuring child Deployment_Task__c records are removed when the parent Software_Release__c record is deleted.
Lookup relationships retain child records by default when a parent record is deleted unless specific Apex or custom logic is implemented.
2
Analyze aggregation requirements
Roll-Up Summary fields can be created on the master object (Software_Release__c) to calculate sums, counts, or min/max values of fields on the detail records.
Declarative Roll-Up Summary fields are exclusively available on the master side of a Master-Detail relationship.

Key Concept

Master-Detail Relationship Capabilities and Roll-Up Summaries
Question 122Question

A Salesforce administrator is building an executive summary dashboard for customer support leadership. When attempting to add a donut chart component to display case volume categorized by origin, the administrator finds that chart visual types are disabled in the dashboard builder. What configuration detail in the underlying report is causing chart components to be unavailable?

Show answer & explanation

Answer: The source report is formatted as a tabular report and lacks at least one row or column grouping.

Answer

The source report is formatted as a tabular report and lacks at least one row or column grouping.
In Salesforce, chart components (such as donut, pie, bar, line, and column charts) require aggregated data. A source report must be grouped by at least one row or column (Summary, Matrix, or Joined report format) for chart components to be enabled in the dashboard builder. A plain tabular report can only be displayed using table components.

Step-by-Step Solution

1
Identify the requirement for adding visual charts (such as donut, bar, or line charts) to a Salesforce dashboard.
Visual chart components plot grouped data categories along axes or segments.
Charts rely on grouped summary data to aggregate metric values across categories.
2
Evaluate why chart options are disabled when configuring the dashboard component.
Tabular reports contain only un-grouped record rows and columns, making it impossible for chart components to summarize metric data.
Adding a group by field (converting the report to a Summary or Matrix format) is required to unlock chart component options.

Key Concept

Dashboard Component Source Report Grouping Requirements
Question 123Question

A Salesforce administrator at a healthcare company needs to import 12,000 new Lead records gathered from a recent medical conference. The administrative requirements specify that the import process must automatically execute active Lead assignment rules and prevent creating duplicate records based on email address matching. Which data tool should the administrator select to fulfill this requirement?

Show answer & explanation

Answer: Data Import Wizard, because it supports Lead imports under 50,000 records and natively provides options to trigger lead assignment rules and detect duplicates.

Answer

Data Import Wizard, because it supports Lead imports under 50,000 records and natively provides options to trigger lead assignment rules and detect duplicates.
The Data Import Wizard is the optimal utility because the dataset size (12,000 records) is well within its 50,000 record capacity limit, the target object (Leads) is supported by the wizard, and it natively includes functionality to run lead assignment rules and match existing records to prevent duplicates during import.

Step-by-Step Solution

1
Evaluate record volume requirement
12,000 records is below the 50,000 record threshold for Data Import Wizard.
Data Import Wizard supports up to 50,000 records per operation, whereas Data Loader supports up to 5,000,000 records.
2
Evaluate target object support
Leads are supported by Data Import Wizard.
Data Import Wizard supports Accounts, Contacts, Leads, Solutions, Campaign Members, Person Accounts, and all Custom Objects.
3
Evaluate operational feature requirements (assignment rules and duplicate matching)
Data Import Wizard natively provides checkboxes to trigger Lead assignment rules and match duplicates by fields such as Email.
Data Loader does not offer built-in duplicate matching UI or lead assignment rule triggers during normal wizard operations.

Key Concept

Selecting between Data Import Wizard and Data Loader based on record volume, object support, assignment rule execution, and native duplicate prevention.
Question 124Question

A Salesforce Administrator is configuring Salesforce Knowledge access controls and article publishing settings for a global support team. Match each Salesforce Knowledge administration component on the left to its correct function or configuration requirement on the right.

Click a left item, then click its matching right item

Items

Knowledge User Feature License
Data Category Group Visibility
Article Action Permissions
Public Knowledge Channel Setting

Matches

Show answer & explanation

Answer

Knowledge User Feature License matches with enabling the checkbox on User records; Data Category Group Visibility matches with controlling access to classification hierarchies via Profiles, Permission Sets, or Roles; Article Action Permissions match with granting granular publishing lifecycle privileges; Public Knowledge Channel Setting matches with dictating article visibility for unauthenticated guest users.
Each Knowledge component serves a distinct administrative purpose: Feature Licenses unlock authoring tools on user records, Data Category Visibility controls taxonomic article access via profiles/permission sets/roles, Article Action Permissions grant granular lifecycle operations (Publish/Archive), and Channel Settings govern external audience exposure.

Step-by-Step Solution

1
Identify user licensing requirements for Salesforce Knowledge authoring
Determine that authoring access requires the Knowledge User feature license checkbox enabled on the user record.
Object permissions alone do not grant article authoring capabilities without the feature license.
2
Evaluate classification security and visibility mechanisms
Associate Data Category Group Visibility with profile, permission set, or role configuration.
Data category visibility controls access to article classification trees independently of standard object permissions.
3
Differentiate between publication workflow permissions and distribution channels
Map Article Actions to publishing workflow privileges and Public Knowledge channels to guest user access.
Article Actions manage the internal content lifecycle while Channels manage target distribution endpoints.

Key Concept

Salesforce Knowledge Provisioning, Security, and Publication Channels
Question 125Question

A Salesforce Administrator at an enterprise software company is evaluating data administration tools for several bulk data operations. Which two statements accurately describe the capabilities or limitations of the Data Import Wizard and Data Loader? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Data Loader must be selected to hard delete 12,000 custom object records to permanently purge them from the org without sending them to the Recycle Bin.; Data Loader must be used instead of the Data Import Wizard when importing 25,000 Opportunity records because the Data Import Wizard does not support importing Opportunities.

Answer

The correct statements are that Data Loader must be selected to hard delete custom object records permanently without moving them to the Recycle Bin, and Data Loader must be used when importing Opportunity records because the Data Import Wizard does not support the Opportunity object.
Data Loader is required for hard deleting records (which permanently purges them without sending them to the Recycle Bin) as well as importing Opportunity records, since the Data Import Wizard does not support the Opportunity object or deletion operations.

Step-by-Step Solution

1
Evaluate object support for the Data Import Wizard
The Data Import Wizard supports Accounts, Contacts, Leads, Solutions, Campaign Members, Person Accounts, and custom objects. It does not support Opportunities.
Opportunity records must be imported using Data Loader regardless of batch size.
2
Evaluate record volume limits for both tools
The Data Import Wizard caps imports at 50,000 records per session, while Data Loader can handle up to 5,000,000 records.
Importing 75,000 records exceeds the Data Import Wizard threshold and requires Data Loader.
3
Analyze operation types supported by each tool
Data Import Wizard only supports insert, update, and upsert operations. Data Loader supports insert, update, upsert, delete, hard delete, export, and export all.
Hard deletion (bypassing the Recycle Bin) and exporting data are capabilities exclusive to Data Loader.

Key Concept

Data Import Wizard vs Data Loader Capabilities and Selection Criteria
Question 126Question

A Sales Operations Manager requires a report that lists all Account records in Salesforce, including Accounts that do not have any associated Opportunities. The report must summarize the total Opportunity Amount across two dimensions simultaneously: Account Industry along the rows and Opportunity Stage across the columns. Furthermore, the administrator must ensure that any custom fields created on Accounts or Opportunities in the future are automatically available in the report builder without requiring manual updates to the report type field layout. Which solution should the Salesforce administrator implement to satisfy all requirements?

Show answer & explanation

Answer: Enable the organizational setting to automatically add new custom fields to custom report types, build a Custom Report Type with Accounts as the primary object and Opportunities defined with 'A records may or may not have related B records', and construct the report using the Matrix format.

Answer

Enable the organizational setting to automatically add new custom fields to custom report types, build a Custom Report Type with Accounts as the primary object and Opportunities defined with 'A records may or may not have related B records', and construct the report using the Matrix format.
To include primary records regardless of whether they have child records, a Custom Report Type with a 'may or may not have related records' (left outer join) relationship must be created. Grouping data simultaneously along rows (Industry) and columns (Stage) requires the Matrix report format. Finally, enabling the automated setting to add new custom fields to custom report types eliminates the operational overhead of manually adding future fields to the CRT layout.

Step-by-Step Solution

1
Determine the required object relationship model ('with' vs 'with or without').
Standard report types for Accounts with Opportunities perform an inner join, omitting Accounts without Opportunities. A Custom Report Type (CRT) with 'A records may or may not have related B records' (left outer join) is required to include Accounts missing Opportunities.
Business requirement mandates seeing all Accounts, even those without related Opportunities.
2
Select the correct report layout format based on grouping requirements.
Matrix format is required to group data by both row (Account Industry) and column (Opportunity Stage) vectors.
Summary format only supports row groupings, whereas Matrix format supports two-dimensional grid summarizing.
3
Configure custom field maintenance strategy for the report type.
Enable 'Auto-add new custom fields to custom report types' in Salesforce setup.
By default, CRT layouts do not automatically include newly created custom fields, unlike standard report types. Enabling this setting ensures future fields appear in the report builder without manual layout editing.

Key Concept

Custom Report Type Object Relationships, Report Format Selection (Matrix), and CRT Field Layout Administration
Question 127Question

A Salesforce administrator is tasked with reassigning record ownership following a corporate sales territory reorganization. The administrator plans to use the native Mass Transfer tool in Setup rather than external API-based tools like Data Loader. Which two statements correctly describe the capabilities and operational behaviors of the native Mass Transfer tool? (Choose 2 options)

Select all that apply

Show answer & explanation

Answer: The administrator can mass transfer Accounts, Leads, Cases, Contracts, and Custom Objects, but cannot select standalone Opportunities for mass transfer without transferring their parent Accounts.; When performing a mass transfer of Accounts, the wizard provides options to selectively include open opportunities, closed opportunities, and open cases owned by the account owner.

Answer

The native Mass Transfer tool supports reassigning Accounts, Leads, Cases, Contracts, and Custom Objects, but requires standalone Opportunities to be updated via Account transfer or Data Loader. Additionally, when transferring Accounts, the setup wizard explicitly allows administrators to include related open opportunities, closed opportunities, and open cases owned by the existing account owner.
The native Mass Transfer feature in Salesforce Setup is designed for specific objects including Accounts, Leads, Cases, Contracts, and Custom Objects. Standalone Opportunities cannot be mass transferred directly through a dedicated Mass Transfer Opportunities wizard; they must either be transferred as related records during an Account transfer or updated in bulk using Data Loader. Furthermore, when reassigning Accounts, the wizard explicitly grants options to transfer open opportunities, closed opportunities, and open cases owned by the target user.

Step-by-Step Solution

1
Identify the supported objects for native Mass Transfer in Salesforce Setup.
Confirm that native Mass Transfer covers Accounts, Leads, Cases, Contracts, and Custom Objects, but lacks a standalone wizard for Opportunities.
Understanding built-in administrative wizard boundaries prevents choosing incorrect tools for bulk ownership updates.
2
Evaluate the specific options available when transferring Accounts.
Recognize that the wizard offers checkboxes to transfer open opportunities, closed opportunities, and open cases owned by the account owner.
Account ownership transfers cascade access and ownership to child records based on selected wizard options.
3
Review system limits and execution behavior for Mass Transfer.
Disprove batch limits of 50,000 (UI is limited to 250 records per query result) and rule out automatic automation bypasses.
Mass operations in the UI adhere to governor search limits (250 items per transfer operation) and standard order of execution.

Key Concept

Native Mass Transfer Capabilities and Limitations
Question 128Question

An administrator needs to customize the items available in the navigation bar for a custom Lightning App accessed via the Salesforce Mobile App. What is the correct sequence of steps to configure these navigation items in Setup?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order to customize navigation items for a Lightning App in the Salesforce Mobile App is: 1) Access App Manager in Setup, 2) Edit the desired Lightning App, 3) Select Navigation Items from App Settings, 4) Add items to the Selected Items list, and 5) Click Save.
Configuring mobile navigation for a Lightning App requires entering App Manager in Setup, editing the targeted Lightning App, selecting Navigation Items from the left-hand panel, choosing the required items into the Selected Items box, and saving the changes.

Step-by-Step Solution

1
Open Setup and search for App Manager.
The App Manager tool appears in the Quick Find results.
App Manager is the central hub for managing Lightning App configurations.
2
Find the relevant Lightning App and click Edit.
The Lightning App Builder settings menu opens.
App Settings must be edited to change navigation items.
3
Select the Navigation Items tab.
Dual listboxes showing Available Items and Selected Items are displayed.
This section manages which tabs/objects are included in the app.
4
Choose items and move them to Selected Items.
The navigation list reflects the chosen items in order.
Selected Items dictate the navigation items visible in the Salesforce Mobile App.
5
Save the configuration.
Changes take effect for all users assigned to the app.
Saving commits the changes to the app settings.

Key Concept

Customizing Lightning App Navigation for Salesforce Mobile
Question 129Question

Northern Trail Outfitters recently enabled Einstein Activity Capture (EAC) for its account executive team using Microsoft Exchange. Sales reps confirm that customer emails and calendar events automatically appear on the Activity Timeline of related Opportunity records. However, the Sales Operations manager reports that a standard custom report based on Tasks and Events fails to display these automatically captured emails. What is the cause of this reporting issue, and how should the administrator resolve it?

Show answer & explanation

Answer: EAC activities are stored in external AWS servers rather than as standard Salesforce Task and Event records, making them unavailable in standard activity reports; the administrator should leverage Activity 360 or Activity Metrics reporting features.

Answer

Einstein Activity Capture data is stored in external AWS infrastructure rather than standard Salesforce Task and Event records, preventing it from showing in standard activity reports. The administrator should utilize Activity Metrics or Activity 360 reporting features.
Einstein Activity Capture (EAC) stores captured emails and calendar events in secure AWS storage off the core Salesforce platform to maintain high performance. Because these activities are not written as standard Task or Event records in the Salesforce database, standard Activity report types (Tasks and Events) cannot display them. To report on EAC activities, administrators must use built-in EAC reporting tools such as Activity Metrics, Activity 360, or CRM Analytics dashboards.

Step-by-Step Solution

1
Analyze how Einstein Activity Capture (EAC) handles data storage.
Identify that EAC stores captured emails and events off-core in external AWS infrastructure and streams them to the Activity Timeline, rather than writing standard Task/Event rows in the Salesforce database.
Understanding the architectural difference between standard activities and EAC captured activities is essential for troubleshooting reporting limitations.
2
Evaluate the impact on standard reporting tools.
Confirm that standard reports built on Tasks and Events only query records in the Salesforce database and therefore exclude EAC captured data.
Standard report types cannot directly query external AWS storage used by EAC.
3
Determine the appropriate solution for reporting on EAC activities.
Select Activity Metrics or Activity 360 / CRM Analytics EAC reporting options, which are designed to summarize and report on EAC activity data.
These features synthesize EAC data for reporting without requiring standard Task/Event record creation.

Key Concept

Einstein Activity Capture Data Storage and Reporting Architecture
Question 130Question

A Salesforce Administrator at an IT services company needs to allow support engineers to create a related Service Ticket record directly from an active Asset record. The solution must automatically populate the Asset lookup field with the current Asset record's details, default the Status field to 'Submitted', and display a streamlined set of fields to the user during creation. Which configuration should the administrator implement to fulfill these requirements?

Show answer & explanation

Answer: Create an Object-Specific Quick Action on the Asset object, configure predefined field values for the Asset and Status fields, and customize the action layout.

Answer

Create an Object-Specific Quick Action on the Asset object, configure predefined field values for the Asset and Status fields, and customize the action layout.
An Object-Specific Quick Action created on the Asset parent object has automatic access to the record context. Setting predefined field values allows the system to populate both the target record's lookup to Asset and fixed values like Status = 'Submitted'. Customizing the action layout controls which fields appear to the user.

Step-by-Step Solution

1
Determine the type of Quick Action required.
Identify that an Object-Specific Quick Action on the Asset object is required because the action must automatically reference the parent record context.
Global actions lack record context and cannot automatically populate record lookup fields based on the host page.
2
Configure predefined field values.
Set predefined field values for the Asset field (referencing the current Asset ID) and set the Status field to 'Submitted'.
Predefined field values satisfy the requirement to populate defaults automatically without requiring manual input from the user.
3
Customize the action layout and add to the page layout.
Arrange the necessary fields on the action layout and add the Quick Action to the Asset Lightning Page Layout / Mobile & Lightning Actions section.
Customizing the action layout ensures only the streamlined set of fields is presented to users during record creation.

Key Concept

Object-Specific Quick Actions and Predefined Field Values
Estimated Time:1m 30s
Question 131Question

Universal Containers implemented a validation rule on the Opportunity object to enforce data quality. The goal is to require a custom field, Discount_Approval_Code__c, whenever Discount_Percentage__c is updated to a value greater than 15% (0.15). However, administrators notice that when users update unrelated fields (such as Description) on existing records where Discount_Percentage__c was already set to 20% in the past, the system blocks the save and displays a validation error.

The current validation rule formula is:
AND(Discount_Percentage__c > 0.15, ISBLANK(Discount_Approval_Code__c))

Which formula modification correctly prevents the validation error from triggering during edits to unrelated fields while still enforcing the requirement when the discount is modified?

Show answer & explanation

Answer: AND(Discount_Percentage__c > 0.15, ISCHANGED(Discount_Percentage__c), ISBLANK(Discount_Approval_Code__c))

Answer

AND(Discount_Percentage__c > 0.15, ISCHANGED(Discount_Percentage__c), ISBLANK(Discount_Approval_Code__c))
The formula combining Discount_Percentage__c > 0.15, ISCHANGED(Discount_Percentage__c), and ISBLANK(Discount_Approval_Code__c) ensures the validation rule triggers only when the discount percentage field itself is modified in the transaction. When an administrator or user edits an unrelated field like Description on an existing record with a high discount, ISCHANGED evaluates to FALSE and the save completes successfully without requiring an approval code.

Step-by-Step Solution

1
Identify why the validation rule triggers on unrelated field updates.
The current formula checks if Discount_Percentage__c > 0.15 on every save operation regardless of whether Discount_Percentage__c was modified in that transaction.
Validation rule formulas run their full boolean evaluation whenever any editable field on the record is saved.
2
Determine the Salesforce formula function that checks whether a specific field's value has changed during the edit.
The ISCHANGED() function returns TRUE only if the current value differs from the prior value in the current context.
ISCHANGED restricts rule execution specifically to edits where the target field has been updated.
3
Combine conditions to form the updated validation rule formula.
AND(Discount_Percentage__c > 0.15, ISCHANGED(Discount_Percentage__c), ISBLANK(Discount_Approval_Code__c))
This formula successfully verifies that the discount exceeds 15%, that the discount field was modified in this save, and that the approval code is blank.

Key Concept

Using ISCHANGED() in Salesforce validation rules to prevent false positives when editing unrelated record fields
Question 132Question

An administrator creates a new Record Type named "Enterprise Deal" on the Opportunity object. Users assigned to the "Enterprise Sales Profile" report that when creating new records under this record type, they see an incorrect arrangement of fields and cannot select the appropriate values from a custom picklist field named Deal_Structure__c.

Which two administrative actions must be completed to resolve these issues? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Edit the Deal_Structure__c picklist settings directly within the Enterprise Deal Record Type configuration to select the available values.; Update the Page Layout Assignment matrix to map the Enterprise Sales Profile and Enterprise Deal Record Type to the enterprise page layout.

Answer

To resolve the page layout and picklist display issues, the administrator must assign the appropriate page layout to the Enterprise Sales Profile for the Enterprise Deal Record Type under Page Layout Assignment, and edit the picklist settings for Deal_Structure__c within the Enterprise Deal Record Type configuration to select the allowable values.
Page layout display is determined by the combination of a user's Profile and the Record Type of the record via Page Layout Assignment. Additionally, the specific picklist values available to a user are governed by the Record Type definition itself, where individual picklist fields must be edited to select which values are active for that record type.

Step-by-Step Solution

1
Navigate to Object Manager > Opportunity > Record Types > Enterprise Deal.
Locate the Picklists Available for Editing section on the record type.
Record types control which picklist values are available to users when creating or editing records assigned to that record type.
2
Edit the Deal_Structure__c picklist field under the Enterprise Deal record type and move required values from Available to Selected.
The specified picklist values become selectable when creating Enterprise Deal records.
New record types do not automatically include all custom picklist values unless explicitly assigned.
3
Navigate to Object Manager > Opportunity > Page Layouts > Page Layout Assignment.
Open the assignment matrix for Profiles and Record Types.
Page layouts are assigned based on a user's Profile and the record's Record Type.
4
Locate the row for Enterprise Sales Profile and column for Enterprise Deal Record Type, then assign the Enterprise Opportunity Page Layout.
Users with the Enterprise Sales Profile see the correct field arrangement when viewing or creating Enterprise Deal records.
Ensures the profile receives the designated layout for that specific record type.

Key Concept

Page Layouts and Record Types Assignment
Estimated Time:1m 30s
Question 133Question

A support operations manager at a commercial refrigeration logistics firm reports that urgent equipment failure tickets submitted through Web-to-Case are not being routed to the Tier-3 Emergency Queue upon creation. Instead, all new cases remain assigned to the Default Case Owner. An investigation shows that an active Case Escalation Rule entry was created with an escalation action set to reassign high-priority cases to the Tier-3 Emergency Queue zero hours after case creation. Which configuration change should the Salesforce administrator make to resolve this issue?

Show answer & explanation

Answer: Create an active Case Assignment Rule entry with criteria matching high-priority cases to assign ownership directly to the Tier-3 Emergency Queue upon record creation.

Answer

The administrator should create an active Case Assignment Rule entry with criteria matching high-priority cases to assign ownership directly to the Tier-3 Emergency Queue upon record creation.
Case Assignment Rules are specifically designed to evaluate criteria upon record creation and route cases to the appropriate user or queue immediately. Because the goal is initial routing upon creation via Web-to-Case, a Case Assignment Rule entry is the required mechanism.

Step-by-Step Solution

1
Identify the functional purpose of Case Automation features in Salesforce.
Recognize that Case Assignment Rules control initial ownership upon case creation, while Case Escalation Rules handle SLA breaches for open cases over time.
Initial routing must happen via Case Assignment Rules when Web-to-Case runs with the assignment checkbox enabled or automated rule execution.
2
Analyze why relying on Escalation Rules for initial record routing fails.
Escalation rules monitor existing cases for resolution delays or SLA thresholds; using zero-hour escalation actions for initial routing is improper configuration and does not handle immediate initial ownership correctly.
Escalation actions execute based on elapsed time criteria relative to creation or modification, whereas Assignment Rules run immediately during record insert.
3
Determine the proper Salesforce configuration solution.
Configure a Case Assignment Rule entry that targets high-priority records and assigns them directly to the Tier-3 Emergency Queue upon creation.
This guarantees instant, correct queue ownership as soon as the case is created via Web-to-Case.

Key Concept

Case Assignment Rules vs. Case Escalation Rules functional scope and timing
Question 134Question

An administrator is setting up data quality checks on the Lead object. Which two statements accurately describe the characteristics and behavior of Salesforce validation rules? (Select TWO)

Select all that apply

Show answer & explanation

Answer: A validation rule evaluates a formula expression and prevents the record from saving if the formula evaluates to true.; Validation rules run when records are created or updated via the user interface, API operations, or data import tools.

Answer

The correct statements are that a validation rule evaluates a formula expression to prevent saving when true, and that validation rules execute for records created or updated through the UI, API, or data import tools.
Validation rules execute whenever a record is created or updated across any input channel (UI, API, or bulk tools). When the validation rule formula evaluates to true, Salesforce displays the designated error message and prevents the transaction from completing.

Step-by-Step Solution

1
Analyze how validation rules trigger error messages.
Validation rule logic is triggered whenever the formula expression evaluates to true, resulting in an error and preventing record save.
This is the core functional mechanism of validation rules in Salesforce.
2
Determine the scope of execution for validation rules.
Validation rules run on all data operations including UI saves, API calls, and data import utilities.
Salesforce enforces system-level validation regardless of data entry channel to maintain data integrity.

Key Concept

Salesforce validation rules contain formula expressions that evaluate to true when criteria are violated, preventing records from saving across all input channels.
Question 135Question

A sales director at Meridian Global requests that an administrator configure Salesforce so that when a sales manager creates a post-meeting follow-up Task assigned to a team of 4 account representatives, a single shared Task record is created that all 4 representatives can update together, while simultaneously linking that single Task to 3 primary client Contacts and 2 separate Account records.

Based on standard Salesforce Activity Management capabilities and limits, how should the administrator respond?

Show answer & explanation

Answer: Explain that while up to 50 Contacts can be related to a single Task using Shared Activities, a Task can only be related to one Account, and assigning a Task to multiple users creates individual copies for each user rather than a single shared record.

Answer

Explain that while up to 50 Contacts can be related to a single Task using Shared Activities, a Task can only be related to one Account, and assigning a Task to multiple users creates individual copies for each user rather than a single shared record.
Salesforce Shared Activities enables users to relate up to 50 Contacts to a single Task or Event, but an activity can only be related to a single Account (or other parent object via the Related To / WhatId field). Furthermore, assigning a task to multiple users creates an independent copy of the task for each assigned user rather than a single shared record.

Step-by-Step Solution

1
Evaluate the requirement for relating multiple Contacts and Accounts to a single Task.
Salesforce Shared Activities allows relating up to 50 Contacts (Name field) to a single Task or Event, but only 1 Account (Related To field) can be associated with an activity.
The Related To / WhatId field on activities accepts only a single parent record, such as one Account, Opportunity, or Case.
2
Evaluate the requirement for creating a single shared Task record for multiple assigned users.
When a Task is created and assigned to multiple users or a group, Salesforce creates separate, independent copies of the Task for each assigned user.
Tasks track individual owner accountability; changes made by one user to their assigned copy do not affect other users' copies.
3
Synthesize the findings to formulate the administrator's response.
The requested setup is not supported as described because an activity cannot link to multiple Accounts and assigning to multiple users creates separate copies.
This accurately reflects both standard system limits and the behavior of group task creation.

Key Concept

Shared Activities Limits and Group Task Assignment Behavior
Estimated Time:2m 0s
Question 136Question

An administrator at Aether Dynamics needs to implement a custom sales pipeline for a new Subscription Renewals team. The renewal pipeline requires a distinct set of Opportunity stages compared to the standard enterprise sales pipeline. Which sequence of administrative steps must be completed to ensure the Subscription Renewal team sees only their specific opportunity stages when creating opportunities?

Show answer & explanation

Answer: Create a new Sales Process with the renewal stages, create a new Opportunity Record Type linked to that Sales Process, and assign the record type to the user profiles.

Answer

The correct sequence is to create a new Sales Process selecting the appropriate renewal stages, link that Sales Process to a new Opportunity Record Type, and assign the Record Type to the relevant user profiles.
Creating a Sales Process first allows the administrator to select the precise subset of Opportunity Stage values needed for the Subscription Renewal sales process. Connecting this Sales Process to a new Opportunity Record Type and assigning it to profiles ensures users see only the relevant stages for their business process.

Step-by-Step Solution

1
Create a new Sales Process
Defines the specific set of stage picklist values required for the renewal pipeline.
Opportunity stage picklist values are governed by Sales Processes, which act as a filter for Opportunity stages.
2
Create a new Opportunity Record Type
Links the newly created Sales Process to a record type for user selection.
Record types allow different page layouts and picklist values (via Sales Processes) to be assigned to different users.
3
Assign the Record Type to User Profiles
Ensures the Renewal team members have access to create opportunities with the renewal pipeline stages.
Profile assignments control which record types are available to users when creating or updating records.

Key Concept

Sales Process and Opportunity Record Type Association
Estimated Time:1m 30s
Question 137Question

An administrator at Apex Logistics is optimizing the Lightning Sales Console to improve navigation efficiency for sales representatives. The sales manager requests that when representatives open a related Contact record from an Account record page, the Contact record should automatically open as a subtab of the parent Account workspace tab instead of opening as a new main workspace tab. Which configuration change should the administrator make in Setup to satisfy this requirement?

Show answer & explanation

Answer: Configure Navigation Rules for the Sales Console app within the App Manager.

Answer

Configure Navigation Rules for the Sales Console app within the App Manager to set Contact records to open as subtabs of Account records.
In Lightning console applications, Navigation Rules configured within App Manager allow administrators to define whether records opened from a parent record open as primary workspace tabs or as subtabs anchored under the parent record.

Step-by-Step Solution

1
Navigate to Setup and search for App Manager.
Access the list of installed standard and custom Lightning apps.
Console application UI layout features and tab navigation settings are managed at the App level.
2
Edit the Lightning Sales Console app and select Navigation Rules.
View object navigation rules for primary tabs and subtabs.
Navigation Rules specify how related records behave when clicked within the console.
3
Set the Contact object to open as a subtab of Account.
Contacts opened from an Account page layout display as subtabs within the parent Account workspace tab.
This directly fulfills the business requirement to keep related records contextualized under their parent tab.

Key Concept

Console Navigation Rules
Estimated Time:1m 30s
Question 138Question

A Salesforce administrator is editing the layout of a newly created Custom Report Type. Which two capabilities can the administrator utilize when customizing the field layout section of the Custom Report Type? (Select 2 options)

Select all that apply

Show answer & explanation

Answer: Add fields from related objects referenced via lookup relationships.; Create custom layout sections to organize fields into logical groupings for users.

Answer

Administrators customizing a Custom Report Type field layout can create custom sections to group fields logically and add fields from related objects via lookup relationships.
When configuring a Custom Report Type, administrators can customize the field layout by adding fields from related objects via lookup paths (up to 4 levels) and organizing fields into clear, custom sections to improve report builder usability.

Step-by-Step Solution

1
Identify valid Custom Report Type field layout administrative capabilities.
Creating custom sections and adding lookup fields are native features of the Custom Report Type field layout editor.
These capabilities help streamline field presentation and expand data visibility across related entities.
2
Evaluate invalid layout configuration assumptions.
Roll-up summaries, row-level formulas, and FLS overrides cannot be established within the Custom Report Type layout.
These actions belong to Object Manager object settings, individual Report Builder instances, or Profile/Permission Set security settings.

Key Concept

Custom Report Type Layout Customization
Question 139Question

An IT Operations team requires a dedicated Chatter group in Salesforce to communicate system maintenance alerts. The group must meet two key requirements: non-members must be able to search for the group and request to join, and only the Group Owner and Group Managers should be allowed to create new posts, while regular members may only view and reply to existing posts. Which TWO settings or configurations should the Salesforce Administrator implement to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Set the group access level to Private.; Enable the Broadcast group setting.

Answer

To meet the requirements, the administrator must set the group access level to Private and enable the Broadcast group setting.
Setting the group to Private ensures that the group is discoverable in search and allows non-members to request membership, which requires approval from a group owner or manager. Enabling the Broadcast group configuration restricts the creation of new posts exclusively to owners and managers, while permitting group members to view feed items and add comments.

Step-by-Step Solution

1
Determine group visibility and join request requirements
Selecting Private group access allows the group to appear in search results and enables non-members to submit membership requests that require manager approval.
Public groups do not require join approval, whereas Unlisted groups hide the group entirely and prevent non-members from requesting to join.
2
Determine posting permission requirements
Enabling the Broadcast group setting restricts feed post creation to group owners and managers while allowing standard members to comment on posts.
Standard Chatter group roles normally allow all members to post; Broadcast groups provide explicit granular posting restrictions at the group level.

Key Concept

Chatter Group Access Types and Broadcast Permissions
Question 140Question

A Salesforce Administrator is setting up a team dashboard to monitor sales operations. The administrator plans to add dashboard filters so team members can interactively filter the visual data by territory and industry. Which TWO statements accurately describe the capabilities and behavior of dashboard filters in Salesforce? (Select 2)

Select all that apply

Show answer & explanation

Answer: Dashboard filters apply only to components whose underlying source reports contain equivalent fields to the filter criteria.; A single dashboard filter allows administrators to define multiple filter options to categorize and group dataset results.

Answer

Dashboard filters apply to components whose source reports contain matching fields, and administrators can define multiple filter options within a filter definition to group data.
Dashboard filters work by mapping specified filter fields to corresponding fields in the source reports of each dashboard component. Additionally, administrators can define multiple filter options per filter to give users predefined choices for slicing the data.

Step-by-Step Solution

1
Evaluate field mapping requirements for dashboard filters.
Confirm that for a dashboard component to reflect a filter, its source report must include a compatible field mapped to that filter.
Filters interact directly with report data fields.
2
Analyze filter configuration capabilities.
Verify that administrators can configure multiple options (such as combinations of picklist values or date ranges) per filter.
This allows users to choose from predefined subsets when interacting with the dashboard.
3
Distinguish dashboard filter functionality from security and dynamic dashboard settings.
Recognize that adding filters does not alter the running user setting or override record visibility rules.
Dashboard security settings (running user) and interactive dynamic filters operate independently.

Key Concept

Dashboard Dynamic Filters Configuration and Mechanics
Estimated Time:1m 0s
PreviousPage 7 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin