All practice questions

1784 questions

Question 861Question

An administrator at Universal Containers wants to enhance sales representative efficiency in the Lightning Sales Console by giving reps quick access to recent items and automated routine actions directly from the console footer bar. Which two productivity tools should the administrator add to the Lightning App Utility Bar? (Select two.)

Select all that apply

Show answer & explanation

Answer: History utility component to allow reps to quickly view and reopen recently visited records and workspace tabs; Macros utility component to enable reps to perform repetitive multi-step tasks with a single click

Answer

The administrator should add the History utility component and the Macros utility component to the Lightning App Utility Bar.
The History utility component and Macros utility component are standard Lightning tools configured within the Utility Bar. The History component allows reps to rapidly navigate back to recently viewed records and subtabs, while the Macros component lets users execute multi-step automated field updates and routine actions.

Step-by-Step Solution

1
Analyze business requirements
The sales team needs direct access to recent records and automation for common repetitive actions from the console footer.
The Utility Bar in Lightning Experience provides persistent access to common productivity tools.
2
Identify matching standard Utility Bar items
The History component provides recent record/tab navigation, and the Macros component automates multi-step field updates and communications.
Both items are standard Lightning utility components designed for sales productivity.

Key Concept

Lightning Sales Console Utility Bar Configuration
Question 862Question

A Salesforce Administrator needs to manually provision a new sales manager account, ensuring appropriate data security, record sharing, and feature access are in place before allowing system entry. Place the standard administrative steps for user provisioning in the correct logical sequence from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence to provision a user is: 1) Create the User record with License and Profile, 2) Assign the Role in the Role Hierarchy, 3) Assign Permission Sets or Permission Set Groups, and 4) Send the account activation email.
The standard operational workflow requires establishing identity and core access controls (User License and Profile) first. Next, the user is integrated into data access models (Role Hierarchy), followed by granting modular permissions (Permission Sets). Finally, notification credentials (Activation Email) are dispatched once access configuration is complete.

Step-by-Step Solution

1
Create user record with core attributes
User account exists with enforced system boundaries set by License and Profile.
Every Salesforce user record requires a valid license and profile upon creation.
2
Set data access context via Role Hierarchy
User is placed into the sharing model for record visibility.
Role assignment governs vertical record access and management reporting lines.
3
Grant flexible permissions via Permission Sets
User receives targeted extra permissions without modifying baseline profiles.
Best practices dictate keeping profiles minimal and extending rights via Permission Sets.
4
Dispatch activation email
User receives login setup instructions.
Sending login links after complete configuration ensures proper security controls are active when the user logs in for the first time.

Key Concept

User Provisioning Lifecycle Sequence
Question 863Question

A Salesforce Administrator at a commercial real estate franchise company needs to display the sum of annual revenue from all active branch offices on the parent Franchise Account record. Currently, the custom object Branch Office is connected to the standard Account object via a Lookup relationship. When attempting to create a new field on the Account object to aggregate this revenue, the administrator notices that the Roll-Up Summary field type is disabled. Which configuration change must the administrator make to satisfy this requirement?

Show answer & explanation

Answer: Convert the existing Lookup relationship field on Branch Office to a Master-Detail relationship, then create a Roll-Up Summary field using the SUM function on the Account object.

Answer

Convert the existing Lookup relationship field on Branch Office to a Master-Detail relationship, then create a Roll-Up Summary field using the SUM function on the Account object.
In Salesforce, Roll-Up Summary fields calculate values from related child records, but they can only be created on the master object in a Master-Detail relationship. Converting the Lookup relationship on the custom child object to a Master-Detail relationship allows the administrator to create a declarative Roll-Up Summary field using the SUM aggregate operation.

Step-by-Step Solution

1
Identify relationship capabilities and limitations
Recognize that native Roll-Up Summary fields are only supported on the parent side of a Master-Detail relationship.
Lookup relationships do not support native Roll-Up Summary fields out-of-the-box.
2
Change relationship type
Convert the custom Lookup field on Branch Office to a Master-Detail relationship (ensuring all child records have a populated parent lookup value first).
Master-Detail relationship is required before a Roll-Up Summary field can be defined on the parent object.
3
Create Roll-Up Summary field
Build a Roll-Up Summary field on the Account object selecting the SUM operation on the Branch Office revenue field.
This automatically calculates and displays the aggregate sum of revenue across all child records on the parent record.

Key Concept

Roll-Up Summary Field Relationship Requirements
Question 864Question

An administrator is configuring the Salesforce Lightning Sales Console and productivity tools to optimize sales representative efficiency. Match each business requirement to the appropriate Salesforce sales productivity feature or console component.

Click a left item, then click its matching right item

Items

Sales representatives need to perform repetitive, multi-step actions (such as sending a specific email template and updating field values) on record pages with a single click.
Inside sales representatives need persistent, dockable access to quick tools like softphone dialers, notes, and recent items across all console workspace tabs.
Sales reps working through a high volume of leads need to view the target record details alongside the working list view without losing context or navigating back and forth.
The sales team requires automated background logging and synchronization of Microsoft Outlook/Gmail emails and calendar events directly to related Salesforce records.

Matches

Show answer & explanation

Answer

Matching pairs: 1) Repetitive multi-step actions -> Macros; 2) Persistent docked quick tools -> Utility Bar; 3) Side-by-side list and record view -> Split View; 4) Automatic email/event sync -> Einstein Activity Capture.
Each feature directly maps to the corresponding productivity objective: Macros automate multi-step UI tasks; the Utility Bar provides docked component access; Split View allows side-by-side list and record navigation in the Sales Console; and Einstein Activity Capture automates background email and calendar sync.

Step-by-Step Solution

1
Analyze requirement 1 regarding automating multi-step record updates.
Identify Macros as the feature designed to automate repetitive task sequences on supported Salesforce objects.
Macros save time by executing pre-scripted updates, field changes, and email dispatches in one user action.
2
Analyze requirement 2 regarding persistent dockable tools at the bottom of the screen.
Identify Utility Bar as the persistent footer layout component in Lightning apps.
The Utility Bar stays docked across navigation, enabling quick access to tools like softphones and notes.
3
Analyze requirement 3 regarding simultaneous viewing of list views and individual record details.
Identify Split View as the console navigation mode designed for high-density record processing.
Split View keeps the list view pinned to the side of the active record workspace.
4
Analyze requirement 4 regarding hands-free background synchronization of external email and calendar events.
Identify Einstein Activity Capture as the automated synchronization solution for Google and Microsoft suites.
Einstein Activity Capture eliminates manual logging by connecting server-side calendar and email feeds to Salesforce timelines.

Key Concept

Salesforce Sales Console Components and Sales Productivity Tools
Question 865Question

A Salesforce Administrator needs to implement several user interface enhancements for different business operational teams. Match each specific business requirement with the most appropriate action, custom button, or custom link solution.

Click a left item, then click its matching right item

Items

Launch an external third-party invoicing website from an Account record page while dynamically passing the record's custom Tax ID as a query string parameter.
Allow support agents working on a Case record page to create a pre-populated child Case record linked automatically to the current parent Case.
Enable sales reps to quickly create a new Lead record from any page or global utility bar in Lightning Experience without requiring a parent record relationship.
Provide a streamlined UI component on a Contact record page to modify specific fields on the current Contact record using a dedicated, customized layout.

Matches

Show answer & explanation

Answer

The business requirements match as follows: launching an external URL with record parameters matches Custom Detail Page Link (URL Type); creating a related child record in context matches Object-Specific Quick Action (Create a Record); creating a record globally from anywhere matches Global Quick Action (Create a Record); and modifying fields on the current record via custom action layout matches Object-Specific Quick Action (Update a Record).
Each requirement maps to its corresponding tool based on scope and action type: URL custom links pass merge parameters to external endpoints; Object-Specific Create Actions create child records in host context; Global Quick Actions allow independent creation from any page; and Object-Specific Update Actions provide tailored field layouts for editing current record data.

Step-by-Step Solution

1
Analyze requirement 1 (External URL integration with field parameter)
Identified as requiring URL merge fields on a record page.
Custom Links (or Buttons) of URL type can embed merge fields to pass dynamic record context to external web applications.
2
Analyze requirement 2 (Context-aware record creation linked to host record)
Identified as requiring parent record context.
Object-Specific Create Record Quick Actions execute in host object context, automatically populating lookup/master-detail fields to the host record.
3
Analyze requirement 3 (Global record creation without host record context)
Identified as requiring global availability.
Global Quick Actions can be placed on global publisher layouts for independent record creation from anywhere in Salesforce.
4
Analyze requirement 4 (Updating host record fields via custom action layout)
Identified as requiring field update layout customization on the host object.
Object-Specific Update Record Quick Actions expose a customized action layout to update specific fields on the target record.

Key Concept

Selecting appropriate Salesforce user interface customization mechanisms based on contextual relationship scope, navigation requirements, and record manipulation types.
Question 866Question

A System Administrator at Nexus Biomedical needs to configure a custom sales pipeline for a new Medical Devices division. Place the administrative steps required to configure this new pipeline in the correct execution order, from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of administrative steps is: 1) Add required custom stage values to the Opportunity Stage picklist field. 2) Create a new Sales Process and select the applicable Opportunity Stages. 3) Create an Opportunity Record Type and associate it with the new Sales Process. 4) Assign the new Opportunity Record Type to the Medical Devices sales team's profiles.
Configuring a new sales pipeline follows a strict dependency order in Salesforce: first, the necessary stage values must be added to the Opportunity Stage picklist field; second, a Sales Process is created to select and map those specific stages; third, an Opportunity Record Type is created and linked to the Sales Process; finally, access to the new Record Type is assigned to the target user profiles.

Step-by-Step Solution

1
Create custom stage values on the Opportunity object.
The Opportunity Stage picklist field includes all new values required by the division.
A Sales Process cannot reference picklist values that do not yet exist on the Opportunity object.
2
Create the custom Sales Process.
A named Sales Process is created containing the selected subset of Opportunity Stages.
Sales Processes define the specific stage progression for a business lifecycle.
3
Create the Opportunity Record Type.
An Opportunity Record Type is linked directly to the newly created Sales Process.
Opportunity Record Types require an existing Sales Process to govern stage picklist display.
4
Assign the Record Type to user profiles.
Target users gain access to create and manage records using the new pipeline.
Users cannot view or select a record type until it is assigned to their profile or permission set.

Key Concept

Sales Process and Record Type setup sequence
Question 867Question

A Salesforce Administrator at a manufacturing company is designing a custom data model to link Equipment (`Equipment__c`) with Inspection Routines (`Inspection_Routine__c`). Each inspection routine MUST be associated with a single equipment record, and deleting an equipment record must automatically remove all of its associated inspection routines. Additionally, executives require a live count of all completed inspection routines displayed directly on the equipment record page without using custom code. Which data model architecture should the administrator implement to meet these requirements?

Show answer & explanation

Answer: Create a Master-Detail relationship on Inspection Routine referencing Equipment, and create a Roll-Up Summary field on Equipment to aggregate completed routines.

Answer

The administrator should create a Master-Detail relationship on Inspection Routine referencing Equipment and add a Roll-Up Summary field on Equipment to aggregate the completed routines.
Creating a Master-Detail relationship field on the Inspection Routine child object satisfies both business requirements: deleting an Equipment record automatically cascades deletion to all related Inspection Routine records, and it allows the creation of a standard Roll-Up Summary field on the Equipment master object to aggregate completed routines.

Step-by-Step Solution

1
Analyze deletion and parentage requirements
Since deleting an Equipment record must cascade and delete all associated Inspection Routine records, a Master-Detail relationship is required.
Lookup relationships do not support native cascade deletion of child records in standard custom object configurations without additional automation.
2
Evaluate aggregation requirement
A Roll-Up Summary field on Equipment will count or calculate child Inspection Routine data natively.
Roll-Up Summary fields are exclusively available on the master object in a Master-Detail relationship.

Key Concept

Master-Detail Relationship Capabilities and Roll-Up Summary Fields
Question 868Question

An administrator at Northern Trail Outfitters needs to enable cross-functional support specialists to collaborate on specific, high-priority customer cases. The requirements state that these specialists must be granted explicit record-level access (such as Read Only or Read/Write) based on their functional role on the case, without transferring case ownership or modifying Organization-Wide Defaults. Which feature should the administrator configure to satisfy this business requirement?

Show answer & explanation

Answer: Predefined Case Teams with customized Case Team Roles

Answer

The administrator should configure Predefined Case Teams with customized Case Team Roles.
Predefined Case Teams and Case Team Roles allow administrators to designate access levels (Read Only or Read/Write) for users collaborating on specific case records. This directly addresses the requirement to grant explicit access to cross-functional members without altering Organization-Wide Defaults or changing case ownership.

Step-by-Step Solution

1
Analyze the requirement for record-level collaboration
Identified that specific users require individual case record access (Read Only or Read/Write) without altering case ownership or global OWD settings.
Case collaboration across functional groups requires flexible record sharing mechanisms.
2
Evaluate Salesforce Service Cloud collaboration tools
Case Teams enable administrators to define roles with explicit access levels and assemble predefined teams of users for quick assignment to cases.
Case Teams directly fulfill the requirement of role-based record sharing per case.

Key Concept

Case Teams and Case Team Roles
Question 869Question

A freight management company uses a custom object named Maintenance_Log__c to record vehicle maintenance events. The Organization-Wide Default (OWD) for Maintenance_Log__c is set to Private. Regional maintenance managers need to view and edit all maintenance logs created by technicians who are assigned to roles below them in the Role Hierarchy. However, managers report that they are unable to see records owned by technicians below them.

Which configuration setting should the Salesforce Administrator check first to resolve this issue?

Show answer & explanation

Answer: Verify that the 'Grant Access Using Hierarchies' checkbox is enabled for the Maintenance_Log__c custom object.

Answer

Verify that the 'Grant Access Using Hierarchies' checkbox is enabled for the Maintenance_Log__c custom object.
For custom objects, Salesforce provides the 'Grant Access Using Hierarchies' checkbox in Object Manager. While enabled by default, an administrator can uncheck it. When unchecked, users in higher roles do not gain implicit access to records owned by users in lower roles. Verifying and re-enabling this setting directly addresses the issue without requiring unnecessary sharing rules or over-privileged system permissions.

Step-by-Step Solution

1
Analyze the access requirement
Users in roles above record owners in the Role Hierarchy need automatic access to Private custom object records.
By default, Salesforce standard objects always grant access using hierarchies, but custom objects allow this feature to be toggled on or off.
2
Identify the cause of missing hierarchy access
If 'Grant Access Using Hierarchies' is unchecked on a custom object, access does not flow upward through the Role Hierarchy.
Checking this setting restores the standard behavior where role hierarchy grants access based on record ownership by subordinates.

Key Concept

Grant Access Using Hierarchies for Custom Objects
Question 870Question

A sales operations administrator at a cloud-based software subscription provider is documenting the standard lead conversion process for internal training. Arrange the following actions in the exact chronological order in which they occur during the standard Salesforce lead conversion execution lifecycle.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological order begins with user initiation and destination record configuration, followed by target record generation with custom field mapping, then updating the lead status to converted with relationship linking, and concluding with activity history transfer and record locking.
Standard Salesforce lead conversion executes in a defined workflow: initiation and target selection occurs first, followed by target record creation and custom field mapping execution, then updating lead status flag (IsConverted = True) with object lookup references, and finally transferring activity history and locking the lead record from standard edits.

Step-by-Step Solution

1
User Conversion Request
Lead conversion dialog opens where the user selects destination Account, Contact, and Opportunity settings.
The process must be initiated by user action or automated flow specifying conversion targets.
2
Record Creation & Custom Field Mapping
Target Account, Contact, and Opportunity records are created or updated using data mapped from custom lead fields.
Target entities must be instantiated and validated before the lead record can be linked to them.
3
Lead Status Transition & Lookup Assignment
The Lead IsConverted boolean flag is set to True, and ConvertedAccountId, ConvertedContactId, and ConvertedOpportunityId fields are populated.
The system formally transitions the lead status and records relational linkages to the new entities.
4
Related Item Relocation & Record Read-Only Locking
Activities, tasks, and notes are reassigned to the Account/Contact/Opportunity, and the converted Lead record becomes read-only.
Converted leads are preserved for conversion analytics and reporting while preventing further modification.

Key Concept

Salesforce Lead Conversion System Execution Order
Question 871Question

A Salesforce Administrator at NovaScale Cloud Infrastructure creates a new product record for a cloud storage solution and marks the record as Active. The administrator needs to make this product available to sales representatives using a custom price book titled 'Federal Public Sector'. However, the administrator is unable to select or add the product to the custom price book. Which action must the administrator take first to resolve this issue?

Show answer & explanation

Answer: Create an active list price entry for the product in the Standard Price Book.

Answer

Create an active list price entry for the product in the Standard Price Book.
In Salesforce, the Standard Price Book acts as the base pricing reference. A product cannot be added to any custom price book until an active price entry exists for that product in the Standard Price Book.

Step-by-Step Solution

1
Identify the prerequisite for adding products to custom price books in Salesforce.
Salesforce architecture requires every product to have an active price in the Standard Price Book before entry into any custom price book.
The Standard Price Book serves as the master catalog and baseline price reference for all products.
2
Create a Standard Price Book entry for the new product record.
The product now possesses an active standard price.
Once the standard price is established and active, Salesforce unlocks the ability to add the product to custom price books.
3
Add the product to the 'Federal Public Sector' custom price book with a custom list price.
Sales representatives can now select the product on opportunities associated with the custom price book.
The system validation rule requiring a standard price entry is satisfied.

Key Concept

Standard Price Book Entry Prerequisite
Question 872Question

A Salesforce Administrator is configuring Service Cloud for a hospital network with distinct case management workflows for Patient Intake, Billing Disputes, and Medical Device Maintenance. Match each Salesforce administrative component on the left to its correct functional role in governing case lifecycles and record interfaces on the right.

Click a left item, then click its matching right item

Items

Support Process
Case Record Type
Page Layout
Case Status Master Field

Matches

Show answer & explanation

Answer

Support Process matches the definition of filtering Case Status picklist values for a business unit; Case Record Type matches linking the business process to page layouts and non-Status picklists; Page Layout matches governing UI structure, fields, and related lists; Case Status Master Field matches holding the full repository of all status values across the Case object.
The matches correctly distinguish the architectural dependencies in Service Cloud setup: Support Processes filter Case Status picklist values for specific business lifecycles; Record Types tie these Support Processes to Page Layouts and non-status picklist sets; Page Layouts control visual UI design; and the Master Field stores all available status choices.

Step-by-Step Solution

1
Identify the role of Support Process in Salesforce case administration.
Recognize that Support Processes directly govern Case Status picklist value subsets for unique business lifecycles.
Case Status cannot be filtered directly at the Record Type level without a Support Process prerequisite.
2
Differentiate Record Type capabilities from Support Process capabilities.
Map Case Record Type to assigning Support Processes, assigning Page Layouts, and controlling non-Status picklist fields.
Record Types handle overall record behavior and UI associations, relying on Support Process for Case Status selection.
3
Distinguish Page Layout functions from object-level field definitions.
Associate Page Layout with structural UI elements (field positioning, sections, related lists).
Page Layouts control visual arrangement on record pages rather than business lifecycle logic.
4
Define the relationship between the Master Case Status field and Support Processes.
Connect Case Status Master Field to the baseline set of all defined statuses on the Case object.
New Case Status values must first be added to the master picklist field before they can be selected within any Support Process.

Key Concept

Support Process and Record Type Dependencies
Question 873Question

A sales manager wants inside sales representatives to stay focused on main account contexts while working in the Lightning Sales Console. When a representative opens a child Opportunity from an Account record page, the manager wants the Opportunity record to open automatically as a subtab under the parent Account primary tab rather than as a new main tab. Which configuration in Salesforce satisfies this requirement?

Show answer & explanation

Answer: Configure Navigation Rules for the Sales Console application in the App Manager.

Answer

Configure Navigation Rules for the Sales Console application in the App Manager.
Configuring Navigation Rules in the App Manager for the Lightning Sales Console enables administrators to define how records open, ensuring child records like Opportunities open as subtabs of primary records like Accounts.

Step-by-Step Solution

1
Identify the user interface requirement in the Lightning Sales Console.
The requirement is to open child records (Opportunities) as subtabs under parent primary tabs (Accounts).
Console workspace navigation relies on primary tab and subtab relationships to keep user workflows organized.
2
Select the appropriate administrative feature for tab behavior in console apps.
Navigation Rules in the App Manager control workspace tab routing rules.
Setting navigation rules for the console app determines whether related objects open as primary workspace tabs or nested subtabs.

Key Concept

Lightning Sales Console Navigation Rules and Workspace Tab Management
Question 874Question

A Salesforce administrator at a telecommunications provider is configuring a custom object named Service Audit to track quality evaluations associated with standard Account records. The business requirement dictates that deleting an Account record must automatically delete all associated Service Audit records, and administrators must be able to create a roll-up summary field on the Account object to count total evaluations. Which relationship configuration on the Service Audit object meets these requirements?

Show answer & explanation

Answer: Create a Master-Detail relationship field on the Service Audit object referencing the Account object.

Answer

Create a Master-Detail relationship field on the Service Audit object referencing the Account object.
Defining a Master-Detail relationship on the custom Service Audit object pointing to the standard Account object allows Account to act as the master. This automatically deletes child Service Audit records whenever their parent Account is deleted, and enables administrators to create Roll-Up Summary fields directly on the Account object.

Step-by-Step Solution

1
Analyze the requirements for data behavior between Account (standard object) and Service Audit (custom object).
The scenario requires cascading record deletion (deleting master deletes detail) and roll-up summary capability on the parent object.
Master-Detail relationships provide native cascade delete functionality and support Roll-Up Summary fields on the master object.
2
Determine object relationship constraints between standard and custom objects.
Standard objects can act as the Master object, while custom objects can serve as the Detail object.
Salesforce architecture prevents standard objects from being on the detail child side of a Master-Detail relationship.
3
Select the correct field location and relationship type.
Creating the Master-Detail field on the child custom object (Service Audit) pointing to the parent standard object (Account) fulfills all requirements.
Relationship custom fields are always defined on the child/detail object pointing to the parent/master object.

Key Concept

Standard and Custom Object Master-Detail Relationships and Capabilities
Question 875Question

A medical device company is introducing a specialized Consulting Services division alongside its existing Equipment Sales team. The Consulting Services division follows a streamlined sales pipeline with unique stage names, specific win probabilities, and distinct required fields that differ significantly from Equipment Sales. Which TWO administrative configuration steps must the administrator execute to ensure Consulting Services sales representatives only encounter their division's specific opportunity stages when creating and managing deals? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Create a custom Sales Process that selects only the Opportunity Stage picklist values designated for the Consulting Services pipeline.; Create a custom Opportunity Record Type, associate it with the new Sales Process, and grant profile access to the Consulting Services team.

Answer

The administrator must create a custom Sales Process containing the specific opportunity stages, then create an Opportunity Record Type linked to that Sales Process and assign it to the appropriate user profiles.
Configuring distinct opportunity stages for different business units requires two primary components: creating a custom Sales Process to select the relevant stage picklist values, and creating an Opportunity Record Type linked to that Sales Process which is then assigned to user profiles.

Step-by-Step Solution

1
Define and create a new Sales Process
Filters the master list of Opportunity stages into a curated subset tailored specifically to the Consulting Services sales pipeline.
Opportunity stage picklist values are controlled exclusively through Sales Processes rather than standard record type picklist selection.
2
Create an Opportunity Record Type and link the Sales Process
Associates the curated Sales Process with the appropriate Opportunity page layout.
Record Types serve as the bridge between Sales Processes, page layouts, and user profile visibility.
3
Assign the Record Type to user profiles
Ensures Consulting Services representatives default to or select the proper record type when creating opportunities.
Profile assignment determines which record types are visible and selectable for end users.

Key Concept

Opportunity Stage management via Sales Processes and Record Types
Question 876Question

Universal Containers needs to establish two distinct business support channels: Premier Managed Support and Standard Operations. Premier Managed Support requires a customized lifecycle with specialized Case Status values ('In Triage', 'Vendor Escalation', and 'Pending Sign-off') that should not be visible to Standard Operations users. Additionally, Premier Managed Support requires a tailored page layout and specific choices for the Case Reason picklist. Which TWO administrative actions must be completed to satisfy these requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a custom Support Process for Premier Managed Support to define its distinct Case Status picklist lifecycle prior to creating the associated record type.; Create a Case Record Type for Premier Managed Support, associate it with the new Support Process, and configure the Case Reason picklist values and page layout assignment for that record type.

Answer

The correct configuration steps are to create a custom Support Process defining the specific Case Status values prior to record type creation, and then create a Case Record Type linked to that Support Process while configuring page layout assignments and Case Reason picklist options.
On the Case object, Case Status picklist values are governed strictly by Support Processes. To implement distinct status lifecycles across different business groups, an administrator must first build a custom Support Process containing the required status values. Afterward, a Case Record Type must be created to link that Support Process, assign the appropriate Page Layout, and filter non-status picklists such as Case Reason.

Step-by-Step Solution

1
Identify the dependency mechanism for Case Status values.
Recognize that Case Status is a special picklist field whose values are controlled by Support Processes, not directly by Record Types or Page Layouts alone.
Salesforce mandates creating a Support Process before assigning custom status lifecycles to Case Record Types.
2
Create the custom Support Process.
A Support Process containing 'In Triage', 'Vendor Escalation', and 'Pending Sign-off' is established.
This establishes the lifecycle baseline required for Premier Managed Support.
3
Create and configure the Case Record Type.
Associate the newly created Support Process with a new Case Record Type, assign the Premier page layout, and edit the Case Reason picklist values specifically for this Record Type.
Record Types bridge the Support Process lifecycle with Page Layout assignments and non-status picklist availability.

Key Concept

Support Process and Record Type prerequisites for the Case object
Question 877Question

Universal Containers is implementing a specialized Product Returns handling workflow alongside its existing Customer Support operations. The Product Returns team requires a custom lifecycle with a specific subset of Case Status picklist values. Which two configuration steps must the administrator complete to successfully implement this requirement? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a new Support Process that selects the appropriate Case Status picklist values.; Create a new Case Record Type and associate it with the custom Support Process.

Answer

To configure customized Case Status picklist values for a specific team, an administrator must create a custom Support Process containing the required status values, and then create a Case Record Type that references that Support Process.
Configuring customized Case Status values requires establishing a Support Process containing the desired status values and linking that Support Process to a newly created Case Record Type.

Step-by-Step Solution

1
Define the Case Status lifecycle using a Support Process.
A new Support Process is saved with the chosen subset of Case Status picklist values.
Case Status picklist values on the Case object are governed by Support Processes rather than standard record type picklist selection screens.
2
Create a Case Record Type.
The Record Type links the page layout, object picklists, and the selected Support Process together.
A Case Record Type cannot be saved without selecting an existing Support Process.

Key Concept

Support Process and Case Record Type Dependency
Question 878Question

When a new support case is created in Salesforce, several automation processes execute during record saving. Arrange the following automation rule types in the correct order in which Salesforce evaluates and executes them from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct order of execution is Validation Rules, followed by Case Assignment Rules, then Case Auto-Response Rules, and finally Case Escalation Rules.
In Salesforce's standard order of execution for case processing, Validation Rules evaluate first to ensure data integrity. Once validated, Case Assignment Rules execute to route and assign the case. Following assignment, Case Auto-Response Rules run to send automated customer communications. Finally, Case Escalation Rules evaluate to schedule SLA escalation actions.

Step-by-Step Solution

1
Identify the data verification stage
Validation Rules execute before automation rules to ensure data compliance.
Salesforce prevents invalid records from entering automated routing pipelines by running validation rules first.
2
Identify ownership routing
Case Assignment Rules execute next to establish record ownership.
Ownership must be assigned before auto-responses or escalation paths can correctly identify responsible users or queues.
3
Determine customer messaging
Case Auto-Response Rules execute after assignment rules.
Auto-response emails rely on case data and ownership information established during assignment.
4
Establish SLA tracking
Case Escalation Rules execute last among standard case automation rule types.
Escalation rules assess case status and age after assignment and customer response actions are established.

Key Concept

Salesforce Case Automation Rule Order of Execution
Question 879Question

Pinnacle Solar Energy recently added a custom field named Tax_Identification_Number__c to the Vendor custom object. Currently, the Field-Level Security setting for this field is set to hidden on the 'Standard Vendor User' profile assigned to all 50 operations staff members. The business requirement specifies that 8 compliance auditors within this group require read and edit access to Tax_Identification_Number__c, while the remaining 42 staff members must not be able to view or edit the field. What is the optimal security configuration to meet this requirement?

Show answer & explanation

Answer: Create a permission set with Read and Edit Field-Level Security enabled for Tax_Identification_Number__c and assign it to the 8 compliance auditors.

Answer

The optimal solution is to create a permission set that enables Read and Edit Field-Level Security for the Tax_Identification_Number__c field and assign that permission set to the 8 compliance auditors.
Salesforce security follows an additive permission model using Permission Sets. Setting the baseline Field-Level Security to restricted/hidden on the profile and assigning a Permission Set with Read and Edit access to the specific 8 compliance auditors ensures data security across all interfaces (UI, API, reports) while keeping profile administration simple.

Step-by-Step Solution

1
Analyze baseline access and user scope.
All 50 users share the 'Standard Vendor User' profile where the field is hidden by default.
Profiles set the baseline minimum access for users assigned to them.
2
Evaluate the mechanism for granting access to a subset of users.
Permission sets allow administrators to grant additional permissions (additive model) to targeted individual users.
Using permission sets avoids profile proliferation and maintains clean security management.
3
Select the correct security feature for data privacy.
Field-Level Security (FLS) controls field access across all entry points, including reports, search, API, and page layouts.
FLS guarantees true field-level data privacy across the entire platform.

Key Concept

Field-Level Security (FLS) and Permission Sets
Estimated Time:1m 0s
Question 880Question

An administrator at Northern Trail Outfitters needs to allow internal specialists to collaborate on specific customer cases by granting them explicit record access (such as Read Only or Read/Write) without altering default sharing settings. Additionally, the administrator wants team members to see real-time updates and posts regarding case changes. Which two configurations should the administrator implement to meet these collaboration requirements?

Select all that apply

Show answer & explanation

Answer: Define Case Team Roles with specific access levels and assign users to Case Teams on individual cases.; Enable Feed Tracking for the Case object so updates and field changes appear automatically in the Case Feed.

Answer

The correct configurations are defining Case Team Roles with explicit access levels and enabling Feed Tracking on the Case object.
Configuring Case Team Roles allows administrators to assign specific access levels (Read Only or Read/Write) to users on an individual case basis. Simultaneously, enabling Feed Tracking on the Case object guarantees that updates, record changes, and team comments are tracked directly in the Case Feed.

Step-by-Step Solution

1
Identify the requirement for granting ad-hoc case access to individual users.
Case Teams provide a mechanism to add users to specific cases with defined roles and access rights (Read Only or Read/Write).
Case Teams resolve the need for targeted record access without opening up organization-wide defaults or creating unnecessary profiles.
2
Identify the requirement for tracking activity and field updates within the case interface.
Enabling Feed Tracking on the Case object ensures changes to tracked fields and Chatter posts are displayed in the Case Feed.
Feed Tracking must be explicitly enabled on an object for record updates to generate automated feed posts.

Key Concept

Case Collaboration Tools (Case Teams and Case Feed Tracking)
PreviousPage 44 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin