All practice questions

1784 questions

Question 1021Question

A Salesforce Administrator needs to configure distinct Case lifecycles and Case Status picklist values for a company's Customer Support team and Field Service team. Which two setup steps must the administrator perform to achieve this configuration? (Select 2 answers.)

Select all that apply

Show answer & explanation

Answer: Create separate Support Processes to define the available Case Status values for each team.; Create separate Case Record Types and assign each to its corresponding Support Process.

Answer

Creating separate Support Processes to define allowed status values for each team, and creating separate Case Record Types linked to those Support Processes.
In Salesforce, the Case object uses Support Processes to define the lifecycle stage values available in the Case Status field. An administrator must first create the required Support Processes to select the valid Case Status picklist values for each workflow, and then create Case Record Types that reference those Support Processes.

Step-by-Step Solution

1
Create Support Processes
Defines distinct Case Status picklist lifecycles for Customer Support and Field Service.
Case Status values are tied directly to Support Processes rather than standard picklist record type configurations.
2
Create Case Record Types and Link Support Processes
Associates each Support Process and Page Layout with its dedicated Record Type.
Record Types provide the mechanism to deliver specific Support Processes and Page Layouts to target profiles.

Key Concept

Support Process Prerequisite for Case Record Types
Question 1022Question

A Support Administrator at a high-volume retail company is preparing for an annual promotional event. The company captures online support requests using standard Web-to-Case. On the day of the sale, incoming web form submissions dramatically spike and exceed the organization's maximum daily Web-to-Case limit. What happens to the customer submissions that are sent after the daily limit has been reached?

Show answer & explanation

Answer: The excess submissions are converted into email messages sent directly to the Default Case Owner specified in Support Settings.

Answer

The excess submissions are converted into email messages sent directly to the Default Case Owner specified in Support Settings.
When an organization reaches its 24-hour Web-to-Case limit, Salesforce does not drop the data or throw a web server error. Instead, it forwards an email containing the web form fields and customer details directly to the Default Case Owner defined in Support Settings so support managers can manually handle or process the request.

Step-by-Step Solution

1
Identify the Case capture mechanism and the operational boundary condition.
The scenario describes Web-to-Case reaching its maximum daily request limit during a traffic surge.
Salesforce enforces governor limits on Web-to-Case requests per 24-hour period based on organization edition.
2
Analyze standard Salesforce system behavior when Web-to-Case limits are exceeded.
Salesforce routes the submitted form data via email to the designated Default Case Owner listed in Support Settings.
This failover mechanism prevents data loss while protecting system resources from unthrottled record creation.

Key Concept

Web-to-Case Daily Limit Overflow Behavior
Question 1023Question

A Service Cloud administrator at a financial services firm is establishing automated case routing, customer notifications, and service level agreement (SLA) tracking for incoming Web-to-Case submissions. In what exact order does Salesforce process automation rules and evaluation steps when a new case is generated via Web-to-Case?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct evaluation order for case processing during Web-to-Case creation is: Validation Rules, Case Assignment Rules, Case Auto-Response Rules, Record-Triggered Flows / Workflow Rules, and Case Escalation Rules.
During case creation via Web-to-Case, Salesforce follows a specific order of execution. System and custom validation rules execute first to ensure data quality. Next, the active Case Assignment Rule sets the case owner (user or queue). Following assignment, the active Case Auto-Response Rule determines which email template to send to the submitter. Afterwards, Record-Triggered Flows and Workflow rules process. Finally, Case Escalation Rules are evaluated to set up time-based SLA escalation actions.

Step-by-Step Solution

1
Verify initial record data integrity.
Validation rules execute first to ensure valid field values.
Salesforce validates data before attempting ownership assignment or automated communication.
2
Assign initial ownership.
The active Case Assignment Rule assigns the case to a user or queue.
Ownership must be resolved before automated emails and subsequent workflow logic execute.
3
Trigger customer auto-response.
The active Case Auto-Response Rule sends a confirmation message to the contact.
Auto-response rules execute immediately following assignment rules.
4
Execute record automation logic.
Record-triggered Flows and Workflow rules execute updates and additional actions.
Custom processes and workflow rules process after initial standard case routing and auto-response logic.
5
Schedule SLA monitoring.
Case Escalation Rules evaluate and schedule escalation actions in the time-based queue.
Escalation rules run after main rule processing to monitor case resolution times against business hours.

Key Concept

Salesforce Order of Execution for Case Automation
Estimated Time:2m 0s
Question 1024Question

Summit Industrial Solutions tracks partner agreements using a custom object named Dealer_Agreement__c. The Organization-Wide Default (OWD) for Dealer_Agreement__c is set to Private. Security policies require that access to these records must NOT automatically propagate to users higher in the Role Hierarchy. Which administration setting should the System Administrator modify to meet this requirement?

Show answer & explanation

Answer: Deselect the 'Grant Access Using Hierarchies' checkbox for the Dealer_Agreement__c object in Sharing Settings.

Answer

Deselect the 'Grant Access Using Hierarchies' checkbox for the Dealer_Agreement__c custom object in Sharing Settings.
For custom objects, the 'Grant Access Using Hierarchies' option can be deselected in Sharing Settings. Unchecking this setting prevents record access from automatically propagating up the role hierarchy to managers while preserving OWD rules.

Step-by-Step Solution

1
Analyze how record access rolls up through the Salesforce Role Hierarchy.
By default, Salesforce enables 'Grant Access Using Hierarchies' for all objects, allowing users above record owners in the hierarchy to inherit record access.
Understanding the default security behavior helps identify the setting responsible for upward access propagation.
2
Identify options available for custom objects versus standard objects.
For custom objects, administrators can disable 'Grant Access Using Hierarchies' in Setup > Sharing Settings.
Disabling this setting stops managers from automatically inheriting access to custom object records owned by subordinates.

Key Concept

Disabling Grant Access Using Hierarchies for Custom Objects
Question 1025Question

A Salesforce Administrator at a global telecommunications company must immediately revoke system access for a departing regional operations director. However, when the administrator attempts to deactivate the user record, Salesforce prevents the action because the user is currently assigned as the Default Workflow User in the organization's Process Automation settings. What is the correct immediate action the administrator should take to secure the organization while resolving this dependency?

Show answer & explanation

Answer: Freeze the user account to instantly prevent login access, then reassign the Default Workflow User setting before deactivating the user record.

Answer

Freeze the user account to instantly prevent login access, then reassign the Default Workflow User setting before deactivating the user record.
Freezing a user account immediately blocks authentication into Salesforce without requiring immediate removal of system dependencies such as being designated as the Default Workflow User. Once frozen and secured, the administrator can reassign the Default Workflow User role to another active user and proceed with deactivating the account to release the Salesforce user license.

Step-by-Step Solution

1
Identify the immediate security requirement versus the system dependency constraint.
System access must be revoked immediately, but deactivation is blocked because the user is designated as the Default Workflow User.
Deactivating a user who is designated as a Default Workflow User or referenced in active hierarchy fields throws a system error.
2
Evaluate the difference between freezing and deactivating a user account.
Freezing halts login access immediately without breaking automated processes or requiring immediate dependency reassignment.
Freezing temporarily stops authentication while keeping the user license allocated and references intact.
3
Determine the proper administrative sequence.
Freeze the user account first to secure the environment, update Process Automation settings to point to another user, and then deactivate the user account to free up the license.
This two-step process satisfies both urgent security needs and system maintenance requirements.

Key Concept

User Freezing vs. User Deactivation
Question 1026Question

An administrator at a B2B SaaS company is setting up a new Campaign to track attendance for a technical workshop series. The marketing team requires that attendee responses be accurately recorded for reporting and that existing Lead campaign history is preserved on the Contact record upon lead conversion. Which two actions should the administrator take to fulfill these requirements? (Choose two.)

Select all that apply

Show answer & explanation

Answer: Add custom Campaign Member Status values on the Campaign record and mark engagement status values as 'Responded'.; Rely on standard Lead Conversion functionality to automatically associate existing Campaign Member records with the converted Contact.

Answer

The administrator should add custom Campaign Member Status values directly on the Campaign record and flag active engagement statuses as 'Responded', while relying on standard Lead Conversion to automatically retain campaign history on the converted Contact record.
Configuring custom Campaign Member Statuses on the Campaign record and checking the 'Responded' box enables precise reporting on attendee engagement. Additionally, standard Salesforce Lead Conversion automatically moves all existing Campaign Member history from the Lead to the converted Contact without extra field mapping.

Step-by-Step Solution

1
Configure Campaign Member Statuses on the Campaign record.
Custom status values (such as 'Attended') become available, and flagging them as 'Responded' ensures accurate campaign response roll-up summary reporting.
Campaign Member Status values are customized at the campaign level, and reporting metrics rely on the 'Responded' flag.
2
Perform standard lead conversion when converting campaign leads.
All Campaign Member records linked to the Lead are automatically relinked to the resulting Contact record.
Salesforce core architecture handles campaign history retention natively during lead conversion without custom field mapping.

Key Concept

Campaign Member Status Tracking and Lead Conversion Behavior
Question 1027Question

An administrator at an industrial robotics enterprise is configuring Salesforce Knowledge for a newly onboarded tier-1 customer support team. The support agents need to search and view published troubleshooting articles. The administrator has already verified that the support agents have the 'Knowledge User' feature license enabled on their user records and 'Read' permission on the Knowledge object in their assigned profile. However, when agents search for published articles categorized under the 'Robotic Arm Maintenance' category, no articles appear in their search results. Which administrative action will resolve this access issue?

Show answer & explanation

Answer: Configure the Data Category Visibility settings for the agents' profile or role to grant access to the 'Robotic Arm Maintenance' category group.

Answer

Configure the Data Category Visibility settings for the agents' profile, permission set, or user role to grant access to the 'Robotic Arm Maintenance' category group.
In Salesforce Knowledge, visibility into published articles depends heavily on Data Category Groups. Even when users possess the 'Knowledge User' license and 'Read' permissions on the Knowledge object, they cannot search for or view published articles unless their User Role, Profile, or assigned Permission Set grants explicit Data Category Visibility to the relevant category group.

Step-by-Step Solution

1
Identify the cause of the missing article search results
Recognize that despite having 'Read' object permissions and a 'Knowledge User' license, articles categorized under specific data category groups remain hidden if data category visibility is restricted or set to 'None'.
Salesforce Knowledge uses Data Category Visibility to filter article access independently of object permissions.
2
Determine the appropriate configuration location for Data Category Visibility
Navigate to Setup and adjust Data Category Visibility settings on the support agents' Role, Profile, or Permission Set.
Visibility can be configured broadly by Role Hierarchy or mapped specifically through Profiles and Permission Sets to grant 'All Categories', 'Custom', or specific category branches.
3
Grant access to the required Data Category branch
Set visibility for the target category group ('Robotic Arm Maintenance') to include the necessary child categories.
This allows support agents to query, search, and view all published articles classified within that category branch.

Key Concept

Data Category Visibility in Salesforce Knowledge
Question 1028Question

An administrator at Cloud Kicks is configuring Chatter Feed Tracking for a custom object named Work_Order__c to track operational changes. The department manager wants to ensure that critical field changes are automatically posted to the record feed. Which rule or limitation must the administrator keep in mind when enabling Chatter Feed Tracking on this object?

Show answer & explanation

Answer: A maximum of 20 fields per object can be selected for Feed Tracking.

Answer

A maximum of 20 fields per object can be selected for Feed Tracking.
When configuring Chatter Feed Tracking for standard or custom objects, Salesforce limits tracking to a maximum of 20 fields per object. Changes to any of the selected 20 fields will automatically create a system-generated post in the record's Chatter feed.

Step-by-Step Solution

1
Identify the Chatter Feed Tracking configuration limits in Salesforce.
Salesforce enforces a strict ceiling of 20 fields per object for Feed Tracking.
Understanding administrative boundaries ensures effective design of record feed monitoring.
2
Evaluate the requirement against object setup rules.
The administrator must select up to 20 key fields on Work_Order__c to track updates in Chatter.
Selecting more than 20 fields is not permitted by the setup interface.

Key Concept

Chatter Feed Tracking Limits and Field Selection
Question 1029Question

An organization reaches its maximum daily submission limit for Web-to-Case during a high-volume product promotion. What happens to additional cases submitted through the web form after this daily limit is reached?

Show answer & explanation

Answer: The submitted case details are emailed directly to the default case owner specified in the Web-to-Case settings.

Answer

The submitted case details are emailed directly to the default case owner specified in the Web-to-Case settings.
When an organization exceeds its maximum daily limit for Web-to-Case requests, Salesforce forwards the submitted case details in an email to the default case owner designated in the Web-to-Case setup.

Step-by-Step Solution

1
Identify system behavior when Web-to-Case daily limits are hit.
Salesforce enforces standard daily limits on the total number of cases generated via Web-to-Case.
Governor limits ensure platform resource stability while providing fallback mechanisms.
2
Determine the fallback handling mechanism for excess cases.
Overflow submissions bypass automatic record creation and are sent via email to the configured default case owner.
This guarantees that customer inquiry data is captured and delivered even during usage spikes.

Key Concept

Web-to-Case Limit Fallback Routing
Estimated Time:1m 0s
Question 1030Question

An administrator is enhancing the Lightning record page for a custom Incident Report object using Dynamic Forms and Dynamic Actions. The business team requires that the 'Root Cause Analysis' field section appears only when the incident status is set to 'Closed', and the 'Escalate Incident' action appears only for users assigned the 'Tier 3 Handler' custom permission. Which TWO configurations in Lightning App Builder will achieve these requirements? (Choose two.)

Select all that apply

Show answer & explanation

Answer: Add a component visibility filter to the 'Root Cause Analysis' Field Section component where Status equals 'Closed'.; Add an action visibility filter to the 'Escalate Incident' quick action using User > Permission > Custom Permission criteria.

Answer

The administrator should set a component visibility rule on the Field Section based on record status and configure an action visibility filter referencing the User custom permission.
Adding a component visibility filter on the Field Section allows administrators to hide or show entire sections dynamically based on record values like Status. In addition, Dynamic Actions filters can evaluate User context—including custom permissions—to conditionally render quick actions directly on the page without requiring multiple page layouts.

Step-by-Step Solution

1
Configure section visibility for record state
Select the 'Root Cause Analysis' Field Section on the Lightning Record Page and add a Component Visibility filter where Record > Status equals 'Closed'.
Dynamic Forms allows component-level control over field sections directly on the page layout.
2
Configure dynamic action visibility for user permissions
Highlight the Highlights Panel or page header, select the 'Escalate Incident' action, and add an Action Visibility filter selecting User > Permission > Custom Permission > Tier 3 Handler equals True.
Dynamic Actions allow conditional display of actions based on fields, user fields, and permissions without needing multiple page layouts.

Key Concept

Dynamic Forms Field Section Visibility and Dynamic Actions Filter Rules
Question 1031Question

Starlight Solar Solutions uses a custom object named Customer_Audit__c to track quality assurance reviews. The System Administrator needs to restrict access to a sensitive custom field, Risk_Assessment_Notes__c, so that only three risk analysts out of forty employees assigned to the Support Specialist profile can view it. Access must be restricted across all interfaces, reports, and API calls for the remaining thirty-seven users. Which configuration approach should the administrator implement to meet this requirement following Salesforce best practices?

Show answer & explanation

Answer: Set Field-Level Security for Risk_Assessment_Notes__c to hidden on the Support Specialist profile, create a permission set granting Read access to the field, and assign the permission set to the three risk analysts.

Answer

Set Field-Level Security for Risk_Assessment_Notes__c to hidden on the Support Specialist profile, create a permission set granting Read access to the field, and assign the permission set to the three risk analysts.
The standard Salesforce best practice for granting field access to a subset of users on a shared profile is to restrict the Field-Level Security on the profile level and use a Permission Set to grant additive Read or Edit access to the specific users who require it. FLS enforces security universally across the UI, API, reports, and list views.

Step-by-Step Solution

1
Evaluate baseline Field-Level Security (FLS) on the common profile
Remove visibility for Risk_Assessment_Notes__c on the Support Specialist profile so that the default baseline access for all forty users is restricted.
Profiles should define the minimum baseline access required by all users sharing that profile role.
2
Create an additive Permission Set
Build a permission set that enables Read access for the Risk_Assessment_Notes__c field.
Permission sets allow administrators to grant additional field permissions to specific users without modifying their assigned profile.
3
Assign the Permission Set to targeted users
Assign the new permission set directly to the three risk analysts.
This grants field visibility to only the required individuals across all UI surfaces, reports, and APIs while keeping the field secured for all other profile members.

Key Concept

Profiles establish baseline access restrictions, while Permission Sets grant additive Field-Level Security (FLS) access for user exceptions.
Estimated Time:1m 30s
Question 1032Question

Meridian Global operates two distinct sales divisions: Direct Commercial Sales and Public Sector Consulting. The Public Sector team requires a unique sequence of Opportunity stage picklist values to track compliance reviews and formal tender submissions, which differ from the standard stages used by Direct Commercial Sales. An administrator must ensure Public Sector reps can only select their division's specific stages when creating and managing opportunities. Which TWO configuration steps must the administrator perform to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Create a new Sales Process that selects the specific set of stage picklist values required for Public Sector Consulting.; Create a new Opportunity Record Type assigned to Public Sector users and link it to the newly created Sales Process.

Answer

The correct administrative steps are creating a new Sales Process with the required stage picklist values, and creating a new Opportunity Record Type linked to that Sales Process.
To display a customized set of Opportunity stages for a specific business unit, an administrator must first create a dedicated Sales Process containing the desired subset of stage picklist values. Next, the administrator creates an Opportunity Record Type linked to that Sales Process and assigns it to the appropriate user profiles. Opportunity stage picklist availability is controlled exclusively through the Sales Process mapped to the record type.

Step-by-Step Solution

1
Define the distinct stage picklist requirements in a Sales Process.
A Sales Process is created containing only the stages required for Public Sector Consulting.
Opportunity stage picklists are unique because their available values must be defined within a Sales Process before assigning them to record types.
2
Create an Opportunity Record Type and associate it with the new Sales Process.
The Record Type links the custom Sales Process to the appropriate user profiles.
Record Types associate page layouts and Sales Processes with users, ensuring reps see only the stage sequence configured for their business unit.

Key Concept

Sales Processes and Record Type Stage Mapping
Question 1033Question

A Salesforce administrator at a regional warehousing and logistics company is managing schema configurations in Object Manager. The team is evaluating the fundamental capabilities and operational constraints of standard objects (such as Account or Contact) compared to newly created custom objects. Which statement accurately describes a key capability difference between standard objects and custom objects in Salesforce?

Show answer & explanation

Answer: Custom objects can be deleted from an organization when they are no longer required, whereas standard objects built into Salesforce cannot be deleted.

Answer

Custom objects can be deleted from an organization when they are no longer required, whereas standard objects built into Salesforce cannot be deleted.
The correct answer accurately states that custom objects created in Salesforce can be deleted from the org if no hard dependencies exist, whereas standard objects provided natively by Salesforce cannot be deleted.

Step-by-Step Solution

1
Analyze standard object management capabilities in Salesforce.
Standard objects (like Account, Contact, Opportunity) are part of the core Salesforce data model and cannot be deleted from the organization, though standard tabs or fields can be hidden or renamed.
Salesforce architecture relies on core standard objects for built-in application logic and feature sets.
2
Analyze custom object management capabilities in Salesforce.
Custom objects created by administrators can be deleted if they are not referenced in component dependencies (such as Apex code, formulas, or active automation).
Deleting a custom object moves it to the undelete list for 15 days before permanent removal.
3
Evaluate the choices against object administration rules.
The statement highlighting that custom objects can be deleted while standard objects cannot be deleted is correct.
This correctly identifies a key administrative boundary between standard and custom schema components.

Key Concept

Standard vs Custom Object Capabilities and Deletion Rules
Estimated Time:1m 15s
Question 1034Question

A Salesforce Administrator needs to model a relationship between a custom object named Subscription__c and a custom object named Server__c. A single subscription can be assigned to multiple servers, and a server can host multiple subscriptions. The business requires tracking assignment metadata, such as Activation Date, on each association. Additionally, if either a Subscription__c or Server__c record is deleted, the association record must be automatically removed. Which TWO configuration steps should the administrator perform to satisfy these business requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a custom junction object containing two Master-Detail relationship fields pointing to Subscription__c and Server__c.; Create custom fields, such as Activation Date, directly on the newly created junction object.

Answer

The administrator must create a custom junction object containing Master-Detail relationships to both Subscription__c and Server__c, and add the necessary custom metadata fields directly onto that junction object.
To model a Many-to-Many relationship with automatic deletion cascading and custom fields per association, an administrator must create a custom junction object. Linking this junction object to both parent objects via Master-Detail relationships ensures that deleting either parent record automatically deletes the junction record. Custom fields for metadata like Activation Date can be created directly on the junction object.

Step-by-Step Solution

1
Identify the data modeling requirement for Many-to-Many relationships
Recognize that a Many-to-Many relationship in Salesforce requires a third custom object acting as a junction object.
Direct Many-to-Many field types do not exist in Salesforce schema design.
2
Select the appropriate relationship type for cascade deletion enforcement
Configure Master-Detail relationship fields on the junction object linking to both parent objects.
Master-Detail relationships enforce automatic deletion of junction records when either parent record is deleted.
3
Add relationship-specific metadata
Create custom fields like Activation Date on the junction object.
The junction object represents the unique intersection of both parent records and is the correct location to store association data.

Key Concept

Many-to-Many Relationships via Junction Objects
Question 1035Question

An administrator at Ursa Major Solar is configuring a Service Cloud Console application for customer support representatives. The support team leader requests that agents have persistent, single-click access to quick productivity features—such as CTI Softphone, History, and Macros—along the bottom footer of their console screen regardless of which record tab they are viewing. Which Salesforce Console configuration component should the administrator customize to fulfill this requirement?

Show answer & explanation

Answer: The Utility Bar in App Manager for the Service Console app

Answer

The Utility Bar in App Manager for the Service Console app
Configuring the Utility Bar for the Service Console application in App Manager allows administrators to attach persistent tools (such as Softphone, History, and Macros) to a fixed footer bar at the bottom of the screen, ensuring instant access across all open tabs.

Step-by-Step Solution

1
Identify the requested UI position and functionality
The requirement calls for a persistent tool dock along the bottom footer of the Service Cloud Console screen for tools like CTI Softphone, Macros, and History.
Understanding where and how the tools must be accessed isolates the correct configuration area in Salesforce Setup.
2
Evaluate Salesforce Console interface configuration components
The Utility Bar is designed specifically to host persistent lightning components at the bottom of the screen in Lightning console applications.
Administrators configure utility bar items under Setup > App Manager > Edit Application > Utility Items.

Key Concept

Lightning App Utility Bar Configuration in Service Cloud Console
Question 1036Question

An organization is implementing a dedicated fulfillment process for the Order object. The administrator must ensure that users working on these fulfillment orders see a customized field layout and are restricted to selecting only specific values from the Status picklist. Which TWO configuration steps must the administrator take to accomplish this requirement? (Choose 2 answers.)

Select all that apply

Show answer & explanation

Answer: Assign the customized page layout to the target user profiles for the newly created record type.; Edit the selectable Status picklist values directly within the new record type detail page.

Answer

Assign the customized page layout to the target user profiles for the newly created record type, and edit the selectable Status picklist values directly within the new record type detail page.
Page layout assignment in Salesforce requires configuring the Page Layout Assignment matrix by user Profile and Record Type. Additionally, picklist value availability is customized per Record Type within Object Manager.

Step-by-Step Solution

1
Map Page Layout to Profile and Record Type
The profile assignment matrix ensures that users accessing the specified record type see the tailored page layout.
Salesforce determines page layout display by referencing the user's Profile and the record's Record Type.
2
Modify Available Picklist Values per Record Type
The Status picklist field only presents the subset of values designated for the fulfillment process.
Record types provide control over available picklist values without altering master picklist field definitions.

Key Concept

Page Layout and Record Type Picklist Assignment
Estimated Time:1m 30s
Question 1037Question

A Salesforce administrator at Cloud Kicks needs team members to see automated record feed updates whenever the Status or Resolution Notes fields on a custom object named Service_Ticket__c are modified. Furthermore, users should be able to create a follow-up Task directly from the Chatter feed header on a Service_Ticket__c record page. Which two administrative actions must the administrator perform to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Enable Feed Tracking for the Service_Ticket__c object and select the Status and Resolution Notes fields in Chatter settings.; Add the Create Task quick action to the Salesforce Mobile and Lightning Experience Actions section of the Service_Ticket__c Page Layout.

Answer

Enabling Feed Tracking for the Service_Ticket__c object with Status and Resolution Notes selected, and adding the Create Task quick action to the Salesforce Mobile and Lightning Experience Actions section of the Service_Ticket__c Page Layout.
To track record field changes automatically in Chatter feeds, an administrator must enable Feed Tracking for the specific object (Service_Ticket__c) and select the desired fields (Status and Resolution Notes). Additionally, to make quick actions (such as Create Task) available on a record's Chatter publisher header, the action must be added to the Salesforce Mobile and Lightning Experience Actions section of that object's Page Layout.

Step-by-Step Solution

1
Navigate to Setup > Feed Tracking, select the Service_Ticket__c object, check Enable Feed Tracking, and select the Status and Resolution Notes fields.
System-generated feed updates automatically appear on record Chatter feeds whenever those selected fields are modified.
Feed tracking configuration defines which object fields trigger automated system posts.
2
Navigate to Object Manager > Service_Ticket__c > Page Layouts and edit the assigned layout.
Placing the Create Task action in the Salesforce Mobile and Lightning Experience Actions area exposes it in the record feed publisher.
Record page publisher actions are dictated by the page layout configuration of that specific object.

Key Concept

Chatter Feed Tracking & Page Layout Publisher Actions
Question 1038Question

An administrator is configuring Opportunity Teams and Team Selling access within a Salesforce org with Private Organization-Wide Defaults. Match each Opportunity Team sharing setting or feature on the left with its corresponding access behavior or functionality on the right. How do these Opportunity Team access permissions behave?

Click a left item, then click its matching right item

Items

Default Opportunity Team
Read/Write Opportunity Team Access
Implicit Parent Account Access
Role Hierarchy Access for Opportunity Teams

Matches

Show answer & explanation

Answer

Default Opportunity Team matches with automatically adding a predefined list of team members; Read/Write Opportunity Team Access matches with granting view and edit permissions despite Private OWD; Implicit Parent Account Access matches with providing Read Only access to the associated parent account; Role Hierarchy Access matches with ensuring managers inherit access granted to subordinate team members.
Each feature corresponds strictly to its Salesforce sharing model behavior: Default Opportunity Teams store standard member configurations; Read/Write access allows record editing under Private OWD; implicit account access provides Read Only access to the parent Account; and Role Hierarchy propagation grants managers access inherited from their subordinates.

Step-by-Step Solution

1
Analyze Default Opportunity Team functionality
Identify that Default Opportunity Teams store a user's standard team setup so it can be added to opportunities efficiently.
Default Opportunity Teams streamline team assignment by adding predefined members with specified access levels.
2
Evaluate Read/Write access behavior on Opportunity Teams
Determine that Read/Write access overrides Private OWD to allow assigned team members to update opportunity details.
Opportunity Team sharing extends record access beyond default organization-wide sharing boundaries.
3
Examine implicit sharing rules between Opportunity Teams and Accounts
Confirm that being added to an Opportunity Team provides implicit Read Only access to the associated parent Account.
Salesforce enforces built-in implicit sharing so team members can view context on the parent account record.
4
Assess how Role Hierarchy interacts with Opportunity Team access
Verify that managers higher up in the role hierarchy receive the same access rights granted to their direct reports on Opportunity Teams.
Hierarchy access rules propagate manually shared or team-shared record access up the managerial chain.

Key Concept

Opportunity Team Sharing and Access Propagation
Estimated Time:1m 30s
Question 1039Question

A system administrator at a renewable energy manufacturing firm is configuring Salesforce Service Cloud to automate support operations. The support manager requests that if any High Priority case remains in an unassigned or pending state for more than 4 business hours after creation, the case must automatically be reassigned to the Tier 3 Escalation Queue and the Support Director must be notified via email. The administrator attempts to implement this requirement by adding an entry with a time offset of 4 hours to the active Case Assignment Rule. Why will this configuration fail to fulfill the requirement?

Show answer & explanation

Answer: Case Assignment Rules evaluate criteria only at record creation or manual assignment submission and cannot execute time-delayed actions; Escalation Rules must be used for time-elapsed reassignment.

Answer

Case Assignment Rules evaluate criteria only at record creation or manual assignment submission and cannot execute time-delayed actions; Escalation Rules must be used for time-elapsed reassignment.
Case Assignment Rules are designed exclusively for immediate, synchronous owner routing when a case is created or when a user checks the 'Assign using active assignment rules' checkbox during an update. They do not support time-based criteria or delayed execution offsets. To automatically reassign a case and send notifications based on the amount of time a case has remained open or unhandled, Case Escalation Rules must be configured.

Step-by-Step Solution

1
Analyze the operational business requirement.
The requirement involves monitoring elapsed time (4 business hours after creation) and performing automated actions (reassigning ownership and sending notification emails).
Time-based criteria tied to SLA compliance require automation tools designed specifically for time offsets.
2
Evaluate the capabilities of Case Assignment Rules versus Case Escalation Rules.
Case Assignment Rules specify how cases are assigned to users or queues synchronously when created or updated. They do not possess time-based triggers. Escalation Rules specifically evaluate time criteria (e.g., hours open) to reassign cases and notify users.
Using the wrong automation feature leads to failure in executing delayed logic.
3
Determine why the administrator's setup fails.
Attempting to configure a 4-hour delay within a Case Assignment Rule entry fails because assignment rules only execute synchronously upon record save.
Only Case Escalation Rules can trigger actions after a specified time threshold has elapsed.

Key Concept

Distinction between Case Assignment Rules (initial synchronous routing) and Case Escalation Rules (time-elapsed reassignment and notification).
Estimated Time:2m 0s
Question 1040Question

A marketing operations team is setting up a virtual workshop campaign in Salesforce. The administrator needs to track members who only registered separately from those who actively participated in the workshop. To ensure that campaign metrics and response counts reflect only participants who actively engaged, which configuration action should the administrator take on the Campaign Member Statuses?

Show answer & explanation

Answer: Add custom status values 'Registered' and 'Attended', and select the 'Responded' checkbox exclusively for the 'Attended' status.

Answer

Add custom status values 'Registered' and 'Attended', and select the 'Responded' checkbox exclusively for the 'Attended' status.
In Salesforce Campaign Management, setting the 'Responded' checkbox on specific Campaign Member Status values determines whether a member's action counts as a response. Marking 'Attended' as responded while leaving 'Registered' unflagged ensures campaign roll-up fields like Total Responses only summarize engaged participants.

Step-by-Step Solution

1
Identify the requirement for tracking campaign member engagement.
Members who registered are distinct from members who attended.
Campaign metrics rely on the 'Responded' flag to calculate response rates.
2
Configure Campaign Member Status values in Advanced Setup on the Campaign record.
Add 'Registered' and 'Attended' as custom status values.
Custom member statuses categorize member progression through campaign activities.
3
Set the 'Responded' flag appropriately.
Check 'Responded' only for 'Attended' and keep 'Registered' unchecked.
Only statuses with the 'Responded' checkbox enabled contribute to the Total Responses count on the Campaign.

Key Concept

Campaign Member Status Responded Flag
PreviousPage 52 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin