All practice questions

1784 questions

Question 881Question

A Salesforce administrator is configuring Lightning App Builder pages for a custom object named Asset_Inspection__c. The requirements state that specific fields must only display when an inspection fails, and custom record layouts must be deployed selectively to different teams. Which two statements accurately describe the functionality of Lightning App Builder page activations and Dynamic Forms component visibility? (Select 2 choices.)

Select all that apply

Show answer & explanation

Answer: Setting a conditional component visibility filter on a field in Dynamic Forms hides the field from the Lightning user interface but does not prevent access through APIs or standard reports.; Activating a Lightning Record Page by App, Record Type, and Profile takes precedence over both App Default and Org Default activations for matching users.

Answer

Dynamic Forms component visibility controls UI display without altering API or reporting access, and activating a Lightning Record Page by App, Record Type, and Profile overrides App Default and Org Default assignments.
Dynamic Forms visibility filters are designed for user interface display control and do not modify underlying Field-Level Security or reporting access. Furthermore, Lightning Record Page activation follows a strict hierarchy where the combination of App, Record Type, and Profile assignment takes precedence over broader App Default and Org Default settings.

Step-by-Step Solution

1
Analyze Dynamic Forms visibility behavior
Dynamic Forms visibility rules conditionally hide or reveal components/fields on the user interface, but underlying data security (FLS and sharing rules) remains unchanged for reports and API access.
UI component visibility is decoupled from data accessibility enforcement.
2
Evaluate Lightning Record Page activation precedence
The activation hierarchy prioritizes explicit matches: App + Record Type + Profile assignment overrides App Default assignment, which in turn overrides Org Default assignment.
Salesforce evaluates page assignments from most granular (App, Record Type, Profile) to least granular (Org Default).

Key Concept

Lightning App Builder Activation Precedence and Dynamic Forms UI Visibility
Question 882Question

An administrator at Orion Solar needs to configure different stage values for the Opportunity Stage picklist to support two distinct sales teams: Direct Commercial Sales and Partner Wholesale. Which feature must the administrator set up first to determine the specific stage picklist values available before assigning them to an Opportunity Record Type?

Show answer & explanation

Answer: Sales Process

Answer

Sales Process
The Sales Process feature must be configured first because the Opportunity Stage picklist is a special business process field. A Sales Process selects a subset of master Stage values, which is then assigned to an Opportunity Record Type.

Step-by-Step Solution

1
Identify requirement
Two distinct sales teams require different sets of Opportunity Stage picklist values.
Salesforce enforces pipeline stage selection through Sales Processes.
2
Determine prerequisite setup component
Create a custom Sales Process for each sales team.
In Salesforce, Opportunity Stage is a special picklist controlled exclusively by a Sales Process.
3
Link Sales Process to Record Type
Associate each Sales Process to its corresponding Opportunity Record Type.
This displays the appropriate sales pipeline stages to each sales team based on their record type.

Key Concept

Sales Process and Opportunity Stage linkage
Question 883Question

Universal Containers uses a custom Work Order object with two Record Types: Standard Service and Emergency Service. An administrator needs to make the 'Dispatched Outside Vendor' value in the Resolution Code picklist available only when creating or editing Emergency Service records. In addition, Support Agent profile users must see the 'Emergency Operations' layout when viewing Emergency Service records, while continuing to see the 'Standard Operations' layout for Standard Service records. Which two administrative configuration steps are required to fulfill these requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Edit the Picklists Available for Editing section on the Emergency Service Record Type detail page to include 'Dispatched Outside Vendor'.; Update Page Layout Assignments to map the Support Agent Profile and Emergency Service Record Type combination to the Emergency Operations layout.

Answer

The administrator must edit the picklists available for editing under the Emergency Service Record Type to include 'Dispatched Outside Vendor', and update Page Layout Assignments to assign the Emergency Operations layout to the Support Agent profile for the Emergency Service Record Type.
To restrict picklist choices to specific record types, administrators edit the Picklists Available for Editing section on the corresponding Record Type setup page. To present different page layouts to users based on their role and record context, administrators use the Page Layout Assignment matrix to map Profile and Record Type combinations to specific page layouts.

Step-by-Step Solution

1
Modify record type picklist selection
The 'Dispatched Outside Vendor' picklist value becomes selectable exclusively on Emergency Service records.
Picklist value availability per record type is governed within the Record Type configuration settings in Object Manager.
2
Configure the Page Layout Assignment grid
Support Agent users are assigned the Emergency Operations page layout when accessing Emergency Service records.
Page layout assignment matrix pairs Profile and Record Type combinations to determine which page layout a user sees.

Key Concept

Page Layouts and Record Types Assignment
Question 884Question

An administrator at a global logistics firm needs to immediately block system access for an operations supervisor who has suddenly departed the company. When attempting to deactivate the user account, Salesforce displays an error because the supervisor is designated as the sole running user for active scheduled flows and process automations. Which action should the administrator take to immediately prevent login while maintaining uninterrupted execution of automated business processes?

Show answer & explanation

Answer: Freeze the user account immediately, then reassign the automated processes to an active user before deactivating the account.

Answer

Freeze the user account immediately, then reassign the automated processes to an active user before deactivating the account.
Freezing a user account immediately stops the user from logging into Salesforce while keeping the account active in the background. This prevents security risks without breaking existing process automations, giving administrators time to update running user references before performing a full account deactivation.

Step-by-Step Solution

1
Identify the immediate requirement to block user login without disrupting system automation.
Determined that account deactivation is blocked due to active process dependencies.
Direct user deactivation fails when a user is tied to active automated steps, default lead/case owners, or hierarchy fields.
2
Select the appropriate administrative capability for temporary login prevention.
Freezing the user account stops authentication while preserving existing configuration references.
Freezing prevents user login immediately without unassigning licenses or causing automated processes to fail.
3
Complete the offboarding workflow.
Reassign process dependencies to an active running user and deactivate the user account.
Once process references are migrated, deactivation can be completed cleanly to free up the user license.

Key Concept

User Freezing vs. User Deactivation
Estimated Time:1m 30s
Question 885Question

A Salesforce Administrator is designing a custom data model for a university to connect Students (`Student__c`) and Courses (`Course__c`). A student can enroll in multiple courses, and a course can have multiple students. The business requirements state that the total number of enrolled students must be dynamically calculated on each course record, and deleting a student must automatically remove their specific enrollment records. Which two configuration steps should the administrator take to meet these requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a custom junction object with Master-Detail relationships to both the Course and Student objects.; Create a Roll-Up Summary field on the Course object that calculates the count of related enrollment records.

Answer

To implement a many-to-many relationship with automated deletion cascading and aggregate metrics, the administrator must create a custom junction object with Master-Detail relationships to both Course and Student, and create a Roll-Up Summary field on the Course object to calculate total enrollment records.
Establishing a junction object with Master-Detail relationships to both master objects creates a robust many-to-many structure. Master-Detail relationships allow the parent object to use Roll-Up Summary fields to count child records and ensure that deleting a primary record automatically cascade-deletes the associated junction records.

Step-by-Step Solution

1
Analyze relationship cardinality and deletion requirements.
A many-to-many relationship requires a custom junction object with Master-Detail relationships to enable cascade-deletion when a master record is removed.
Master-Detail relationships enforce cascading deletion of detail records when the master record is deleted.
2
Evaluate field capabilities for calculating total enrollments.
Roll-Up Summary fields are created on the master object to aggregate child records in a Master-Detail relationship.
Lookup relationships do not support native Roll-Up Summary fields without custom automation or Apex.

Key Concept

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

An administrator at Apex Solutions is optimizing the Lightning Sales Console application to streamline workflows for sales representatives. The team needs to ensure that when a rep opens a related Contact record from an Account record view, the Contact record automatically opens as a subtab under the parent Account workspace tab rather than a main workspace tab. In addition, reps need the capability to perform repetitive, multi-step field updates on multiple records simultaneously from list views. Which set of configurations should the administrator implement in Salesforce?

Show answer & explanation

Answer: Configure Navigation Rules in the App Manager for the Sales Console app to open Contacts as subtabs of Accounts, and add the Macros component to the app's Utility Bar to support bulk macros.

Answer

Configure Navigation Rules in the App Manager for the Sales Console app to open Contacts as subtabs of Accounts, and add the Macros component to the app's Utility Bar to support bulk macros.
The correct solution involves configuring App Navigation Rules in App Manager to force child records (Contacts) to open as subtabs under their parent records (Accounts) in the Lightning Sales Console. Additionally, adding the Macros utility item to the console's Utility Bar enables sales reps to run macros, including bulk macros for performing multi-step actions across multiple list view records.

Step-by-Step Solution

1
Identify the tab navigation requirement in Lightning Sales Console.
Navigation Rules within App Manager control whether child records open as subtabs of parent records (e.g., Contacts under Accounts) or as top-level workspace tabs.
By setting Navigation Rules for the Sales Console app, child records open contextually under their parent record tab.
2
Identify the requirement for executing multi-step updates on multiple records from a list view.
Adding the Macros component to the Console Utility Bar gives reps access to macros, including bulk macros that execute on multiple records selected from a list view.
Bulk macros streamline repetitive tasks across multiple records directly within console list views.

Key Concept

Sales Console Navigation Rules and Macro Utility Bar Setup
Estimated Time:2m 0s
Question 887Question

A System Administrator at Cloud Kicks needs to enable support agents to quickly log a specialized follow-up record directly from an active Case record page in Lightning Experience. The requirement specifies that when launched, the creation dialog must automatically populate the Priority field to 'High' and set the Related To field to the current Case, while presenting a stripped-down form layout containing only the Subject, Due Date, and Description fields. Which configuration strategy should the administrator implement to satisfy these business requirements?

Show answer & explanation

Answer: Create an Object-Specific Create Record Quick Action on the Case object, customize its action layout to show only Subject, Due Date, and Description, set Predefined Field Values for Priority and Case, and place the action on the Case page layout.

Answer

Create an Object-Specific Create Record Quick Action on the Case object, customize its action layout to show only Subject, Due Date, and Description, set Predefined Field Values for Priority and Case, and place the action on the Case page layout.
Object-Specific Quick Actions are specifically designed to create related records within the context of a host record (such as Case). They feature dedicated Action Layouts that allow admins to display only necessary fields (Subject, Due Date, Description) and support Predefined Field Values to automatically set values like Priority to 'High' and assign the parent Case ID.

Step-by-Step Solution

1
Identify the contextual requirement for creating a related record with automatic parent linking and custom default field values.
Determine that an Object-Specific Quick Action is required because Global Actions cannot infer relationship context from a host record page.
Object-Specific Quick Actions inherit record context (such as Case ID) and support Predefined Field Values.
2
Configure the Action Layout and Predefined Field Values.
Remove unnecessary fields from the action layout so only Subject, Due Date, and Description remain, and define formulas/static values for default fields.
Action layouts dictate the exact fields shown in the quick action dialog without affecting standard record page layouts.
3
Add the Quick Action to the appropriate Lightning Experience actions section on the target page layout.
Make the quick action available to end users on the Case Lightning record page.
Actions must be added to the Salesforce Mobile and Lightning Experience Actions section of the object page layout to appear in the UI.

Key Concept

Object-Specific Quick Actions vs. Global Quick Actions and Custom Buttons
Question 888Question

TechWave Distribution uses a custom object named Partner_Evaluation__c to conduct performance reviews for channel partners. The Organization-Wide Default (OWD) for Partner_Evaluation__c is currently set to Private, and the 'Grant Access Using Hierarchies' checkbox on the custom object definition has been deselected by an administrator.

The sales leadership team requires the following record access behavior:
1. Sales managers must be able to view and edit evaluation records owned by users below them in the role hierarchy.
2. Members of the Partner Operations team must be able to view all evaluation records where the Rating field is set to 'High Priority', regardless of record ownership.

Which TWO configuration steps should the administrator take to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Select the 'Grant Access Using Hierarchies' setting on the Partner_Evaluation__c custom object definition.; Create a criteria-based sharing rule on Partner_Evaluation__c that shares records where Rating equals 'High Priority' with the Partner Operations Public Group.

Answer

The administrator must enable 'Grant Access Using Hierarchies' on the custom object definition to grant manager access, and create a criteria-based sharing rule sharing 'High Priority' records with the Partner Operations Public Group.
Selecting 'Grant Access Using Hierarchies' allows users higher in the role structure to inherit the access permissions of their subordinates for custom objects. Combining this with a criteria-based sharing rule satisfies the requirement to expose specific records matching field criteria ('High Priority') to a group of users.

Step-by-Step Solution

1
Evaluate requirement for role hierarchy access on the custom object
Identify that custom objects allow disabling 'Grant Access Using Hierarchies'. Re-enabling this checkbox grants record access to users higher in the role hierarchy.
By default for custom objects, 'Grant Access Using Hierarchies' can be toggled. Selecting it allows managers to inherit owner permissions from subordinates without needing manual sharing rules.
2
Evaluate requirement for field-based record visibility for a team
Determine that a criteria-based sharing rule is required to share records matching Rating = 'High Priority' with the Partner Operations team.
Criteria-based sharing rules allow access to be granted to a Public Group based on field values regardless of who owns the records.

Key Concept

Custom Object Role Hierarchy Access and Criteria-Based Sharing Rules
Question 889Question

Northern Trail Outfitters recently introduced a dedicated hardware repair unit. The Salesforce Administrator created a custom Case page layout and created a new Case Record Type named 'Hardware Repair'. However, support reps report that when creating a 'Hardware Repair' case, the Status field shows standard customer support picklist options rather than the specialized statuses required for repairs, such as 'In Diagnostics' and 'Parts Ordered'. What administrative setup step did the administrator omit during configuration?

Show answer & explanation

Answer: Creating a dedicated Support Process containing the specialized Status picklist values and assigning it to the 'Hardware Repair' Case Record Type.

Answer

The administrator must create a dedicated Support Process containing the new Status values and associate it with the 'Hardware Repair' Case Record Type.
On the Case object, the available options for the Case Status field are governed by a Support Process. To display customized lifecycle statuses for a specific record type, an administrator must first create a Support Process containing those specific Status values and then select that Support Process when setting up or modifying the Case Record Type.

Step-by-Step Solution

1
Identify the relationship between Case Status, Support Processes, and Case Record Types.
Recognize that the Case Status field is controlled by Support Processes rather than standard object picklist edit menus.
On the Case object, Case Status availability for different business streams is governed by Support Processes.
2
Determine missing prerequisite configuration.
A custom Support Process must be defined first to specify which lifecycle Status values are active for the repair lifecycle.
When creating a Case Record Type, Salesforce requires the selection of an existing Support Process.
3
Associate the Support Process with the Record Type.
Linking the created Support Process to the 'Hardware Repair' Record Type ensures users see the correct Status picklist values.
Without linking the correct Support Process, the Record Type defaults to an existing or standard Support Process.

Key Concept

Support Process Dependency on Case Record Types
Question 890Question

An administrator is setting up Salesforce Knowledge for a customer support team. The administrator has already granted the required object-level permissions to the support agents. Which additional setting must be enabled directly on each support agent's User record to allow them to create and publish Knowledge articles?

Show answer & explanation

Answer: The Knowledge User feature license checkbox

Answer

The Knowledge User feature license checkbox must be enabled on the user record.
To create, edit, archive, or publish Salesforce Knowledge articles, a user must have the Knowledge User feature license enabled on their individual User record in addition to having appropriate object permissions.

Step-by-Step Solution

1
Identify the user-level feature license requirement for Salesforce Knowledge.
Recognize that creating and publishing articles requires the Knowledge User feature license in addition to object permissions.
Salesforce requires a specific feature license for Knowledge authoring functionality.
2
Navigate to the User record setup.
Locate the Knowledge User checkbox field on the user detail page.
Feature licenses are granted per user via checkboxes on the User record.

Key Concept

Salesforce Knowledge User Feature License
Question 891Question

Match each Salesforce Case Collaboration feature to its corresponding administrative requirement or operational behavior.

Click a left item, then click its matching right item

Items

Predefined Case Teams
Case Team Roles
Case Feed Quick Actions
Feed Item Visibility

Matches

Show answer & explanation

Answer

Predefined Case Teams matches with allowing administrators to quickly add a reusable group of predefined internal users and roles; Case Team Roles matches with defining the explicit access level granted to team members; Case Feed Quick Actions matches with providing agents with interactive publisher buttons on the case feed; Feed Item Visibility matches with determining whether Chatter posts are restricted to internal users or shared with external users.
Each feature aligns directly with its Salesforce functional implementation: Predefined Case Teams allow standard grouping of users and roles; Case Team Roles control record access levels; Case Feed Quick Actions expose publisher buttons for agent workflows; Feed Item Visibility governs internal versus external post accessibility.

Step-by-Step Solution

1
Identify the administrative purpose of Predefined Case Teams.
Recognize that Predefined Case Teams store reusable lists of support members and assigned roles for fast addition to case records.
This avoids manually selecting individual users each time a standard collaboration group is required on a case.
2
Analyze how Case Team Roles control security and record access.
Determine that Case Team Roles dictate whether members get Private, Read Only, or Read/Write access to the targeted case.
Record sharing granted through Case Teams is governed directly by the assigned role's configured access level.
3
Evaluate the functional utility of Case Feed Quick Actions.
Establish that Quick Actions enable agents to perform record updates, log activity, or communicate directly from the feed publisher.
Quick Actions enhance agent productivity by embedding record operations into the feed timeline layout.
4
Determine the scope of Feed Item Visibility controls.
Confirm that Feed Item Visibility toggles post access between internal colleagues and external Experience Cloud site users.
Support teams need to keep internal notes private while sharing relevant updates with external customers.

Key Concept

Salesforce Case Collaboration Tools Configuration and Access Controls
Question 892Question

A Salesforce Administrator at Zenith Telecom is configuring a new enterprise telecommunications solution, 'FiberMax 10G', to be sold at regional rates using a custom price book named 'EMEA Enterprise Price Book'. What is the correct sequential order of administrative and user steps required to make this new product available and add it as an Opportunity Line Item using the custom price book?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of steps is: 1) Create the 'FiberMax 10G' Product record and set its status to Active, 2) Create an active Standard Price Entry in the Standard Price Book, 3) Create and activate the 'EMEA Enterprise Price Book', 4) Add a custom Price Book Entry for 'FiberMax 10G' to the 'EMEA Enterprise Price Book', and 5) Select the 'EMEA Enterprise Price Book' on an Opportunity and add 'FiberMax 10G' as an Opportunity Line Item.
In Salesforce Core Administration, setting up product pricing follows a mandatory dependency order: First, create the Product record and set it to Active. Second, add an active Standard Price entry in the Standard Price Book because Salesforce requires standard pricing prior to custom pricing setup. Third, create and activate the custom price book. Fourth, create a custom Price Book Entry linking the product to the custom price book. Fifth, set the custom price book on the Opportunity and add the product as an Opportunity Line Item.

Step-by-Step Solution

1
Create and activate the Product record
Product 'FiberMax 10G' is established in the org.
Price book entries cannot be created without an existing active base product record.
2
Create Standard Price Entry
An active standard list price is assigned in the Standard Price Book.
Salesforce architecture mandates an active standard price entry before any custom price book entries can be created for a product.
3
Create and activate Custom Price Book
'EMEA Enterprise Price Book' is created and active.
A custom price book must be active to hold price book entries and be visible to end users.
4
Create Custom Price Book Entry
Product entry with regional pricing is added to the custom price book.
Associates the specific list price required for enterprise sales in the target region.
5
Add product to Opportunity
'FiberMax 10G' is added as an Opportunity Line Item.
The opportunity uses the custom price book to draw available line items and pricing.

Key Concept

Salesforce Product and Price Book Architecture Prerequisites
Question 893Question

A Salesforce administrator at a commercial architecture firm creates a custom picklist field named 'Project Scope' on the Lead object. To retain this data during lead conversion, matching custom picklist fields with identical values are created on both the Account and Opportunity objects. However, during conversion testing, the 'Project Scope' field on the newly created Opportunity record remains blank. Which administrative action is required to ensure the lead field data populates on the Opportunity record upon conversion?

Show answer & explanation

Answer: Configure Lead Custom Field Mapping in Setup to explicitly map the Lead picklist field to the Opportunity picklist field.

Answer

Configure Lead Custom Field Mapping in Setup to explicitly map the Lead picklist field to the Opportunity picklist field.
In Salesforce, creating custom fields with identical names or picklist values on both the Lead and target objects (Account, Contact, or Opportunity) does not automatically transfer field values upon conversion. An administrator must explicitly map custom Lead fields to custom target object fields using the 'Map Lead Fields' tool in the Lead Object Manager. When correctly mapped to a compatible picklist field on the Opportunity object, the selected value transfers seamlessly during conversion.

Step-by-Step Solution

1
Identify why custom field data did not transfer during lead conversion.
Recognize that creating custom fields with identical names and types on target objects does not automatically map them during lead conversion.
Salesforce requires explicit configuration to define data transfer between Lead custom fields and target object custom fields.
2
Navigate to Object Manager > Lead > Fields & Relationships > Map Lead Fields in Setup.
Access the custom field mapping interface for Account, Contact, and Opportunity target objects.
This is the native platform tool for linking custom lead fields to corresponding custom fields on converted records.
3
Map the 'Project Scope' Lead field to the 'Project Scope' Opportunity field.
Lead values in 'Project Scope' will now populate on the Opportunity upon lead conversion.
Custom fields must be of compatible data types (such as Picklist to Picklist) and explicitly mapped to transfer data.

Key Concept

Lead Custom Field Mapping
Question 894Question

Global Freight Logistics needs to establish a specialized case lifecycle for its Import Customs Compliance team to handle regulatory holds and duty payments, separately from its standard customer delivery issues. The administrator has already added the new status values ('Under Customs Audit' and 'Duty Pending') to the Case Status master picklist. Which step must the administrator complete next to ensure these specific status values are available on cases created for the Import Customs Compliance team?

Show answer & explanation

Answer: Create a new Support Process that includes the new status values, then assign that Support Process to a new Case Record Type.

Answer

Create a new Support Process that includes the new status values, then assign that Support Process to a new Case Record Type.
In Salesforce, Case Status values are driven by Support Processes. Before creating or updating a Case Record Type to use specialized status values, an administrator must create a Support Process containing those specific status values and then associate the Support Process with the Case Record Type.

Step-by-Step Solution

1
Identify the controlling mechanism for Case Status picklists.
Recognize that Case Status is controlled by a Support Process rather than direct Record Type picklist selection.
Salesforce requires a Support Process to define the lifecycle stages (status picklist values) for Case records.
2
Determine the administrative sequence for configuring Case lifecycles.
First create the Support Process containing the new status values, then create/associate the Case Record Type to that Support Process.
A Case Record Type cannot be saved without selecting an existing Support Process.

Key Concept

Support Process and Case Record Type Dependency
Question 895Question

A Salesforce Administrator is configuring a custom object record page in Lightning App Builder. The finance team requires that a specific field section containing sensitive billing metrics is displayed on the page only when the record status is set to 'Completed' and the viewing user holds the 'Finance Director' role. Furthermore, this section must be hidden entirely when viewed on mobile devices. Which configuration approach should the administrator use to satisfy these requirements?

Show answer & explanation

Answer: Upgrade the page to Dynamic Forms and configure component visibility filters on the Field Section component based on Record Status, User Role, and Device.

Answer

The administrator should upgrade the Lightning record page to Dynamic Forms and apply component visibility filters on the Field Section component using Record Status, User Role, and Device as filter criteria.
Upgrading the record page to Dynamic Forms in Lightning App Builder allows field sections to be placed as modular components. Administrators can configure visibility filters directly on the Field Section component using filter logic that checks record field values (Status = Completed), user profile/role details (Role = Finance Director), and device environment (Device = Desktop).

Step-by-Step Solution

1
Identify the Lightning App Builder features required for section-level control.
Dynamic Forms enables field sections to act as individual components on a Lightning record page.
Standard page layouts render record details as a single monolithic block without conditional component visibility.
2
Migrate the page layout details to Dynamic Forms using the page upgrade wizard in Lightning App Builder.
Fields and field sections become customizable Lightning components on the canvas.
Upgrading converts fields into independent elements that can accept visibility rules.
3
Add visibility filters to the specific Field Section component.
Filter set: Record > Status equals 'Completed', User > Role > Name equals 'Finance Director', and Device equals 'Desktop'.
Component visibility rules seamlessly evaluate record data, viewing user attributes, and device context simultaneously.

Key Concept

Dynamic Forms Component Visibility Rules
Question 896Question

A system administrator at Quantum Logistics is troubleshooting case automation issues for critical support inquiries. The business requirement dictates that when a case is submitted with Priority set to 'Urgent' and Account Tier set to 'Platinum', it must be immediately assigned to the 'Tier 3 Operations Queue'. Furthermore, if the case remains open for 2 hours during active business hours, an escalation action should reassign the case to the 'Executive Escalation Queue'.

During user acceptance testing, newly submitted cases meeting both criteria are being routed to the 'General Support Queue' (the organization's default owner) upon creation, and the 2-hour escalation action fails to execute.

Upon auditing the setup:
1. The active Case Assignment Rule has Entry 1 defined as Priority equals 'Urgent' (routing to General Support Queue), and Entry 2 defined as Priority equals 'Urgent' AND Account Tier equals 'Platinum' (routing to Tier 3 Operations Queue).
2. The active Case Escalation Rule entry specifies 'Age over 2 hours' based on Case Creation Time, but has no Business Hours specified, while the test case was created outside of standard organization business hours.

What combination of adjustments must the administrator make to resolve both the initial assignment failure and the escalation failure?

Show answer & explanation

Answer: Reorder the Case Assignment Rule entries so the multi-criteria Platinum entry evaluates first, and populate a valid Business Hours schedule on the Case Escalation Rule entry.

Answer

The administrator must reorder the Case Assignment Rule entries so the multi-criteria Platinum entry evaluates first, and populate a valid Business Hours schedule on the Case Escalation Rule entry.
Case Assignment Rules evaluate rule entries sequentially from top to bottom according to their sort order. When a record matches a rule entry, Salesforce applies the assignment action for that entry and halts further rule entry processing. Consequently, rule entries with specific multi-field criteria must be positioned before broader criteria. In addition, Case Escalation Rules calculate elapsed time based on specified Business Hours; assigning the correct Business Hours schedule to the escalation rule entry ensures the escalation clock counts active operational hours correctly.

Step-by-Step Solution

1
Analyze the Case Assignment Rule entry evaluation order.
Since Entry 1 only checks for Priority = Urgent, all urgent cases match Entry 1 immediately and stop further evaluation. Entry 2 is never reached.
Salesforce assignment rules evaluate entries sequentially by sort order and terminate evaluation upon the first successful match. Specific criteria must precede broader criteria.
2
Correct the Case Assignment Rule sort order.
Move the entry requiring both Priority = Urgent AND Account Tier = Platinum to Sort Order 1, and move the broader Priority = Urgent entry to Sort Order 2.
This guarantees that Platinum urgent cases match the specific entry first and route to the Tier 3 Operations Queue.
3
Evaluate the Escalation Rule Business Hours configuration.
Without business hours assigned to the escalation rule entry or case, the escalation clock relies on default organization business hours. If submitted outside business hours, time calculation does not accumulate elapsed active hours as expected.
Escalation age calculation requires an explicit Business Hours setting on the escalation rule entry or case record to measure SLA thresholds accurately against working hours.

Key Concept

Case Automation Order of Evaluation & Rule Configuration Mechanics
Estimated Time:3m 0s
Question 897Question

A global cybersecurity firm, Meridian Shield, is expanding its operations to include a dedicated Managed Security Services division alongside its traditional Enterprise Hardware Sales team. The Managed Security Services team requires a streamlined sales pipeline with a specific subset of Opportunity Stages (Discovery, Technical Validation, Proposal, Closed Won, and Closed Lost) that differs from the Hardware team's pipeline. The System Administrator has already verified that all necessary Stage picklist values exist in the Opportunity object. Which sequence of administrative actions should the administrator complete to ensure the Managed Security Services sales team uses the correct stage progression?

Show answer & explanation

Answer: Create a new Sales Process, select the required Opportunity Stages for Managed Security Services, create a new Opportunity Record Type linked to this Sales Process, and assign the Record Type to the appropriate user profiles.

Answer

Create a new Sales Process to define the subset of Opportunity Stages, associate that Sales Process with a new Opportunity Record Type, and assign the Record Type to the relevant user profiles.
In Salesforce Core Administration, the Opportunity Stage field is uniquely tied to a Sales Process. To implement different stage progressions for distinct business units, an administrator must first create a Sales Process containing the desired subset of stages. Next, a Record Type must be created for the Opportunity object and linked to that Sales Process. Finally, the Record Type is assigned to the appropriate profiles or permission sets.

Step-by-Step Solution

1
Create a new Sales Process
Defines the specific lifecycle stages (Discovery, Technical Validation, Proposal, Closed Won, Closed Lost) and probabilities for the business unit.
Opportunity Stage values are unique picklists that cannot be filtered directly at the Record Type level without a Sales Process master structure.
2
Create a new Opportunity Record Type and select the newly created Sales Process
Links the custom Sales Process pipeline to the Record Type definition.
Record Types drive page layout assignment and picklist value availability, but for Opportunities, stage picklist options are determined by the assigned Sales Process.
3
Assign the new Record Type to User Profiles / Permission Sets
Grants the Managed Security Services sales team access to create and manage opportunities with the streamlined stage workflow.
Users must have access to the Record Type to select it upon record creation and view the corresponding sales process stage progression.

Key Concept

Sales Processes and Record Type Linkage
Question 898Question

Match each Salesforce Files feature to its corresponding sharing or functional requirement.

Click a left item, then click its matching right item

Items

Content Deliveries
Library Permissions
File Versioning
File Privacy on Records

Matches

Show answer & explanation

Answer

Content Deliveries matches generating a public URL with password and expiration controls; Library Permissions matches controlling user actions within a specific workspace folder; File Versioning matches maintaining document updates while preserving past iterations; File Privacy on Records matches restricting viewing of an attached file to only the owner and explicit collaborators.
Each feature corresponds to its primary Salesforce administration capability: Content Deliveries generate customizable external links; Library Permissions govern actions within libraries; File Versioning manages document iteration history; and File Privacy on Records restricts attached file visibility regardless of parent record access.

Step-by-Step Solution

1
Identify the feature designed for sharing files externally with tracking and security parameters.
Content Deliveries creates public web links with optional expiration dates and passwords.
Salesforce Content Deliveries converts files into tracking-enabled external links.
2
Determine how access is managed inside Content Libraries.
Library Permissions define member privileges such as Authoring, Administering, or Viewing.
Workspace permissions govern user capabilities within specific libraries independently of standard object records.
3
Analyze how updating document content works without creating duplicate file records.
File Versioning retains previous iterations while making the newest file version active.
Uploading new versions updates the underlying file asset across all linked records automatically.
4
Determine how to prevent users with record visibility from automatically accessing sensitive attached files.
File Privacy on Records restricts attached file visibility exclusively to the owner and designated collaborators.
The 'Private on Record' toggle overrides standard record-inherited file permissions.

Key Concept

Salesforce Files Management and Sharing Capabilities
Estimated Time:1m 0s
Question 899Question

A Salesforce administrator needs to configure a unique sales pipeline for a new subscription service division that requires a distinct sequence of opportunity stages. Which TWO administrative actions must the administrator complete to achieve this setup?

Select all that apply

Show answer & explanation

Answer: Create a new Sales Process to select the specific stage picklist values required for the pipeline.; Create an Opportunity Record Type and associate it with the newly created Sales Process.

Answer

To configure a custom opportunity sales pipeline, the administrator must create a Sales Process to select the required opportunity stages and create an Opportunity Record Type linked to that Sales Process.
Establishing a custom sales stage lifecycle on the Opportunity object requires two interdependent setup steps: creating a Sales Process to select the active stage picklist values, and creating an Opportunity Record Type that links to that Sales Process.

Step-by-Step Solution

1
Navigate to Setup and create a new Sales Process for the Opportunity object.
A curated set of Opportunity Stage picklist values is grouped into a named Sales Process.
Opportunity stage picklist values are business processes that must be defined within a Sales Process before assigning them to record types.
2
Create a new Opportunity Record Type and select the newly created Sales Process.
The Record Type enforces the specific stage lifecycle for opportunities created under it.
Opportunity Record Types require an associated Sales Process to determine which stage picklist values are available.

Key Concept

Sales Process and Record Type linkage for Opportunity Stages
Question 900Question

A Salesforce administrator at a digital media agency is configuring the organization's data model and evaluating management rules for standard versus custom objects. Which two statements correctly describe the capabilities and characteristics of standard and custom objects in Salesforce? (Select 2)

Select all that apply

Show answer & explanation

Answer: Standard objects provided by Salesforce cannot be deleted, whereas custom objects created by administrators can be deleted if no dependent components exist.; Standard fields automatically created on custom objects, such as Created By, Last Modified By, and Owner, cannot be deleted by an administrator.

Answer

Standard objects provided by Salesforce cannot be deleted while custom objects can be deleted if free of dependencies, and standard system fields created on custom objects cannot be deleted by an administrator.
Standard objects delivered by Salesforce are permanent core schema components that cannot be deleted from an organization, whereas custom objects can be removed via Object Manager when no hard dependencies exist. Additionally, standard fields that Salesforce automatically attaches to custom objects (such as Created By, Last Modified By, and Owner) are required for platform auditability and cannot be deleted by administrators.

Step-by-Step Solution

1
Analyze object deletion rules for standard versus custom objects.
Standard objects are permanent platform components and cannot be deleted. Custom objects can be deleted when no dependent metadata or code references exist.
Differentiating object lifecycle boundaries ensures administrators understand object modification capabilities.
2
Evaluate standard field restrictions on custom objects.
System audit fields like Created By, Last Modified By, and Owner are created automatically on custom objects and cannot be deleted.
Salesforce mandates standard system fields for tracking record ownership and system governance.
3
Analyze relationship capabilities for roll-ups and record deletion.
Roll-up summary fields require a Master-Detail relationship, and cascading deletion happens under Master-Detail relationships, not default Lookup relationships.
Understanding the functional boundaries between Lookup and Master-Detail relationships prevents data model misconfigurations.

Key Concept

Standard and Custom Object Management Rules and Field Limitations
PreviousPage 45 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin