All practice questions

1784 questions

Question 1041Question

A Salesforce Administrator is configuring a Lightning record page for a custom Compliance Audit object. The business requires the sensitive field 'Penalty Amount' to appear on the Lightning record page only when the 'Audit Status' picklist field is set to 'Non-Compliant'. Additionally, data security policies require that users without proper authorization cannot access 'Penalty Amount' values through reports, list views, or API exports. Which combination of configurations should the administrator use to fulfill these requirements?

Show answer & explanation

Answer: Configure Field-Level Security to restrict field access for unauthorized users, and set up a Dynamic Forms component visibility rule on the Lightning record page based on Audit Status.

Answer

Configure Field-Level Security to restrict field access for unauthorized users, and set up a Dynamic Forms component visibility rule on the Lightning record page based on Audit Status.
The correct answer combines Field-Level Security (FLS) with Dynamic Forms component visibility. FLS is mandatory for data security across all entry points (reports, list views, API, and record pages). Dynamic Forms component visibility provides the required conditional rendering on the record page based on the 'Audit Status' picklist value.

Step-by-Step Solution

1
Identify the data security requirement
Field-Level Security (FLS) must be configured for the 'Penalty Amount' field so unauthorized users cannot access it via API, reports, list views, or record detail views.
UI visibility rules alone do not prevent data access through alternative interfaces like reports or API.
2
Identify the user interface requirement
A Dynamic Forms component visibility filter is configured on the 'Penalty Amount' field component in Lightning App Builder with the criteria: Audit Status equals 'Non-Compliant'.
Dynamic Forms allows granular component and field visibility based on record field values on Lightning record pages.
3
Combine security and UI visibility controls
Authorized users will see the field on the Lightning page only when Audit Status is 'Non-Compliant', while unauthorized users will remain unable to access the field anywhere in Salesforce.
Combining FLS and Dynamic Forms visibility ensures both data security and optimal user experience.

Key Concept

Dynamic Forms Visibility vs. Field-Level Security
Question 1042Question

Summit Financial Solutions requires a subset of financial analysts within the Operations department to have Read and Edit access to a sensitive custom field, Bank_Account_Number__c, on the Customer_Profile__c object. Currently, all Operations staff share a single baseline profile that grants no access to this field. Furthermore, management requires that these specific analysts be restricted to logging into Salesforce only from the corporate network IP range, while other Operations staff remain unaffected. Which TWO actions should the System Administrator take to meet these requirements securely? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a Permission Set that grants Read and Edit field-level security for Bank_Account_Number__c, and assign it to the financial analysts.; Clone the standard profile to create a dedicated profile for the financial analysts, define the Login IP Ranges on the new profile, and reassign the analysts to this profile.

Answer

The administrator should create a Permission Set granting Read and Edit field-level security for the custom field and assign it to the analysts, and clone the baseline profile to create a dedicated profile where Login IP Ranges are configured for those specific users.
To grant additional field access to specific users without altering the shared baseline profile, a Permission Set granting Read and Edit field-level security should be assigned to those users. To enforce login IP restrictions for only those analysts, they must be assigned to a dedicated profile where Login IP Ranges are specified, because login IP restrictions are enforced at the profile level.

Step-by-Step Solution

1
Evaluate field-level security requirements.
Identify that additive field access for a subset of users sharing a profile requires a Permission Set rather than modifying the shared baseline profile.
Salesforce best practice dictates keeping profiles minimal and using Permission Sets to grant extra object or field permissions.
2
Evaluate login IP restriction requirements.
Recognize that Login IP Ranges must be enforced on a profile level to restrict login access strictly within a specified network range.
Since Login IP Ranges are defined per profile, users requiring distinct login restrictions must be assigned to a separate profile configured with those IP ranges.

Key Concept

Profiles control restrictive baseline settings like Login IP Ranges, whereas Permission Sets grant additive permissions such as Field-Level Security.
Estimated Time:1m 30s
Question 1043Question

An administrator at a global aviation maintenance company needs to immediately suspend login access for a lead auditor placed on sudden administrative leave. When attempting to deactivate the user record, Salesforce prevents the action due to active system dependencies. Which two configurations explain why deactivating the user account is currently blocked, making account freezing the required immediate alternative? (Select 2 answers.)

Select all that apply

Show answer & explanation

Answer: The user is currently assigned as the Default Workflow User in Process Automation Settings.; The user is designated as the Default Case Owner in Support Settings.

Answer

Deactivation is prevented when a user is configured as the Default Workflow User in Process Automation Settings or designated as the Default Case Owner in Support Settings. Freezing the account allows administrators to immediately block login access while resolving these dependencies.
Deactivating a user account in Salesforce is blocked when the user is referenced in specific system settings, such as being designated as the Default Workflow User or Default Case Owner. Freezing the user account allows administrators to immediately stop login access while these administrative configuration references are updated.

Step-by-Step Solution

1
Identify the operational requirements for restricting access.
Login access must be revoked immediately, but system dependencies prevent standard deactivation.
Users tied to default system settings cannot be deactivated until those administration roles are transferred.
2
Evaluate system dependency rules preventing deactivation.
Selections as Default Workflow User or Default Case/Lead Owner actively block the deactivation operation in Setup.
Salesforce enforces integrity by ensuring automated processes continuously have valid default routing targets.
3
Determine the appropriate immediate administrative action.
Freezing the user account temporarily blocks authentication without removing license assignment or breaking automated process definitions.
Freezing bypasses deactivation dependency checks to provide immediate security enforcement.

Key Concept

User Freezing vs. User Deactivation Dependencies
Question 1044Question

An administrator at Vertex Logistics is configuring Chatter collaboration capabilities and Feed Tracking for the custom Shipment__c object and standard Account object. Which two administrative configurations are accurate regarding Chatter Feed Tracking and Publisher Layouts? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Enabling Feed Tracking on an object allows administrators to select up to 20 fields whose changes automatically create Chatter feed updates.; Overriding the Global Publisher Layout on an object's page layout allows administrators to customize which Chatter quick actions appear for that specific object.

Answer

The two correct configurations are selecting up to 20 fields per object for automatic Chatter feed updates when Feed Tracking is enabled, and overriding the Global Publisher Layout on an object's page layout to customize Chatter quick actions for that specific object.
Enabling Feed Tracking allows administrators to choose up to 20 fields per object to post changes automatically to record feeds. Additionally, overriding global publisher layouts on an object page layout grants administrators control over object-specific quick action placement in Chatter feeds.

Step-by-Step Solution

1
Analyze Chatter Feed Tracking limits and setup behavior
Confirm that Feed Tracking must be enabled per object and supports selecting up to 20 specific fields to trigger feed posts upon modification.
Field changes will not generate Chatter feed posts unless Feed Tracking is enabled and specific fields are checked in Setup.
2
Evaluate Publisher Layout override rules for objects
Determine that while Global Publisher Layouts provide global defaults, individual object page layouts can override these defaults to offer tailored actions.
Object-specific publisher layout customization ensures users see relevant quick actions (like creating a record or logging a call) contextually.

Key Concept

Chatter Feed Tracking enables automatic record feed posts for up to 20 designated fields per object, while Publisher Layouts control the quick actions available in Chatter feeds globally or per object.
Question 1045Question

An administrator needs to create a Chatter group for executive announcements. All employees should be able to view and comment on posts in the group feed, but only group owners and managers should be permitted to create new posts. Which Chatter group feature should the administrator use to satisfy this requirement?

Show answer & explanation

Answer: Broadcast group setting

Answer

The correct option is the Broadcast group setting, which restricts post creation to group owners and managers while allowing all group members to view and comment.
Enabling the Broadcast group setting on a Chatter group restricts post creation exclusively to group owners and managers. Group members retain the ability to view feed updates and comment on posts, making it the standard Salesforce configuration for announcement-only groups.

Step-by-Step Solution

1
Identify the functional requirement for Chatter group posting permissions.
The requirement specifies that general members should read and comment, but only managers and owners can post.
Salesforce provides specialized Chatter group types and options to handle common collaboration patterns like one-way announcement channels.
2
Evaluate Chatter group options against the requirement.
Marking a Chatter group as a Broadcast group limits post creation exclusively to group owners and managers.
This built-in setting directly enforces the required posting restrictions without needing custom administrative permissions or workarounds.

Key Concept

Chatter Broadcast Group Capabilities
Estimated Time:45s
Question 1046Question

A Salesforce administrator is evaluating intake channels and needs to configure On-Demand Email-to-Case to process incoming customer support requests. Which two features or operational characteristics apply to On-Demand Email-to-Case? (Select 2)

Select all that apply

Show answer & explanation

Answer: Email messages and attachments up to 25 MB are processed entirely through Salesforce cloud infrastructure without requiring local agent software behind a firewall.; Administrators can configure Over-Limit Actions such as Bounce, Discard, or Requeue to determine how emails are handled if daily processing limits are reached.

Answer

On-Demand Email-to-Case processes emails and attachments up to 25 MB entirely within the Salesforce cloud infrastructure, and enables administrators to configure Over-Limit Actions (such as Bounce, Discard, or Requeue) when daily limit thresholds are reached.
On-Demand Email-to-Case routes emails through Salesforce cloud infrastructure (Apex Email Services) without requiring local agent software, accepting email messages up to 25 MB. Furthermore, administrators can specify Over-Limit Actions (Bounce, Discard, or Requeue) to determine how incoming emails are processed when the daily organization processing limit is exceeded.

Step-by-Step Solution

1
Identify the architecture and attachment limit of On-Demand Email-to-Case.
Recognize that On-Demand Email-to-Case uses Salesforce cloud infrastructure (Apex Email Services) rather than a local server agent, supporting attachments up to 25 MB.
This distinguishes On-Demand Email-to-Case from traditional Email-to-Case which uses an behind-the-firewall agent.
2
Evaluate overflow administration capabilities.
Identify that admins can set Over-Limit Actions (Bounce, Discard, or Requeue) to handle incoming messages when daily processing limits are met.
Salesforce provides explicit options to manage incoming traffic when daily email limits are reached.

Key Concept

On-Demand Email-to-Case Architecture and Limit Actions
Question 1047Question

A Salesforce administrator at a university research library system is configuring a custom object named Manuscript Loan to track archived manuscript borrowing requests associated with the standard Contact object. The administrator needs to evaluate schema management capabilities, relationship requirements, and data governance rules for this setup. Which two statements accurately describe Salesforce standard and custom object capabilities in this scenario? (Select 2)

Select all that apply

Show answer & explanation

Answer: If a Master-Detail relationship is configured between Contact and Manuscript Loan, deleting a Contact record will automatically delete all related Manuscript Loan records.; Custom objects can be deleted from Object Manager even if they contain data records, as long as all custom field references, Apex code, and workflow dependencies are cleared.

Answer

Cascading deletion occurs automatically for detail records in a Master-Detail relationship when the master record is deleted, and custom objects containing data can be deleted from Object Manager after clearing component dependencies.
In Salesforce Object Manager schema design, establishing a Master-Detail relationship forces child records to inherit parent lifecycle behavior, meaning deleting the parent Contact automatically deletes related child records. Additionally, administrators can delete custom objects containing records provided component dependencies such as code or custom formula fields are disassociated.

Step-by-Step Solution

1
Analyze relationship lifecycle behavior for standard and custom objects.
Master-Detail relationships enforce cascading deletion of child records upon deletion of the parent record.
Detail records depend entirely on the master record for ownership and access control.
2
Evaluate custom object deletion prerequisites in Object Manager.
Custom objects with existing records can be deleted once hard component dependencies (such as Apex or formula references) are removed.
Salesforce allows schema deletion of custom objects without requiring record purging first, provided non-data metadata dependencies are cleared.
3
Review roll-up summary and UI security limitations against distractors.
Lookup relationships do not support Roll-Up Summary fields without custom code or automation, and Dynamic Forms component visibility does not enforce backend API security.
Roll-Up Summary functionality strictly requires Master-Detail architecture, while Field-Level Security must be managed at the profile/permission set level.

Key Concept

Standard vs Custom Object Lifecycle and Schema Capabilities
Question 1048Question

A Salesforce Administrator is setting up a new Lightning Service Console app for a tier-two support team. Place the steps for creating and publishing this console app in the correct chronological order.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with creating a New Lightning App in App Manager, specifying Console Navigation as the navigation style, adding items to the Utility Bar, and finally assigning the app to the appropriate user profiles.
Building a Lightning Service Console app follows the step-by-step Salesforce App Manager wizard: initiating app creation in Setup, defining the app as Console Navigation, adding footer tools via the Utility Bar, and granting access by assigning target User Profiles.

Step-by-Step Solution

1
Access App Manager in Setup and click New Lightning App
Launches the Lightning App Wizard to define app details.
All new Lightning console applications must be created from the App Manager.
2
Set App Options to Console Navigation
Configures the app to open records in primary tabs and subtabs.
Choosing Console Navigation distinguishes a Service Console app from a standard tabbed app.
3
Configure Utility Items
Adds quick-access tools to the footer of the console app.
Utility components are added after navigation style and app details are defined.
4
Assign User Profiles
Grants visibility and access to designated support representatives.
Profile assignment is the final stage of the app creation wizard before saving.

Key Concept

Service Cloud Console Configuration Sequence
Question 1049Question

Universal Containers maintains an Organization-Wide Default (OWD) sharing setting of Private for both Account and Opportunity records. A sales representative adds a technical specialist to an Opportunity Team with Read/Write access on a specific high-value deal. What access does the technical specialist automatically receive on the associated parent Account record as a result of this action?

Show answer & explanation

Answer: Implicit Read Only access to the parent Account record

Answer

The technical specialist receives implicit Read Only access to the parent Account record.
Under Salesforce Parent Implicit Sharing rules, when a user is added to an Opportunity Team, Salesforce automatically grants that user implicit Read Only access to the associated parent Account record if they do not already have access to it.

Step-by-Step Solution

1
Identify the sharing mechanics triggered by Opportunity Team addition
Adding a user to an Opportunity Team establishes object-level access for the Opportunity record.
Salesforce built-in implicit sharing determines how access cascades up to parent records.
2
Apply Parent Implicit Sharing rules for Opportunities
Salesforce grants the Opportunity Team member implicit Read Only access to the associated parent Account record.
Users who can view or edit a child record must be able to see the parent record context.

Key Concept

Opportunity Team Implicit Account Sharing
Estimated Time:1m 30s
Question 1050Question

An administrator is troubleshooting Chatter feed behavior for a custom object named Project__c. Users report two distinct issues:
1. Automated feed posts are not generated when the Risk_Level__c custom field is updated on a Project__c record, despite Feed Tracking being turned on for the Project__c object.
2. A newly created Global Quick Action, 'Log Risk', appears on the Chatter Home tab publisher but is missing from the publisher on individual Project__c record pages.

Which combination of administrative actions will resolve both issues?

Show answer & explanation

Answer: Select the Risk_Level__c checkbox under Project__c Feed Tracking settings, and add the 'Log Risk' action to the Salesforce Mobile and Lightning Experience Actions section of the Project__c Page Layout.

Answer

Select the Risk_Level__c checkbox under Project__c Feed Tracking settings, and add the 'Log Risk' action to the Salesforce Mobile and Lightning Experience Actions section of the Project__c Page Layout.
Enabling Feed Tracking for an object is a two-step process: turning on tracking for the object itself, and then explicitly checking the boxes for up to 20 specific fields (such as Risk_Level__c) whose changes should create feed posts. Furthermore, Global Quick Actions placed on the Global Publisher Layout only appear on global Chatter locations (Home tab, Chatter tab, Profile). To make a quick action available on a record page publisher, it must be added to that object's Page Layout under the Salesforce Mobile and Lightning Experience Actions section.

Step-by-Step Solution

1
Analyze why field updates to Risk_Level__c do not generate Chatter feed posts.
Enabling Feed Tracking at the object level is a prerequisite, but field updates are only posted if specific field checkboxes (up to 20 per object) are explicitly selected in Setup > Feed Tracking.
Simply enabling object-level feed tracking without selecting the target field prevents change events from generating feed items.
2
Analyze why the Global Quick Action 'Log Risk' is missing from record pages.
Global Quick Actions added to Global Publisher Layouts render only on global feeds (Home tab, Chatter tab, User Profiles).
To display a quick action on an individual record page feed publisher, the action must be added to the Salesforce Mobile and Lightning Experience Actions palette on that object's specific Page Layout.
3
Synthesize the resolution requiring both configurations.
Select Risk_Level__c in Project__c Feed Tracking settings and add the 'Log Risk' action to the Project__c Page Layout.
This dual resolution addresses both the field tracking configuration gap and the publisher layout action scope.

Key Concept

Chatter Feed Tracking Field Selection and Publisher Layout Action Scoping
Estimated Time:2m 0s
Question 1051Question

An administrator creates a new Record Type called 'Enterprise Partner' on the Lead object to support a specialized channel sales team. During testing, users assigned to the 'Partner Sales Manager' profile report that when creating a Lead using the 'Enterprise Partner' record type, the 'Industry' picklist field displays values irrelevant to partner leads, and the detail view displays the default lead fields rather than the specialized partner fields. Which combination of configuration steps must the administrator perform to resolve both issues?

Show answer & explanation

Answer: Edit the page layout assignment matrix to assign the specialized partner layout to the Partner Sales Manager profile for the Enterprise Partner record type, and modify the selected picklist values for the Industry field directly within the Enterprise Partner record type configuration.

Answer

The administrator must edit the page layout assignment matrix to map the specialized partner layout to the Partner Sales Manager profile for the Enterprise Partner record type, and adjust the available Industry picklist values under the Enterprise Partner record type settings.
To display custom fields and restricted picklist options for a specific business process, an administrator must complete two distinct steps: map the appropriate page layout to the user profile and record type in the Page Layout Assignment grid, and edit the picklist configuration under the specific Record Type to choose which values are available.

Step-by-Step Solution

1
Navigate to Object Manager > Lead > Page Layouts > Page Layout Assignment.
Access the matrix mapping profiles to record types and page layouts.
Page layouts are assigned based on the combination of a user's Profile and the record's Record Type.
2
Select the cell corresponding to the Partner Sales Manager profile and Enterprise Partner record type, and select the specialized partner page layout.
Users with the Partner Sales Manager profile see the correct fields when viewing or creating Enterprise Partner leads.
This establishes the appropriate layout assignment for the target user group.
3
Navigate to Object Manager > Lead > Record Types > Enterprise Partner, locate the Industry picklist field, and edit its selected values.
Only relevant picklist values are enabled for selection on this record type.
Creating a record type inherits all master picklist values by default; specific values must be manually selected for each record type.

Key Concept

Page Layout Assignment and Record Type Picklist Filtering
Question 1052Question

A Salesforce Administrator is configuring distinct case management lifecycles for an enterprise support team. Match each Salesforce administrative component on the left with its correct role or function in configuring Case Record Types and Support Processes on the right.

Click a left item, then click its matching right item

Items

Support Process
Case Record Type
Page Layout
Master Case Status Picklist

Matches

Show answer & explanation

Answer

Each administrative component maps directly to its specific role: Support Process defines a subset of status picklist values for a lifecycle; Case Record Type links a Support Process with a Page Layout for profile assignment; Page Layout controls field organization and UI visibility; and Master Case Status Picklist stores all possible organizational status values.
Support Processes define the allowed Case Status values for a particular business workflow. Case Record Types reference a designated Support Process along with a Page Layout to control layout and picklist access per profile. Page Layouts arrange UI elements, and the Master Case Status Picklist contains the entire baseline repository of status options.

Step-by-Step Solution

1
Identify the primary role of a Support Process on the Case object.
Determine that a Support Process filters the master status list down to specific values needed for a business lifecycle.
Before a Case Record Type can be created, a Support Process must exist to define the valid Case Status picklist values.
2
Identify the function of a Case Record Type.
Understand that Record Types tie together the Support Process and Page Layout and enable profile assignment.
Record Types drive page layout assignments and picklist value availability for distinct user profiles.
3
Differentiate Page Layouts and Master Case Status picklists.
Map Page Layouts to UI layout formatting and Master Case Status to the overall organizational pool of status values.
Page Layouts govern UI elements, while Master Picklists store all global value definitions.

Key Concept

Support Process and Record Type Architecture
Estimated Time:1m 30s
Question 1053Question

An administrator needs to track employee certifications in Salesforce. An employee can hold multiple certifications, and a single certification can be held by multiple employees. Additionally, management requires a roll-up summary field on the Employee object to count the total number of certifications earned by each employee. Which configuration should the administrator implement to meet these requirements?

Show answer & explanation

Answer: Create a custom junction object with Master-Detail relationships to both the Employee and Certification objects.

Answer

Create a custom junction object with Master-Detail relationships to both the Employee and Certification objects.
To model a many-to-many relationship in Salesforce, a custom junction object must be created with relationship fields linking to both parent objects. Furthermore, because management requires a roll-up summary field on the parent object, the relationship from the junction object to the parent object must be a Master-Detail relationship, as roll-up summary fields are only supported over Master-Detail relationships.

Step-by-Step Solution

1
Determine the data modeling structure required to support a many-to-many relationship between Employee and Certification.
A custom junction object is required to connect both standard/custom objects.
In Salesforce, many-to-many relationships are established by creating a junction object that links two parent objects.
2
Evaluate the field type requirement for roll-up summary capabilities on the parent objects.
The relationship fields on the junction object pointing to both parent objects must be Master-Detail relationships.
Roll-up summary fields can only be created on the master object in a Master-Detail relationship, not over Lookup relationships.

Key Concept

Many-to-Many Relationships and Roll-Up Summary Field Requirements
Estimated Time:1m 30s
Question 1054Question

Apex Health Logistics is implementing a custom Lightning Service Console app for its specialized tier-2 escalation support team. The support manager has outlined three strict functional layout requirements for the console interface: 1) When an agent opens an Account record from inside a Case, the Account record must open as a subtab under that Case rather than as a new primary tab; 2) Support agents must be able to view and edit associated Contact details directly from the Case record view without switching active tabs; and 3) Key case fields (Status, Priority, Account Name, and Contact Phone) must remain persistently visible at the top of the Case record page regardless of scrolling. Which combination of configuration actions should the Salesforce Administrator perform to fulfill these requirements?

Show answer & explanation

Answer: Define tab navigation rules in Navigation Items settings to open Account as a subtab of Case; add a Related Record component for Contact to the Case Lightning Record Page; and customize the Case Compact Layout with the required fields.

Answer

Define tab navigation rules in App Manager settings to open Account as a subtab of Case; add a Related Record component for Contact to the Case Lightning Record Page; and customize the Case Compact Layout.
The solution requiring tab navigation rules, a Related Record component, and a Compact Layout correctly addresses all three admin requirements. Console App Navigation Rules in App Manager define parent-child tab navigation (making Account open as a subtab under Case). The Related Record component on the Case Lightning page displays fields from the parent Contact lookup, enabling inline editing without navigating away. Finally, customizing the Case Compact Layout populates the top Highlights Panel, ensuring key case attributes remain visible during scrolling.

Step-by-Step Solution

1
Configure Console Tab Navigation Rules in App Manager
Specifies that opening an Account record from a parent Case context dynamically opens the Account as a subtab under the primary Case tab.
Console navigation rules govern how related records open relative to primary workspace tabs.
2
Add a Related Record component to the Case Lightning Record page
Allows agents to view and update fields on the associated Contact record directly inside the Case page view.
The Related Record component uses quick actions to present editable fields of a lookup record without tab switching.
3
Customize the Case object's Compact Layout
Drives the fields displayed in the top Highlights Panel of the Service Console record page.
The Highlights Component in Lightning Console relies on the object's assigned Compact Layout to display persistent header summary fields.

Key Concept

Service Cloud Console Navigation Rules, Related Record Components, and Compact Layout Configuration
Question 1055Question

Match each Salesforce Chatter group access type on the left with its corresponding visibility and membership behavior on the right.

Click a left item, then click its matching right item

Items

Public Group
Private Group
Unlisted Group

Matches

Show answer & explanation

Answer

Public Group matches with 'Visible in search; any internal user can view feed content and join without approval.' Private Group matches with 'Visible in search; only members can view feed content, and non-members must request to join.' Unlisted Group matches with 'Hidden from search; only members can view feed content, and users must be invited to join.'
Public groups permit open access and visibility to all users. Private groups remain discoverable in search but restrict feed visibility and require membership approval. Unlisted groups hide the group from search entirely and restrict access strictly to invited members.

Step-by-Step Solution

1
Analyze Public Chatter Group access settings.
Public groups are fully accessible to all internal users without needing approval.
Public group visibility settings permit open join requests and open feed access.
2
Analyze Private Chatter Group access settings.
Private groups are discoverable in search, but feed content requires membership approval.
Private groups protect discussion privacy while remaining discoverable in the directory.
3
Analyze Unlisted Chatter Group access settings.
Unlisted groups conceal both group existence in search results and feed content from non-members.
Unlisted groups require enabling unlisted groups in Chatter settings and offer confidential collaboration via invitation only.

Key Concept

Chatter Group Types and Visibility Rules
Estimated Time:45s
Question 1056Question

An administrator at an online subscription platform is troubleshooting Salesforce Knowledge access for customer support representatives. The representatives have active Knowledge User feature licenses and object-level Read permissions on Knowledge articles, but they cannot view any published articles categorized under the newly created "Account Billing" Data Category group. What configuration change should the administrator make to grant the representatives access to these articles?

Show answer & explanation

Answer: Configure the Data Category group visibility for the representatives' roles, profiles, or permission sets.

Answer

Configure the Data Category group visibility for the representatives' roles, profiles, or permission sets.
In Salesforce Knowledge, visibility into published articles associated with Data Categories is controlled separately through Data Category visibility settings on Roles, Profiles, or Permission Sets (or Default Data Category Visibility). Having an active Knowledge User feature license and object-level Read permissions is required, but without Data Category visibility granted for a given category group, users cannot view articles in that group.

Step-by-Step Solution

1
Identify why published articles remain invisible.
Object-level Read permissions and feature licenses are active, indicating a category-level restriction.
Salesforce Knowledge uses Data Category visibility settings to determine which categorized articles users can view.
2
Review Data Category visibility settings.
The new Data Category group is set to None by default for the support user roles, profiles, or permission sets.
Categories default to restricted access unless explicit visibility rules (All, Custom, or Default) are configured.
3
Update Data Category visibility permissions.
Support representatives are granted Custom or All visibility to the Account Billing category group.
Explicit Data Category visibility enables users to search for and view articles assigned to those categories.

Key Concept

Data Category Visibility in Salesforce Knowledge
Question 1057Question

A Lead Administrator at an international freight logistics company is designing automated case management logic in Salesforce Service Cloud. The support operations require incoming critical shipping cases to be routed immediately to specialized regional support queues, while unassigned or unresolved high-priority cases must notify senior managers if inactive for 4 hours during defined business hours. Which two statements accurately describe the configuration rules and behaviors for Case Assignment Rules and Escalation Rules?

Select all that apply

Show answer & explanation

Answer: Only one Case Assignment Rule and one Escalation Rule can be active at any given time on the Case object, even though each active rule can contain multiple prioritized rule entries.; Case Assignment Rules assign ownership of newly submitted cases upon creation, whereas Escalation Rules perform actions such as reassignment or email notifications based on elapsed time criteria.

Answer

The two correct statements are that only one Case Assignment Rule and one Escalation Rule can be active at a time on the Case object, and that Case Assignment Rules assign ownership upon creation while Escalation Rules execute actions based on elapsed time criteria.
The correct options accurately state Salesforce's single active rule limitation (one active Assignment Rule and one active Escalation Rule per object) and correctly distinguish between initial ownership routing upon creation versus time-elapsed escalation actions.

Step-by-Step Solution

1
Evaluate rule activation limits on the Case object in Salesforce.
Salesforce restricts configuration to exactly one active Case Assignment Rule and one active Escalation Rule per object.
Although a single rule structure can contain multiple ordered rule entries evaluated sequentially, only one overall rule can be active simultaneously.
2
Differentiate the operational triggers for Case Assignment Rules versus Escalation Rules.
Case Assignment Rules determine initial ownership at creation, whereas Escalation Rules execute actions based on elapsed time relative to creation or modification dates.
Escalation Rules evaluate SLA thresholds against specified Business Hours to trigger reassignment or notification actions on aging cases.

Key Concept

Case Assignment Rules govern initial ownership routing at creation, whereas Escalation Rules trigger automated actions based on elapsed time thresholds and business hours. Salesforce permits only one active Assignment Rule and one active Escalation Rule at any time on the Case object.
Estimated Time:2m 0s
Question 1058Question

A Salesforce Administrator needs to convert a custom object record page to Dynamic Forms and configure conditional visibility for a sensitive financial section. Place the steps required to complete this task in the correct chronological sequence.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence to convert to Dynamic Forms and configure section visibility is: 1) Open the record page in Lightning App Builder, 2) Select the Record Detail component and click Upgrade Now, 3) Select the source page layout and complete the wizard, 4) Select the Field Section and configure Component Visibility filters, 5) Save and activate the Lightning Record Page.
Migrating to Dynamic Forms requires opening the record page in Lightning App Builder, selecting the Record Detail component to run the Upgrade Now wizard, picking a source page layout to extract fields/sections, applying component visibility filters to the decoupled section component, and finally saving and activating the page assignment.

Step-by-Step Solution

1
Navigate to Lightning App Builder for the target object page.
The record page canvas is available for editing.
Modifications to Lightning page components require opening the page in Lightning App Builder.
2
Select Record Detail component and start Upgrade Now.
The Dynamic Forms migration wizard opens.
Dynamic Forms upgrade is initiated from the properties pane of the existing Record Detail component.
3
Select source layout and finish the migration wizard.
The Record Detail component is replaced by individual Field Section and Field components on the canvas.
The wizard converts standard page layout sections and fields into granular Lightning components.
4
Add Component Visibility filter to the target Field Section.
The section display rules are established (e.g., conditional visibility based on User Profile or field value).
Granular component visibility can only be applied after fields and sections are converted to individual Lightning components.
5
Save and activate the Lightning Record Page.
The updated Dynamic Forms page becomes active for users.
Changes must be saved and assigned via activation rules to take effect for end users.

Key Concept

Procedural migration of standard page layouts to Dynamic Forms in Lightning App Builder to enable component-level conditional visibility.
Estimated Time:1m 30s
Question 1059Question

Pinnacle Aviation manages safety compliance using a custom object named Flight_Audit__c. The Organization-Wide Default (OWD) sharing setting for Flight_Audit__c is set to Private, and the administrator deselects the 'Grant Access Using Hierarchies' option for this object. A criteria-based sharing rule is configured to share high-risk audit records with a Public Group named 'Safety Reviewers'. A user assigned to the 'Safety Manager' role owns several high-risk audit records. The 'Safety Director' role sits directly above the 'Safety Manager' role in the role hierarchy. If a user in the 'Safety Director' role is not a member of the 'Safety Reviewers' Public Group, which statement correctly describes their access to these Flight_Audit__c records?

Show answer & explanation

Answer: They will not have access to the records owned by Safety Managers because disabling 'Grant Access Using Hierarchies' prevents vertical record access propagation up the role hierarchy.

Answer

Users in the Safety Director role will not have access to the records because disabling 'Grant Access Using Hierarchies' prevents vertical access inheritance up the role hierarchy for custom objects.
For custom objects, Salesforce allows administrators to uncheck the 'Grant Access Using Hierarchies' setting. When unchecked, record access does not automatically roll up to users higher in the role hierarchy. Since the Safety Director is neither the record owner nor a member of the target Public Group receiving the sharing rule, they receive no access to the Flight_Audit__c records owned by Safety Managers.

Step-by-Step Solution

1
Evaluate the baseline Organization-Wide Default (OWD) and custom object hierarchy setting.
The OWD for Flight_Audit__c is Private, meaning users only access records they own unless shared. 'Grant Access Using Hierarchies' is deselected.
For standard objects, hierarchy access is always enabled. For custom objects, deselecting 'Grant Access Using Hierarchies' stops users higher in the role hierarchy from automatically inheriting record access owned by or shared with subordinates.
2
Evaluate the Public Group sharing rule and role memberships.
The records are shared to the 'Safety Reviewers' Public Group, but the Safety Director is not a member of this Public Group.
Because hierarchy access is disabled on the object, access granted to a Public Group does not roll up to managers of group members.
3
Determine final effective access for the Safety Director.
The Safety Director has no implicit hierarchy access and no group sharing rule access, so they cannot access the records.
Without ownership, explicit sharing rules, or hierarchy access, the Private OWD blocks record access.

Key Concept

Impact of 'Grant Access Using Hierarchies' on Custom Object Record Access
Question 1060Question

A Salesforce Administrator at an agricultural technology enterprise needs to immediately revoke system login access for a departing sales operations coordinator. When trying to deactivate the user account, Salesforce displays an error message indicating that the user is currently designated as the Default Workflow User in Process Automation Settings. Which immediate action should the administrator take to prevent the user from logging in while maintaining system operational integrity?

Show answer & explanation

Answer: Freeze the user account to block login access immediately, then reassign the Default Workflow User setting before deactivating the user.

Answer

Freeze the user account to block login access immediately, then reassign the Default Workflow User setting before deactivating the user.
Freezing a user account immediately revokes login access without releasing the license or breaking functional dependencies. This allows administrators to stop user logins instantly while they update process references, such as the Default Workflow User setting, before permanently deactivating the account.

Step-by-Step Solution

1
Identify the immediate requirement and system bottleneck
Login access must be revoked immediately, but direct deactivation is blocked because the user is assigned as the Default Workflow User.
Salesforce prevents deactivation of users tied to specific hierarchy roles, default owners, or system settings such as Default Workflow User.
2
Apply the appropriate user management tool for immediate access revocation
Freeze the user account from the User detail page.
Freezing blocks login access right away without requiring the removal of active references or configuration dependencies.
3
Resolve configuration dependencies and finalize account status
Reassign the Default Workflow User setting to an active user, then deactivate the original user account.
Once the configuration reference is cleared, deactivation can be completed to free up the user license.

Key Concept

Distinction between freezing and deactivating users when system configuration dependencies exist
Estimated Time:1m 15s
PreviousPage 53 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin