All practice questions

1784 questions

All types1,784 Multiple choice918 Multiple select587 Matching142 Ordering137

Match each Salesforce security requirement on the left with the correct administration configuration mechanism on the right.

Click a left item, then click its matching right item

Show answer & explanation

Answer

1. Field access restriction across all interfaces maps to Field-Level Security on Profiles/Permission Sets. 2. Record deletion restriction maps to Profile Object Permissions. 3. Conditional page field hiding maps to Dynamic Forms Component Visibility. 4. Time-restricted login access maps to Profile Login Hours.

Each security requirement correctly aligns with its architectural layer in Salesforce: Field-Level Security (FLS) enforces data visibility at the API/database layer; Profile Object Permissions control object-level CRUD actions; Dynamic Forms manage conditional layout rendering; and Profile Login Hours govern user authentication timing windows.

Step-by-Step Solution

Analyze field-level security vs UI display requirements.

Hiding a field across API, reports, and layouts requires Field-Level Security (FLS), whereas conditional UI display uses Dynamic Forms.

FLS guarantees strict data security at the schema level, while Dynamic Forms only affect page rendering.

Evaluate record-level action permissions (CRED).

Preventing record deletion requires removing the Delete permission on the Object Permissions settings in the Profile.

Object permissions grant baseline Create, Read, Edit, and Delete access on custom and standard objects.

Evaluate authentication and login security constraints.

Restricting access based on time of day is configured via Login Hours under Profile settings.

Key Concept

Salesforce Security Architecture: Profile Object Permissions, Field-Level Security, Login Hours, and Dynamic Forms Visibility

Question 1082Question →

A Service Cloud administrator at an enterprise cybersecurity hardware firm is investigating why high-priority support cases fail to escalate to the Tier-2 Support queue within the required 4-hour Service Level Agreement (SLA). The administrator verifies that the active Escalation Rule entry criteria correctly identify open, high-priority cases and that the escalation action is set to reassign ownership after 4 hours. However, support agents regularly edit field values and append internal notes during their initial review, which prevents the escalation action from executing at the expected 4-hour mark after case creation. What configuration change should the administrator make to ensure cases escalate 4 hours after initial creation?

Update the Escalation Rule entry setting to calculate case age based on case creation date rather than last modified date.

Reorder the system rule hierarchy to place Escalation Rules before Case Assignment Rules in the order of execution.

Configure an active Case Auto-Response Rule entry to lock the case modified timestamp whenever internal updates occur.

Create a before-save Record-Triggered Flow to bypass Escalation Rules and evaluate case modified timestamps synchronously.

Show answer & explanation

Answer: Update the Escalation Rule entry setting to calculate case age based on case creation date rather than last modified date.

Answer

Update the Escalation Rule entry setting to calculate case age based on case creation date rather than last modified date.

The correct option addresses the root cause of the SLA failure. In Salesforce Case Escalation Rules, 'How age is calculated' can be based on Case Creation Date, Last Modified Date, or a custom Date/Time field. If set to Last Modified Date, frequent edits by agents continually reset the escalation timer, preventing the 4-hour threshold from ever being reached. Setting it to Case Creation Date ensures uninterrupted tracking from initial case entry.

Step-by-Step Solution

Analyze the escalation behavior.

Identified that case updates by support agents reset the escalation clock.

When 'How age is calculated' is set to 'Based on last modified date', any edit modifies the SystemModstamp/LastModifiedDate, resetting the elapsed time counter.

Evaluate the SLA requirement.

The business requirement specifies that cases must escalate 4 hours after initial creation regardless of agent interaction.

Calculating age based on creation date maintains a fixed countdown independent of intermediate edits.

Select the appropriate Escalation Rule configuration.

Modify the rule entry setting for age calculation to 'Based on case creation date'.

This guarantees that the escalation action fires exactly 4 hours after the case record is created.

Key Concept

Escalation Rule Age Calculation Settings

Estimated Time:2m 0s

Question 1083Question →

A Salesforce administrator at an agricultural equipment dealership is configuring schema elements to support a new equipment maintenance tracking initiative. When evaluating the capabilities and characteristics of standard objects compared to custom objects, which two statements are accurate? (Select 2)

Select all that apply

Standard objects cannot be deleted from the Salesforce organization schema.

Standard fields on standard objects can have their data types modified by an administrator.

Standard objects can serve as the detail record in a master-detail relationship with a custom object as the master.

Standard fields on standard objects cannot be deleted, but their field labels can be renamed.

Show answer & explanation

Answer: Standard objects cannot be deleted from the Salesforce organization schema.; Standard fields on standard objects cannot be deleted, but their field labels can be renamed.

Answer

Standard objects cannot be deleted from the organization schema, and standard fields on standard objects cannot be deleted, though their display labels can be customized.

Standard objects are built directly into Salesforce and cannot be deleted from the organization schema. Similarly, standard fields on standard objects cannot be deleted or have their data types changed, but administrators can rename their display labels to meet business needs.

Step-by-Step Solution

Evaluate standard object schema capabilities.

Standard objects are permanent components of Salesforce core functionality and cannot be deleted.

Core standard objects (such as Account, Contact, and Opportunity) are required system elements.

Analyze standard field customization rules.

Standard fields cannot be deleted or have their data types changed, but their labels can be renamed to match business terminology.

Salesforce protects data integrity by locking standard field definitions while allowing user-facing label customization.

Verify object relationship restrictions.

Standard objects cannot sit on the child (detail) side of a master-detail relationship with a custom master object.

Platform architecture prohibits standard objects from being owned by custom objects in master-detail definitions.

Key Concept

Standard vs Custom Object Schema Capabilities and Limits

Question 1084Question →

An organization is establishing a Chatter group for a confidential project. The administrator must ensure that non-members cannot search for or request to join the group. Furthermore, to minimize feed clutter, standard group members must be able to view and comment on posts, but only the group owner and managers should be permitted to create new posts. Which combination of Chatter group configuration options satisfies all of these security and collaboration requirements?

Create an Unlisted Chatter group and select the Broadcast Only checkbox in the group settings.

Create a Private Chatter group, disable Feed Tracking on the Group object, and assign the Manage Unlisted Groups permission set to standard members.

Create a Private Chatter group, select Broadcast Only, and assign a custom profile with Read-Only Chatter permissions to standard group members.

Create an Unlisted Chatter group and freeze the user accounts of standard group members within the Chatter Group member management subtab.

Show answer & explanation

Answer: Create an Unlisted Chatter group and select the Broadcast Only checkbox in the group settings.

Answer

Create an Unlisted Chatter group and select the Broadcast Only checkbox in the group settings.

The correct response combines an Unlisted Chatter group with the Broadcast Only setting. Unlisted groups ensure that non-members cannot see posts, search for the group, or request to join. The Broadcast Only setting restricts post creation exclusively to group owners and managers while still allowing members to reply with comments.

Step-by-Step Solution

Analyze privacy requirement

Identify that the group must be completely hidden from non-members and prohibit request-to-join actions.

Unlisted groups provide complete privacy by hiding the group from search results and member lists for non-members, whereas Private groups are discoverable in search.

Analyze communication requirement

Identify the setting that restricts initial post creation to owners and managers while allowing standard members to comment.

The 'Broadcast Only' (or Broadcast) group setting specifically limits post creation rights to Owners and Managers.

Combine features

Select the configuration combining Unlisted group access with Broadcast Only setting.

This precise combination satisfies both the strict privacy requirement and the communication feed control requirement.

Key Concept

Chatter Unlisted Groups and Broadcast Group Settings

Question 1085Question →

Match each Salesforce Case Capture configuration component or feature to its primary administrative function.

Click a left item, then click its matching right item

Show answer & explanation

Answer

Default Case Owner matches assigning cases when assignment rules fail; reCAPTCHA Verification matches preventing spam/bot submissions on public forms; Default Case Origin matches populating the Case Origin picklist value; Email-to-Case Routing Address matches providing an alias destination for forwarded support emails.

Each feature corresponds strictly to its administrative setting in Salesforce Case Capture setup: Default Case Owner acts as a fallback when assignment rules fail; reCAPTCHA prevents spam submissions on Web-to-Case forms; Default Case Origin establishes the channel picklist value; and Routing Addresses process forwarded emails into cases.

Step-by-Step Solution

Identify the role of Default Case Owner in case capture.

It serves as the fallback owner (user or queue) when rule-based assignment does not match.

Prevents cases from becoming unassigned or lost upon capture.

Identify the purpose of reCAPTCHA Verification.

It authenticates human interaction on public web forms before sending data to Salesforce.

Protects Web-to-Case intake endpoints against automated spam scripts.

Identify the purpose of Default Case Origin.

It defines the initial channel picklist value (such as Web or Email) assigned to newly captured records.

Provides accurate channel tracking for incoming cases.

Identify the purpose of an Email-to-Case Routing Address.

It generates an automated email address that receives customer emails and converts them into cases.

Connects external company support email addresses with Salesforce Apex Email Processing.

Key Concept

Salesforce Case Capture Configuration and Administration

Estimated Time:1m 0s

Question 1086Question →

An administrator at Starlight Manufacturing needs to configure Chatter collaboration and feed tracking for a custom object named Equipment_Maintenance__c. The operations team requires automated Chatter feed posts whenever maintenance status or assigned technician fields change, as well as global quick actions accessible from the main Chatter feed.

Which two administration rules and behaviors must the administrator consider when setting up this configuration? (Select two)

Select all that apply

Feed tracking allows up to 20 total fields to be selected per object, automatically generating feed updates when those field values change.

Enabling feed tracking on an object automatically overrides Organization-Wide Defaults, allowing users to view feed posts for records they cannot otherwise access.

Global Publisher Layouts determine the global quick actions available on global Chatter feeds, such as the Home tab and Chatter tab.

A custom field must be set as universally required before it can be selected for Chatter feed tracking.

Global Publisher Layouts directly override and replace Object Page Layouts for action placement on record detail pages.

Show answer & explanation

Answer: Feed tracking allows up to 20 total fields to be selected per object, automatically generating feed updates when those field values change.; Global Publisher Layouts determine the global quick actions available on global Chatter feeds, such as the Home tab and Chatter tab.

Answer

The two correct statements are that Feed Tracking supports up to 20 fields per object to generate automated feed updates, and Global Publisher Layouts customize quick actions on global feeds such as the Home and Chatter tabs.

Feed tracking enables administrators to select up to 20 standard or custom fields per object to generate automatic feed posts when modified. Additionally, Global Publisher Layouts control the quick actions accessible on global Chatter feeds (such as on the Home page and Chatter tab), preserving a clear functional boundary from object-specific page layouts.

Step-by-Step Solution

Evaluate Chatter Feed Tracking limits and behavior

Confirm that Chatter Feed Tracking allows selecting up to 20 fields per standard or custom object. Changes to these fields create automated feed items while respecting record sharing security.

Salesforce enforces a strict 20-field tracking limit per object and preserves underlying data security.

Evaluate Global Publisher Layout scope vs Object Page Layout scope

Determine that Global Publisher Layouts dictate publisher quick actions on global feeds (Home tab, Chatter tab, User profile), whereas record detail page actions are controlled by object page layouts.

Global publisher layouts govern global quick actions, whereas object page layouts manage object record page actions.

Key Concept

Chatter Feed Tracking limits (maximum 20 fields per object) and Global Publisher Layout scope vs Object Page Layout scope.

Question 1087Question →

Universal Containers plans to launch a self-service Experience Cloud site for customer support. The administrator needs to allow logged-in portal users to view their own support cases and access public Knowledge articles. Which two actions should the administrator take to fulfill these requirements?

Select all that apply

Assign permission sets to external users to grant object-level access to Cases and Knowledge.

Configure Sharing Sets to grant portal users access to Cases associated with their Account or Contact.

Create separate custom profiles for each portal user to grant unique additive permissions.

Disable 'Grant Access Using Hierarchies' on standard objects to restrict external record access.

Restrict Data Category visibility settings so portal users cannot view published Knowledge articles.

Show answer & explanation

Answer: Assign permission sets to external users to grant object-level access to Cases and Knowledge.; Configure Sharing Sets to grant portal users access to Cases associated with their Account or Contact.

Answer

The administrator should assign permission sets to grant object-level access to Cases and Knowledge, and configure Sharing Sets to grant access to Cases associated with the user's Account or Contact.

To expose cases and self-service Knowledge articles in Experience Cloud, administrators must grant object permissions via permission sets and establish record-level access using Sharing Sets mapped to the user's Account or Contact.

Step-by-Step Solution

Grant object-level permissions

External portal users are granted Read permissions on Cases and Knowledge.

Users must have object-level permissions before they can access any individual records.

Configure Sharing Sets for record access

Portal users automatically gain access to Case records linked to their Contact or Account.

Sharing Sets provide automated record-level access for high-volume Experience Cloud users.

Key Concept

Experience Cloud Security and Sharing Sets

Question 1088Question →

A System Administrator at a financial consulting firm is configuring a Salesforce Campaign to track participant engagement for an upcoming executive summit. The marketing team added custom Campaign Member Status values: 'Invited', 'Registered', and 'Attended'. However, campaign performance metrics show that contacts marked as 'Attended' are not being counted toward Total Responses on campaign reports, whereas contacts marked as 'Registered' are incorrectly increasing the response count. Which administrative action should the System Administrator take to resolve this reporting issue?

Edit the Campaign Member Status values for the campaign, checking the 'Responded' box for 'Attended' and unchecking it for 'Registered'.

Modify Organization-Wide Defaults for Campaigns to set the default response status automatically to 'Attended'.

Update the Lead Conversion Field Mapping to map the custom Campaign Member Status field to the Opportunity Stage field.

Add the 'Attended' value to the standard Lead Status picklist to allow automatic recalculation of campaign responses.

Show answer & explanation

Answer: Edit the Campaign Member Status values for the campaign, checking the 'Responded' box for 'Attended' and unchecking it for 'Registered'.

Answer

Edit the Campaign Member Status values for the campaign, ensuring the 'Responded' checkbox is enabled for 'Attended' and disabled for 'Registered'.

In Salesforce, Campaign Member Status values include a 'Responded' checkbox setting. Any member whose status has the 'Responded' box checked is counted in aggregate campaign metrics such as Total Responses. To fix the issue where 'Attended' is not counted and 'Registered' is incorrectly counted, the administrator must edit the campaign member statuses to enable the 'Responded' checkbox for 'Attended' and disable it for 'Registered'.

Step-by-Step Solution

Identify how Salesforce calculates campaign responses.

Salesforce tracks responses based on the boolean 'Responded' flag assigned to each Campaign Member Status value.

Only status values marked as 'Responded' increment response metrics such as Total Responses and Response Rate on Campaign records and reports.

Navigate to the Campaign Member Statuses setup for the campaign.

Access the list of status values associated with the campaign.

Individual status flags can be customized per campaign or set up as organization defaults.

Adjust the 'Responded' checkbox configuration.

Check 'Responded' for 'Attended' and uncheck 'Responded' for 'Registered'.

This aligns reporting metrics with actual engagement, ensuring only members who actively attended count as responded.

Key Concept

Campaign Member Status Responded Flag Configuration

Question 1089Question →

A sales representative at a global consulting firm frequently collaborates with the same Sales Engineer and Product Specialist on complex sales deals. The Organization-Wide Default (OWD) for Opportunities is Private. The sales representative wants these two colleagues to automatically gain Read/Write access to every new opportunity record the representative creates, avoiding the need to manually add them to each deal individually. Which administrative configuration or user setting fulfills this requirement with the least administrative effort?

Instruct the sales representative to set up a Default Opportunity Team in their personal user settings and enable automatic addition to new opportunities.

Create a criteria-based Sharing Rule on the Opportunity object that shares records owned by the sales representative with a Public Group containing the colleagues.

Assign a custom Permission Set to the colleagues granting Modify All permission on the Opportunity object.

Add the colleagues to the parent Account Team and rely on standard Account Team member access propagation to grant edit permissions on all child opportunities.

Show answer & explanation

Answer: Instruct the sales representative to set up a Default Opportunity Team in their personal user settings and enable automatic addition to new opportunities.

Answer

The sales representative should configure a Default Opportunity Team within their personal settings and enable the option to automatically add the team to newly created opportunities.

Configuring a Default Opportunity Team in personal settings allows the user to specify default team members, roles, and access levels (such as Read/Write). Setting the option to automatically add the default team ensures every new opportunity created by the sales representative automatically shares access with the specified team members.

Step-by-Step Solution

Identify the requirement

The goal is to automatically grant specific team members Read/Write access to newly created opportunities owned by a specific sales representative.

The user seeks an automated, record-owner specific method to share opportunities without manual repetitive steps.

Evaluate Salesforce Team Selling capabilities

Salesforce allows individual users to define a Default Opportunity Team under Advanced User Details in personal settings.

Default Opportunity Teams let users specify team members, roles, and opportunity access levels (e.g., Read/Write) to automatically apply whenever they create a deal.

Distinguish from administrative record-sharing mechanisms

System-wide sharing rules or permission sets either grant excessive permissions or require ongoing administrative setup for personal workflows.

Default Opportunity Teams empower end users to manage their collaboration partners directly without admin intervention.

Key Concept

Default Opportunity Teams allow users to define a recurring group of collaborators with specific access levels that can be added manually or automatically to opportunities they own.

Question 1090Question →

A System Administrator at a solar equipment manufacturer needs to configure automated case handling in Salesforce Service Cloud. When a customer submits a new case, it must immediately be assigned to a designated Tier 1 support queue. If a high-priority case remains open and unresolved after 4 hours, the system must reassign the case to the Tier 2 management queue and send an alert to the support supervisor.

Which two automated rule types should the administrator configure to meet these requirements? (Select 2 answers)

Select all that apply

Case Assignment Rule to route newly logged cases to the Tier 1 support queue based on criteria upon creation.

Case Escalation Rule to reassign open cases to Tier 2 management after 4 hours and send a notification email.

Case Escalation Rule to perform initial routing of newly logged cases to Tier 1 support queues upon case creation.

Auto-Response Rule to reassign high-priority unresolved cases to the Tier 2 management queue after 4 hours.

Show answer & explanation

Answer: Case Assignment Rule to route newly logged cases to the Tier 1 support queue based on criteria upon creation.; Case Escalation Rule to reassign open cases to Tier 2 management after 4 hours and send a notification email.

Answer

The administrator should configure a Case Assignment Rule for initial routing of new cases to Tier 1 queues, and a Case Escalation Rule to handle the time-based reassignment to Tier 2 management along with supervisor notification.

Case Assignment Rules set initial ownership when cases are created, directing them to the Tier 1 support queue. Case Escalation Rules continuously monitor open cases against defined SLA thresholds (such as 4 hours unresolved) and execute escalation actions to reassign ownership to Tier 2 management and send notifications.

Step-by-Step Solution

Determine the tool required for initial case routing at creation.

Identify Case Assignment Rules as the standard mechanism for evaluating new cases and assigning queue ownership upon creation.

Case Assignment Rules run when a case is submitted to assign it to an individual or queue.

Determine the tool required for time-triggered re-routing and notification.

Identify Case Escalation Rules as the mechanism for monitoring open cases and triggering actions after specified time thresholds.

Case Escalation Rules track time elapsed (such as 4 hours since creation) and perform actions like record reassignment and notification.

Key Concept

Distinction between Case Assignment Rules (initial ownership routing on creation) and Case Escalation Rules (time-triggered actions for open cases).

Question 1091Question →

A Salesforce Administrator is tasked with configuring Entitlement Management with Milestone tracking to enforce Service Level Agreements (SLAs) for customer support cases. In what sequence should the administrator complete the setup steps to ensure milestones and automated actions function properly?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of setup steps is: 1) Enable Entitlement Management in Organization Setup, 2) Create master Milestones, 3) Create an Entitlement Process, add the Milestones, and configure Warning and Violation actions, 4) Activate the Entitlement Process, and 5) Create a customer Entitlement record and assign the active Entitlement Process to it.

Configuring Entitlement Management with Milestones follows a strict dependency order in Salesforce. First, Entitlement Management must be enabled in Organization Setup. Second, master Milestones must be created so that milestone types are available. Third, the administrator creates an Entitlement Process, adds those master milestones, and sets up milestone actions (such as warning emails or escalation tasks). Fourth, the Entitlement Process must be activated. Fifth and finally, the active process is assigned to customer Entitlement records so incoming cases trigger SLA milestone tracking.

Step-by-Step Solution

Enable Entitlement Management

Unlocks Entitlement Management objects, settings, and administration menus in Salesforce Setup.

Entitlement processes and milestone objects are unavailable until the feature is explicitly enabled in Setup.

Create master Milestones

Establishes reusable milestone definitions in the org.

Milestone records act as templates and must exist prior to referencing them inside an entitlement process.

Build Entitlement Process & add Milestone Actions

Defines SLA rules, target resolution times, warning notifications, and violation escalations.

Processes define the business logic for when milestones apply and what automated actions execute upon success, warning, or violation.

Activate the Entitlement Process

Changes process status to Active and locks version details.

Salesforce prevents inactive entitlement processes from being linked to customer entitlement records or active cases.

Assign process to Customer Entitlement record

Enables milestone tracking for all newly created cases associated with that customer entitlement.

Cases inherit milestone tracking timelines directly from their assigned entitlement record.

Key Concept

Entitlement Management Setup Workflow

Question 1092Question →

An administrator created a new Record Type named 'Internal Audit' on the Case object to support a specialized compliance team. The administrator created a dedicated page layout and updated the Page Layout Assignment matrix for the Compliance User profile. However, when Compliance Users create a case using the 'Internal Audit' record type, they observe that the custom 'Audit Status' picklist field displays all available values in the org rather than the restricted subset intended for compliance tracking. Which configuration step did the administrator omit?

Editing the Picklists Available for Editing section on the Internal Audit record type configuration page.

Assigning the custom page layout through a Permission Set assigned to the Compliance Users.

Configuring field value visibility filters within the Dynamic Forms component settings.

Associating the record type with a dedicated Sales Process before updating page layouts.

Show answer & explanation

Answer: Editing the Picklists Available for Editing section on the Internal Audit record type configuration page.

Answer

The administrator omitted editing the Picklists Available for Editing section on the Internal Audit record type configuration page.

In Salesforce, Record Types control the availability of picklist values independently of Page Layouts. When a new Record Type is generated, all existing picklist values remain enabled by default. To restrict options, the administrator must edit the 'Picklists Available for Editing' section on the specific Record Type detail page in Object Manager.

Step-by-Step Solution

Analyze why all picklist values are visible despite assigning a dedicated page layout.

Page layouts govern field presence and positioning, whereas Record Types govern which picklist values are available for selection.

Page layout assignment does not filter individual values within a picklist field.

Identify the correct administrative path to restrict picklist values for a specific record type.

In Object Manager, navigate to Case > Record Types > Internal Audit, and select Edit next to the Audit Status picklist in the 'Picklists Available for Editing' section.

Newly created record types automatically inherit all active picklist values until explicitly configured.

Key Concept

Picklist Value Assignment per Record Type

Estimated Time:1m 15s

Question 1093Question →

Cloud Kicks wants to grant external users on its public Experience Cloud site access to search and view published Knowledge articles without requiring them to log in. Which action should the administrator take in Experience Builder to meet this requirement?

Enable Public Access in the Experience Builder site settings.

Create a custom profile for guest users and assign additive object permissions via permission sets.

Enable Grant Access Using Hierarchies on the Knowledge object under Organization-Wide Defaults.

Change the default Case Assignment Rule to assign unauthenticated requests to the Guest User.

Show answer & explanation

Answer: Enable Public Access in the Experience Builder site settings.

Answer

Enable Public Access in the Experience Builder site settings to allow unauthenticated site visitors to view published Knowledge articles.

Enabling Public Access in Experience Builder settings allows unauthenticated site visitors to access public pages and view published Knowledge articles without needing credentials.

Step-by-Step Solution

Identify the access requirement for unauthenticated portal visitors.

Unauthenticated visitors interact with an Experience Cloud site via the Guest User Profile.

Public access must be explicitly enabled for an Experience Cloud site to allow guest users to view pages without logging in.

Configure site access settings in Experience Builder.

Enabling Public Access in General Settings grants unauthenticated visitors access to published articles exposed on public pages.

This single configuration setting toggles public page visibility for unauthenticated users.

Key Concept

Experience Cloud Site Public Access for Self-Service Knowledge

Question 1094Question →

A Salesforce Administrator at an enterprise software firm needs to model a data structure to track software license allocations across corporate departments. A single software license can be allocated to multiple departments, and a single department can hold allocations for multiple software licenses. Each allocation must record unique metadata such as seat count and allocation date. Furthermore, if either a software license or a department record is deleted, its associated allocation records must be automatically removed. Which two configuration steps should the administrator take to fulfill these requirements? (Select 2 answers.)

Select all that apply

Create a custom junction object with two Master-Detail relationship fields linking to the Software License and Department objects.

Add custom fields for seat count and allocation date directly onto the custom junction object.

Create a custom junction object with two Lookup relationship fields to ensure allocation records are preserved if a parent record is deleted.

Create Roll-Up Summary fields on the Department object pointing directly to a Lookup relationship on the Software License object.

Show answer & explanation

Answer: Create a custom junction object with two Master-Detail relationship fields linking to the Software License and Department objects.; Add custom fields for seat count and allocation date directly onto the custom junction object.

Answer

To model a many-to-many relationship with automatic cascade deletion, the administrator must create a custom junction object containing two Master-Detail relationship fields (referencing Software License and Department) and place the allocation-specific fields (seat count and allocation date) directly on that junction object.

A many-to-many relationship in Salesforce requires a custom junction object. Using two Master-Detail relationship fields ensures that deleting either a Software License or a Department record automatically deletes the associated allocation record. Storing seat count and allocation date on the junction object properly captures metadata specific to each allocation.

Step-by-Step Solution

Identify the relationship requirements between Software License and Department.

Since both objects have a multi-directional relationship (many-to-many), a custom junction object is required.

Salesforce handles many-to-many data modeling via a junction object.

Determine the appropriate relationship field types.

Use Master-Detail relationships from the junction object to both parent objects.

Master-Detail relationships enforce cascading record deletion when a master record is deleted and enable roll-up summary functionality.

Define where relationship-specific metadata fields should reside.

Place seat count and allocation date custom fields on the custom junction object.

Attributes specific to the intersection/allocation of the two entities must be stored on the junction object.

Key Concept

Junction Objects and Master-Detail Relationship Rules

Question 1095Question →

Universal Containers installed a productivity-focused managed package from the AppExchange to streamline proposal generation. The Salesforce administrator needs to grant access to this tool exclusively to select account executives across three different departments, without granting access to other users who share those executives' existing profiles. Which administrator action meets this requirement?

Assign the permission set included with the AppExchange package directly to the designated account executives.

Clone each department's existing profile, enable the package object permissions on the new profiles, and reassign the account executives.

Modify the organization's standard profiles to grant custom object permissions for the managed package to all account executives.

Deactivate the target account executives' existing user records and create new user records assigned to a specialized AppExchange profile.

Show answer & explanation

Answer: Assign the permission set included with the AppExchange package directly to the designated account executives.

Answer

Assign the permission set included with the AppExchange package directly to the designated account executives.

AppExchange managed packages generally come with pre-built permission sets that grant the necessary permissions for the package's objects, components, and apex classes. Assigning these permission sets directly to specific users across different departments provides the needed access cleanly without creating additional profiles or modifying existing baseline profiles.

Step-by-Step Solution

Identify the target user access requirements

Selective access is required for specific users spanning multiple baseline profiles.

Profiles control baseline access for groups of users, whereas selective access across disparate profiles requires additive entitlement.

Evaluate AppExchange package access components

Managed packages typically include custom permission sets pre-configured with object and field access.

Managed package components use permission sets to allow flexible administrative deployment.

Assign the package permission set to the selected users

Target account executives receive the required access while maintaining their existing profiles.

Permission sets provide targeted, additive permissions to individual users without requiring redundant profile creation.

Key Concept

AppExchange Package Access Management via Permission Sets

Estimated Time:1m 15s

Question 1096Question →

An administrator is configuring Salesforce Knowledge for an internal IT Help Desk team that needs to view specialized troubleshooting documentation. Although the articles are published, active, and assigned to the 'IT Infrastructure' Data Category group, the technicians report that they cannot locate or view any of these articles. The administrator has already verified that the Knowledge User feature license is enabled and that object-level Read permission is granted. What is the most likely cause of this visibility issue?

The Data Category visibility for the 'IT Infrastructure' group is set to None on the technicians' assigned roles, permission sets, or profiles.

The technicians were assigned a permission set rather than modifying their profile settings to grant object access.

The 'IT Infrastructure' category was omitted from the available picklist values on the Knowledge object record type.

The Organization-Wide Default (OWD) sharing setting for the Knowledge object is configured as Public Read-Only.

Show answer & explanation

Answer: The Data Category visibility for the 'IT Infrastructure' group is set to None on the technicians' assigned roles, permission sets, or profiles.

Answer

The Data Category visibility for the 'IT Infrastructure' group is set to None on the technicians' assigned roles, permission sets, or profiles.

Data Category visibility determines which categorized articles a user can view. When category group access is set to None within a user's role hierarchy, permission set, or profile settings, articles categorized under that group remain invisible regardless of article publication status or general object permissions.

Step-by-Step Solution

Analyze Knowledge Visibility Components

Access to Knowledge articles requires a Knowledge User license, object permissions, and explicit Data Category visibility.

When feature licenses and object permissions are active but articles in a specific category cannot be found, Data Category settings are the determining factor.

Evaluate Data Category Visibility Configuration

Data Category visibility controls article access based on user role hierarchy, permission sets, or profiles (All, Custom, or None).

If the Data Category visibility is set to None for a given group, users are unable to search for or view any articles classified under that category.

Key Concept

Salesforce Knowledge Data Category Visibility

Question 1097Question →

An administrator needs to enable sales representatives to log emails directly from Microsoft Outlook to Salesforce records and use standardized email templates containing record merge fields. Which TWO configurations should the administrator perform to satisfy these requirements? (Select 2 options)

Select all that apply

Enable the Outlook Integration in Salesforce Setup to allow users to view and log emails to Salesforce records directly from Microsoft Outlook.

Create separate user profiles for each sales representative to grant access to the Outlook integration side panel.

Create Lightning Email Templates and place them in public or shared template folders for sales reps to access.

Enable Shared Activities to automatically grant user-level read/write permissions to email template folders.

Freeze the user accounts of all sales reps to force the integration side panel to update template permissions automatically.

Show answer & explanation

Answer: Enable the Outlook Integration in Salesforce Setup to allow users to view and log emails to Salesforce records directly from Microsoft Outlook.; Create Lightning Email Templates and place them in public or shared template folders for sales reps to access.

Answer

The administrator must enable the Outlook Integration in Salesforce Setup and create Lightning Email Templates in shared folders accessible to the sales team.

Enabling the Outlook Integration feature provides the user interface link between Outlook and Salesforce, allowing users to log messages and view related records. Storing Lightning Email Templates in shared folders ensures users have the necessary permissions to select and send standardized template messages.

Step-by-Step Solution

Turn on Outlook Integration in Setup.

Sales representatives gain the ability to view Salesforce data and log emails directly within Microsoft Outlook.

This is the required core setting that connects Outlook to the Salesforce environment.

Configure Lightning Email Templates in shared folders.

Reps can access, insert, and send consistent email communications containing field merge data.

Email templates must reside in folders with appropriate sharing permissions for sales reps to select them.

Key Concept

Salesforce Outlook Integration and Email Template Folder Management

Question 1098Question →

An administrator at Meridian Health needs to configure Chatter collaboration and feed update functionality for a custom object named Vendor_Audit__c. The compliance team requires automatic Chatter feed updates whenever the Audit_Status__c or Compliance_Score__c fields are modified on an audit record. Furthermore, users must be able to log a new Vendor_Audit__c record directly from the global Chatter feed publisher on their home page, but the action is currently not visible in their publisher menu. Which TWO configuration steps must the administrator take to fulfill these requirements? (Select TWO)

Select all that apply

Navigate to Feed Tracking in Setup, enable feed tracking for the Vendor_Audit__c object, and check the boxes for Audit_Status__c and Compliance_Score__c.

Edit the assigned Global Publisher Layout in Setup and add the Create a Record Quick Action for Vendor_Audit__c to the Salesforce Mobile and Lightning Experience Actions section.

Configure a custom Chatter Group for Vendor_Audit__c and enable Auto-Feed Post Generation under Group Settings for untracked object fields.

Modify the Vendor_Audit__c standard Object Page Layout to include the Global Publisher component within the details section.

Enable Feed Tracking under User Profile System Permissions to override object-level Chatter feed tracking limits.

Show answer & explanation

Answer: Navigate to Feed Tracking in Setup, enable feed tracking for the Vendor_Audit__c object, and check the boxes for Audit_Status__c and Compliance_Score__c.; Edit the assigned Global Publisher Layout in Setup and add the Create a Record Quick Action for Vendor_Audit__c to the Salesforce Mobile and Lightning Experience Actions section.

Answer

The administrator must enable Feed Tracking for the Vendor_Audit__c object in Setup while selecting the Audit_Status__c and Compliance_Score__c fields, and edit the Global Publisher Layout to include the Vendor_Audit__c quick action in the Salesforce Mobile and Lightning Experience Actions section.

To automatically track field changes in record Chatter feeds, an administrator must enable Feed Tracking on the object and check the specific fields to monitor (Audit_Status__c and Compliance_Score__c). To display quick actions in global Chatter feed publishers, the quick action must be added to the assigned Global Publisher Layout under the Salesforce Mobile and Lightning Experience Actions section.

Step-by-Step Solution

Enable object and field level Feed Tracking

System automatically generates feed posts on record updates

Salesforce requires Feed Tracking to be explicitly enabled on a per-object basis in Setup, with up to 20 specific fields selected to trigger feed posts upon field changes.

Customize the Global Publisher Layout

The quick action becomes accessible in the global Chatter feed publisher

Global Publisher Layouts define the actions accessible in the Chatter publisher on global pages like Home and Chatter feeds. Adding the record creation quick action to the Salesforce Mobile and Lightning Experience Actions section exposes it to users.

Key Concept

Chatter Feed Tracking configuration and Global Publisher Layout action placement

Estimated Time:2m 0s

Question 1099Question →

CloudKicks uses an Experience Cloud site to provide self-service support to external customers who hold standard Customer Community licenses. The support team requires that external users be able to view and update all Cases submitted by any contact affiliated with their parent Account. Because standard Customer Community license holders cannot be assigned roles or benefit from standard criteria-based sharing rules, which configuration mechanism must the administrator implement to grant case access across the account?

Configure a Sharing Set mapping the User's Contact Account to the Case Account object for the Customer Community user profile.

Set the Case External Org-Wide Default to Public Read/Write and enable Grant Access Using Hierarchies on the Case sharing settings.

Create a custom Profile for external users and enable the View All permission on the Case object.

Create a Criteria-Based Sharing Rule that shares cases where Case Account equals the user's Account with the portal user group.

Show answer & explanation

Answer: Configure a Sharing Set mapping the User's Contact Account to the Case Account object for the Customer Community user profile.

Answer

Configure a Sharing Set mapping the User's Contact Account to the Case Account object for the Customer Community user profile.

Sharing Sets are specifically designed for high-volume Experience Cloud user licenses (Customer Community) that do not support roles. By configuring a Sharing Set, the administrator maps the user's Contact Account field to the Account lookup on the Case object, granting users access to all cases created within their account.

Step-by-Step Solution

Analyze license capabilities and constraints

Identify that Customer Community licenses are high-volume portal licenses that do not utilize Salesforce roles or standard owner-based/criteria-based sharing rules.

High-volume portal user licenses require specialized sharing mechanisms to maintain low overhead and high performance.

Evaluate record sharing requirements

Determine that external users need access to Case records related to their parent Account.

The business requirement demands cross-contact visibility within the same account boundary.

Select the appropriate Experience Cloud sharing feature

Implement a Sharing Set mapping User:Contact.Account to Case:Account.

Sharing Sets grant high-volume community users record access based on common account or contact relationships defined in their user profile.

Key Concept

Experience Cloud Sharing Sets for High-Volume External Users

Estimated Time:2m 0s

Question 1100Question →

Match each Salesforce AppExchange package type or solution to its primary operational characteristic.

Click a left item, then click its matching right item

Show answer & explanation

Answer

Managed Package pairs with protected code and publisher-pushed upgrades; Unmanaged Package pairs with fully editable code without direct upgrades; Salesforce Labs Solution pairs with free, employee-created open-source tools.

Each AppExchange distribution model fulfills specific architecture requirements: Managed packages protect intellectual property and allow continuous upgrades; Unmanaged packages provide customizable baseline code without upgrade paths; Salesforce Labs offers free, employee-built productivity utilities.

Step-by-Step Solution

Identify the characteristics of Managed Packages on AppExchange.

Managed packages lock the underlying components and Apex code to protect IP while allowing seamless version updates.

Independent Software Vendors (ISVs) use managed packages to distribute commercial products that need ongoing maintenance.

Identify the characteristics of Unmanaged Packages.

Unmanaged packages install all components as native, fully editable assets within the target org.

They serve as starter templates for customization and do not support publisher updates.

Identify the characteristics of Salesforce Labs solutions.

Salesforce Labs apps are free, open-source solutions created by internal Salesforce employees.

These solutions help administrators address common productivity gaps, though they rely on community support.

Key Concept

AppExchange Package Characteristics and Solution Types

PreviousPage 55 / 90Next

All practice questions

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Answer

Step-by-Step Solution

Key Concept