All practice questions

1784 questions

Question 1161Question

A software quality engineering team requires a dedicated space in Salesforce for discussing pre-release bug findings. The group must restrict post and file visibility exclusively to members who have been added to the space. Additionally, the group creator wants to delegate administrative duties, such as adding members and updating group description details, to team leads without relinquishing overall group ownership. Which TWO Chatter group configurations or administrative actions fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Set the Chatter group access type to Private.; Promote designated team leads to the Group Manager role within the group settings.

Answer

The requirements are met by establishing a Private Chatter group and promoting key team leads to the Group Manager role.
Configuring the group as Private restricts visibility of all posts, feeds, and files solely to members. Promoting team leads to Group Managers allows them to edit group details and handle member requests without changing the primary group owner.

Step-by-Step Solution

1
Determine the appropriate group access type for privacy requirements.
Selecting a Private group ensures that only designated group members can view, post, and share files within the group feed.
Public groups allow all internal users to view content, while Unlisted groups are hidden from search. Private groups fit the requirement for restricted internal collaboration.
2
Determine how to delegate administrative duties without transferring group ownership.
Promoting designated members to Group Managers grants them permissions to edit group details and manage group members.
The Group Manager role enables member administration without transferring overall ownership away from the original group creator.

Key Concept

Chatter Group Types and Member Roles
Question 1162Question

The sales manager at Pinnacle Financial Services reports that when sales representatives click on related Contact records from an Account page in the Lightning Sales Console, the Contact record opens in a new primary workspace tab. The manager requests that Contact records automatically open as subtabs under their parent Account record instead. Which setup procedure should the administrator complete to achieve this requirement?

Show answer & explanation

Answer: Navigate to App Manager in Setup, edit the Lightning Sales Console application settings, and configure the Navigation Rules for the Contact object to open as a subtab of Account.

Answer

Configure Navigation Rules for the Contact object inside the App Manager console app settings to open records as subtabs of Account.
In Salesforce Lightning Console apps, administrators configure how records open by defining Navigation Rules within the App Manager settings. Specifying that Contact records open as subtabs of Account ensures child records remain logically organized under the parent workspace tab.

Step-by-Step Solution

1
Access Setup and open App Manager
Locate the designated Lightning Sales Console application entry.
Console navigation behavior is configured at the application level.
2
Edit the Console App Settings and select Navigation Rules
Access the Navigation Rules configuration interface.
Navigation Rules specify how related child objects open when navigated to from a parent record.
3
Set the Contact object to open as a subtab of Account
Contact records clicked from Account contexts will consistently open in subtabs rather than standalone primary workspace tabs.
This directly fulfills the requested console layout optimization.

Key Concept

Lightning Sales Console Navigation Rules
Question 1163Question

An administrator at a manufacturing company is configuring a Salesforce Campaign to evaluate participant engagement for an interactive product workshop. The marketing team requires a custom Campaign Member Status called 'Attended' that accurately updates campaign response metrics such as Total Responses. Which action should the administrator take to fulfill this requirement?

Show answer & explanation

Answer: Add the custom Campaign Member Status 'Attended' to the campaign settings and select the Responded checkbox.

Answer

Add the custom Campaign Member Status 'Attended' to the campaign settings and select the Responded checkbox.
To ensure custom campaign member statuses count toward campaign response metrics, the administrator must explicitly check the 'Responded' box when defining or editing that status. This flag designates the status as a positive response in campaign roll-up calculations and summary reporting.

Step-by-Step Solution

1
Navigate to the Campaign detail page or Campaign Member Statuses configuration panel.
Access member status settings for the specified campaign.
Campaign member status values and response flags are defined on the Campaign object level.
2
Create the custom member status entry named 'Attended'.
The new status becomes available for assignment to campaign members.
Custom status values allow tracking specific engagement behaviors beyond standard defaults.
3
Enable the 'Responded' checkbox for the 'Attended' status.
Salesforce classifies member records with this status as responses.
The 'Responded' checkbox determines whether members with that status increment total responses and response rate metrics in campaign summary reporting.

Key Concept

Campaign Member Statuses and Responded Tracking
Estimated Time:1m 30s
Question 1164Question

A company's sales representatives use the Salesforce Integration with Gmail to communicate with customers. The system administrator needs to enable representatives to use and create shared Lightning Email Templates directly from the Gmail integration panel. Which TWO actions should the administrator take to fulfill this requirement?

Select all that apply

Show answer & explanation

Answer: Enable Enhanced Email in Salesforce Setup so emails saved from Gmail relate to records as standard Email Message records.; Assign a permission set containing the 'Create Lightning Email Templates' permission to the sales representatives.

Answer

The administrator should enable Enhanced Email in Salesforce Setup and assign a permission set containing the 'Create Lightning Email Templates' permission to the sales representatives.
Enabling Enhanced Email ensures logged emails become standard Email Message records, allowing seamless template integration. Assigning a permission set with the 'Create Lightning Email Templates' system permission allows reps to create and manage shared templates while adhering to baseline profile security.

Step-by-Step Solution

1
Enable Enhanced Email in Setup
Emails logged from Gmail are saved as standard Email Message records in Salesforce.
Enhanced Email is required for full compatibility with Lightning Email Templates and activity features.
2
Create and assign a Permission Set with 'Create Lightning Email Templates'
Sales representatives gain the ability to create and share Lightning email templates.
Salesforce best practice dictates using permission sets for additive user capabilities rather than creating additional profiles.

Key Concept

Configuring Gmail Integration and permissions for Lightning Email Templates
Estimated Time:1m 0s
Question 1165Question

A Salesforce administrator is configuring custom report types to support executive reporting. Which two statements correctly describe the capabilities of custom report types when defining object relationships? (Select two answers.)

Select all that apply

Show answer & explanation

Answer: Object relationships can be specified as 'with' (each record must have at least one related record) or 'with or without' (records may or may not have related records).; A primary object can be linked to up to three levels of child objects, allowing a maximum of four objects in the report type hierarchy.

Answer

The correct answers are the statements that object relationships can be specified using 'with' or 'with or without' constraints, and that a primary object can be linked down through up to three child levels (four objects total).
Custom report types provide the ability to specify object join rules ('with' or 'with or without') to control parent record visibility regardless of child record presence. Additionally, Salesforce allows building custom report types up to four object levels deep in a single hierarchy (e.g., Accounts > Contacts > Cases > Solutions).

Step-by-Step Solution

1
Analyze custom report type object relationship constraints
Confirm that custom report types support both inner joins ('with') and outer joins ('with or without').
This capability controls whether parent records without related child records appear in report results.
2
Determine maximum object hierarchy depth in custom report types
Confirm that up to 4 objects can be chained together (Primary object + 3 levels of child objects).
Salesforce platform limits restrict object relationship depth to 4 objects per custom report type.

Key Concept

Custom Report Type Object Relationships and Capabilities
Question 1166Question

Cloud Peak Solutions recently introduced two distinct Opportunity Record Types: Standard Licensing and Enterprise Consulting. However, sales representatives report that when creating a record under the Enterprise Consulting Record Type, all standard opportunity stage values are visible instead of only the specific stages intended for consulting deals. What administrative configuration step was omitted during setup?

Show answer & explanation

Answer: Creating a dedicated Sales Process for Enterprise Consulting to select the specific stage picklist values, and then assigning that Sales Process to the Record Type.

Answer

Creating a dedicated Sales Process for Enterprise Consulting to select the specific stage picklist values, and then assigning that Sales Process to the Record Type.
In Salesforce Core Administration, Opportunity Stages are tied to business processes. To customize available stage values for a specific group of users or sales pipeline, an administrator must create a Sales Process (selecting the specific stages, stage types, and probabilities) and then assign that Sales Process to the appropriate Opportunity Record Type.

Step-by-Step Solution

1
Identify the mechanism controlling Opportunity Stage picklist values in Salesforce.
Recognize that Opportunity Stages are unique picklist fields controlled specifically by Sales Processes rather than standard object picklist edit pages.
Salesforce requires a Sales Process to define the lifecycle, probability, and stage values available for different sales business models.
2
Determine the setup order required for Opportunity Record Types.
First create the custom Sales Process containing the required stage subset, then associate it when creating or editing the Opportunity Record Type.
An Opportunity Record Type cannot filter stage picklist values independently without being linked to a Sales Process.

Key Concept

Sales Process and Record Type Linkage for Opportunity Stages
Estimated Time:1m 30s
Question 1167Question

An administrator at Vantage Logistics is setting up sales productivity tools for representatives using the Lightning Sales Console. The sales manager requests a solution that allows reps to quickly insert standardized, pre-written message snippets—such as common follow-up emails and call log descriptions—directly into console feeds using keyboard shortcuts. Which Salesforce productivity feature should the administrator enable and configure to meet this requirement?

Show answer & explanation

Answer: Enable Quick Text in Setup and assign user permissions to create and insert pre-written snippets.

Answer

Enable Quick Text in Setup and assign user permissions to create and insert pre-written snippets.
Enabling Quick Text in Setup provides sales representatives with pre-written messages that can be inserted into emails, call logs, and task descriptions using quick keyboard shortcuts (e.g., Ctrl+. or Cmd+.). This directly fulfills the request for standardized communication snippets within the Lightning Sales Console.

Step-by-Step Solution

1
Identify the business requirement
Sales representatives need to quickly insert pre-defined text snippets into emails and activity logs within the Sales Console using keyboard shortcuts.
The scenario asks for a productivity feature designed specifically for pre-written snippets and keyboard shortcut insertion.
2
Evaluate Salesforce Sales Productivity features
Quick Text is the standard Salesforce feature designed for creating reusable snippets in emails, tasks, events, and console feeds.
Quick Text supports channels like Email, Event, Task, and Phone, allowing reps to trigger insertions via keyboard shortcuts (such as Ctrl+. or Cmd+.).
3
Select the correct administrative action
Enabling Quick Text in Setup and granting permissions allows reps to build and insert standardized text across console publisher layouts.
Administrators must enable Quick Text globally in Organization Settings and ensure users have appropriate object access or folder permissions to use Quick Text.

Key Concept

Quick Text Configuration in Lightning Sales Console
Question 1168Question

A non-profit organization is deploying an AppExchange managed package to streamline volunteer event coordination. The package includes custom objects, custom tabs, and a pre-configured permission set provided by the vendor. The administrator must grant access to 15 event coordinators who currently hold different base profiles across various departments, ensuring they receive necessary object permissions and license access without altering their standard profile settings. Which administrative action should the administrator take to achieve this requirement?

Show answer & explanation

Answer: Assign the vendor-provided permission set and allocate managed package licenses directly to the 15 event coordinators.

Answer

Assign the vendor-provided permission set and allocate managed package licenses directly to the 15 event coordinators.
Assigning the pre-configured permission set alongside the managed package license to specific users is the standard Salesforce administrator best practice for deploying AppExchange solutions. It grants necessary object and tab access without introducing profile maintenance overhead or exposing access to unneeded users.

Step-by-Step Solution

1
Identify the requirement for granting access across users with diverse existing profiles without modifying base profile setups.
Recognize that additive permissions should be granted using Permission Sets rather than modifying or cloning Profiles.
Permission sets allow flexible assignment of object, field, and tab access to specific users regardless of their assigned profile.
2
Evaluate AppExchange managed package deployment license requirements.
Determine that users require explicit managed package license assignments in addition to object security access.
Managed packages licensed per user require administrators to assign licenses so end users can invoke package components.
3
Combine permission set assignment with package license allocation.
Select the option that assigns both the permission set and the package licenses directly to the target users.
This fulfills all security and licensing constraints cleanly with minimal administrative overhead.

Key Concept

AppExchange Managed Package Permission and License Assignment
Estimated Time:2m 0s
Question 1169Question

A Salesforce Administrator at Crestview Capital Management is tasked with setting up a specialized Lightning Service Console application for high-priority client support agents. The requirements state that opening a Case must create a primary tab, related Contact and Account records must open automatically as subtabs under the Case, the Case Highlights Panel must show vital client status fields, and the console app must be deployed to the support team profile. In what sequential order should the administrator perform the steps to complete this configuration?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with editing the console app in App Manager, configuring primary and subtab navigation rules, setting up the Case compact layout for the highlights panel in Object Manager, and ending with profile assignment in App Manager.
The correct deployment sequence begins by opening the console application for editing in App Manager. Within App Manager settings, Navigation Rules are configured to determine how primary tabs (Case) and subtabs (Contact/Account) open. Next, the administrator navigates to Object Manager to customize the Case Compact Layout, which directly controls the fields displayed in the console Highlights Panel. Finally, profile access is assigned in App Manager to grant support agents access to the customized console app.

Step-by-Step Solution

1
Open Setup and navigate to App Manager to edit the Console application.
The Lightning App Builder interface for app settings is opened.
Administrative edits to console navigation options must originate from App Manager.
2
Configure Navigation Rules to set Case as primary tab and related objects as subtabs.
Tab structure and parent-child navigation behavior are defined for agents.
Console tab relationship rules are managed under Navigation Rules in App Manager.
3
Go to Object Manager > Case > Compact Layouts to customize fields displayed at the top of record pages.
The fields rendered in the Console Highlights Panel are established.
Highlights Panel content is directly driven by the primary or custom compact layout assigned to the record type.
4
Assign the completed Lightning Service Console application to the support agent profiles under User Assignments.
Support agents receive access to launch the configured app from the App Launcher.
Profile assignment ensures security and deployment visibility for the user population.

Key Concept

Service Cloud Console Application Configuration Sequence
Question 1170Question

BioHealth Dynamics is architecting its AppExchange deployment strategy across four specialized operating divisions. The Lead System Administrator must select and configure the appropriate AppExchange solution packaging model to fulfill specific operational, technical, governance, and licensing constraints for each division:

- The Clinical Division needs a free productivity dashboard built by Salesforce employees that can be fully modified at the code level, with the understanding that no vendor support or upgrade path is provided.
- The Commercial Division requires a paid third-party document assembly tool where intellectual property is hidden, Apex execution receives separate namespace governor limit allocations, and user access is governed by seat license assignments.
- The Automation Division requires a pre-built process automation package consisting exclusively of declarative workflows that administrators can customize freely without contributing to the organization's custom Apex code storage limit.
- The Enterprise Division needs a standardized productivity utility distributed across subsidiary subscriber orgs where central IT can issue non-destructive patch releases while preserving local org schema extensions.

Which AppExchange packaging model correctly satisfies each division's architectural and operational requirement?

Click a left item, then click its matching right item

Items

Clinical Division: Free customizable productivity dashboard requiring full Apex code access without vendor support or automated upgrades.
Commercial Division: Paid third-party productivity app requiring hidden IP, namespace governor limit isolation, and seat-level license management.
Automation Division: Pre-built process automation template requiring full admin editability without consuming custom Apex storage caps.
Enterprise Division: Multi-org productivity utility requiring central IT patch pushes while preserving subscriber org custom extensions.

Matches

Show answer & explanation

Answer

Clinical Division matches Salesforce Labs Unmanaged Package; Commercial Division matches ISV Commercial Managed Package; Automation Division matches AppExchange Flow Solution (Declarative Template); Enterprise Division matches Second-Generation (2GP) Managed Package Patch Release.
Each division's architectural constraint maps directly to a specific AppExchange solution pattern: Salesforce Labs unmanaged packages provide free editable code without vendor maintenance; ISV managed packages enforce IP protection, separate governor limit namespaces, and package licensing; Flow solutions offer editable declarative templates without Apex overhead; and 2GP managed package patch releases enable vendor-controlled updates across subscriber environments.

Step-by-Step Solution

1
Analyze the Clinical Division requirement for a free tool built by Salesforce employees with editable code and no vendor support.
Identify this as the defining characteristic of a Salesforce Labs Unmanaged Package.
Salesforce Labs builds free, open-source unmanaged apps where source code is copied into the subscriber org as unmanaged components with no vendor upgrade path.
2
Analyze the Commercial Division requirement for IP protection, separate governor limits, and seat license management.
Identify this as an ISV Commercial Managed Package.
Passing AppExchange security review grants managed packages isolated Apex governor limits, obfuscates code to protect IP, and enables seat-based licensing via Package Licenses.
3
Analyze the Automation Division requirement for pre-built declarative processes that do not consume Apex storage caps.
Identify this as an AppExchange Flow Solution (Declarative Template).
Flow Solutions deliver unmanaged or template flow processes, giving admins full edit rights without contributing to Apex code size limits.
4
Analyze the Enterprise Division requirement for multi-org distribution allowing central IT patch updates without overwriting subscriber extensions.
Identify this as a Second-Generation (2GP) Managed Package Patch Release.
Managed packaging models support patch versioning and subscriber upgrades, allowing package creators to update logic safely across subscribing orgs.

Key Concept

AppExchange Package Architecture, Licensing, and Governance Capabilities
Estimated Time:3m 0s
Question 1171Question

An administrator is setting up two distinct record types—'Standard Support' and 'Field Escalation'—on the custom object Service Ticket to accommodate different operational workflows. The administrator creates both record types and assigns custom page layouts to the appropriate user profiles. However, users assigned to the Field Escalation profile report that when creating a Field Escalation record, the custom picklist field Resolution Status displays values exclusive to Standard Support (such as 'Resolved on First Call') while omitting required escalation values (such as 'Dispatched to On-Site Team'). Which administrative step did the administrator omit during setup?

Show answer & explanation

Answer: Configuring the available picklist values specifically under the 'Field Escalation' Record Type detail page in Object Manager.

Answer

The administrator omitted configuring the available picklist values specifically under the 'Field Escalation' Record Type in Object Manager. When a record type is created, the administrator must edit the picklists available for that record type to specify which values users can select.
The correct answer highlights that picklist values must be explicitly configured for each Record Type within Object Manager. When a Record Type is created, it inherits all existing picklist values by default until an administrator edits the Picklists Available for Editing section on the specific Record Type detail page.

Step-by-Step Solution

1
Identify the root cause of incorrect picklist choices appearing on a record type.
Recognize that record types govern both Page Layout assignments and Picklist value selection.
Creating a record type does not automatically filter existing picklist values; it inherits default picklist values until configured.
2
Navigate to the object in Object Manager and select Record Types.
Locate the 'Field Escalation' record type definition.
Picklist value assignments per record type are configured directly under the Record Type detail page in Object Manager.
3
Edit the 'Resolution Status' picklist under the record type settings.
Move appropriate values ('Dispatched to On-Site Team') to Selected Values and remove irrelevant ones ('Resolved on First Call').
This ensures users assigned to the record type only see picklist choices relevant to their specific business process.

Key Concept

Page Layout and Record Type Assignment (Picklist Value Selection per Record Type)
Estimated Time:1m 30s
Question 1172Question

A Salesforce Administrator at an agricultural machinery manufacturer is setting up Salesforce Knowledge for customer support representatives. Representatives report that published troubleshooting articles classified under the "Tractor Electronics" data category are missing from their search results and Knowledge sidebar component. Organization-Wide Defaults for Knowledge are set to Public Read Only. Which administrative action will resolve this issue?

Show answer & explanation

Answer: Update the Data Category Visibility settings for the support team's role or profile to grant access to the Tractor Electronics category.

Answer

Update the Data Category Visibility settings for the support team's role or profile to grant access to the Tractor Electronics category.
In Salesforce Knowledge, visibility into published articles categorized by Data Categories is determined by Data Category Visibility settings assigned to roles, permission sets, or profiles. Even if Organization-Wide Defaults allow access, users cannot view articles in a specific category unless that category is explicitly made visible to their role or profile.

Step-by-Step Solution

1
Analyze the reported issue and current security setup
Articles are published and object OWD is Public Read Only, indicating object permissions are sufficient but Data Category filtering is restricting article visibility.
Salesforce Knowledge uses Data Category Visibility settings as a distinct layer to determine which categorized articles users can search and view.
2
Configure Data Category Visibility settings
Navigate to Setup, access Data Category Visibility for the target role, profile, or permission set, and set visibility for the relevant Category Group to Custom or All.
Explicitly granting category access ensures support representatives can search, filter, and view articles categorized under Tractor Electronics.

Key Concept

Salesforce Knowledge Data Category Visibility Settings
Question 1173Question

An administrator at Financial Connect enables Shared Activities in Salesforce to improve client meeting logging. Which capability becomes available to users when creating a single Event record?

Show answer & explanation

Answer: Relating up to 50 Contacts to the single Event record

Answer

Relating up to 50 Contacts to the single Event record
Enabling Shared Activities allows users to relate a single Task or Event to up to 50 Contacts (or Leads). The Related To field still permits only one parent record, such as an Account or Opportunity.

Step-by-Step Solution

1
Identify the feature being enabled
Shared Activities ('Allow Users to Relate Multiple Contacts to Tasks and Events') is enabled in Salesforce.
Understanding the core functionality of Shared Activities is necessary to evaluate record limits.
2
Determine object relationship limits under Shared Activities
Shared Activities allows relating up to 50 Contacts (or Leads) to a single Task or Event record via the Name field.
Salesforce restricts multi-object activity relationships to people records (Contacts/Leads), while non-people objects such as Accounts, Opportunities, or Cases remain limited to a single related record per activity.

Key Concept

Salesforce Shared Activities limits and capabilities
Question 1174Question

A system administrator at an enterprise analytics company needs to immediately revoke Salesforce login access for an integration specialist who was abruptly reassigned. When trying to deactivate the account, the system prevents deactivation because the user is assigned as a custom hierarchy user in active multi-step approval processes. Which action should the administrator perform to immediately restrict system access without interrupting active approvals?

Show answer & explanation

Answer: Freeze the user account to prevent login immediately while keeping the user record active until approval dependencies are updated.

Answer

Freeze the user account to prevent login immediately while keeping the user record active until approval dependencies are updated.
Freezing a user account is the appropriate solution when login access must be suspended immediately, but deactivation cannot be completed because the user is referenced in system processes such as custom hierarchy fields or default workflow settings.

Step-by-Step Solution

1
Identify the administrative requirement and system blockage.
Login access must be revoked immediately, but direct user deactivation is blocked by active system dependencies (custom hierarchy field reference).
Deactivating a user who is referenced in ongoing system processes or hierarchy fields is prevented by Salesforce to maintain data integrity.
2
Evaluate the difference between freezing and deactivating a user.
Freezing stops the user from logging in immediately without unlinking dependencies or freeing the user license.
Freezing is designed specifically for scenarios where deactivation cannot occur immediately due to configuration dependencies.

Key Concept

Freezing vs. Deactivating Users
Question 1175Question

An administrator is configuring Einstein Activity Capture (EAC) for a sales team integrated with Microsoft 365. The sales manager specifies three requirements: emails and calendar events must sync bidirectionally, feature access must be granted additively without altering existing user profiles, and management must be able to track sales activity volume within Salesforce reports. Which set of administrative actions correctly fulfills these requirements while accounting for platform data storage limitations?

Show answer & explanation

Answer: Assign the Einstein Activity Capture permission set to sales users, configure the sync direction for Emails and Events to Both Ways in the EAC configuration, and enable Activity Metrics so management can report on captured activity fields.

Answer

Assign the Einstein Activity Capture permission set to sales users, configure the sync direction for Emails and Events to Both Ways in the EAC configuration, and enable Activity Metrics so management can report on captured activity fields.
Granting feature access using permission sets complies with Salesforce security best practices for additive functionality. Setting the sync direction to 'Both Ways' satisfies the bidirectional sync requirement for emails and events. Because EAC data is stored off-core in an external cloud repository and does not create core Task/Event records, enabling Activity Metrics is required to expose aggregate activity fields (such as activity counts and dates) for reporting.

Step-by-Step Solution

1
Determine the appropriate access control method for granting Einstein Activity Capture permissions.
Use a Permission Set (or Permission Set License assignment) rather than creating or altering user Profiles to follow additive security practices.
Additive feature grants should always use permission sets to avoid profile proliferation.
2
Configure the synchronization direction within Einstein Activity Capture settings.
Select 'Both Ways' for both Emails and Events in the EAC configuration settings.
This meets the explicit business requirement for bidirectional synchronization between Microsoft 365 and Salesforce.
3
Evaluate reporting capabilities and data storage architecture for Einstein Activity Capture.
Enable Activity Metrics to allow reporting on activity fields such as Last Activity Date and Activity Count.
Activities captured by EAC are stored in an off-core AWS cloud repository and displayed on the Activity Timeline without creating standard Task or Event records in Salesforce core storage. Standard reports cannot query EAC data unless Activity Metrics is activated.

Key Concept

Einstein Activity Capture Architecture and Reporting
Question 1176Question

A non-profit organization needs to track volunteer shift assignments between individual Volunteer contact records and Community Event records. A single volunteer can participate in multiple community events, and a community event can have multiple volunteers assigned to it. The system must allow administrators to calculate the total volunteer hours worked directly on the Community Event record, and deleting a Community Event record must automatically delete all associated shift assignment records. Which TWO configuration steps should the Salesforce Administrator implement to meet these requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a custom junction object with Master-Detail relationships pointing to both the Contact (Volunteer) object and the Community Event object.; Create a Roll-Up Summary field on the Community Event object to sum total hours recorded on the shift assignment records.

Answer

The administrator must create a custom junction object with Master-Detail relationships to both master objects (Contact and Community Event) and create a Roll-Up Summary field on the Community Event object to sum the hours.
To model a many-to-many relationship between Volunteers (Contacts) and Community Events while satisfying cascade deletion and native aggregation requirements, a custom junction object with two Master-Detail relationships must be created. Once established, a Roll-Up Summary field can be added to the Community Event object to calculate total hours from the child records.

Step-by-Step Solution

1
Model the Many-to-Many relationship
Create a custom junction object (e.g., Volunteer_Shift__c) with two Master-Detail relationship fields pointing to Contact and Community Event.
Master-Detail relationships enforce cascading deletion of junction records when a parent record is removed and establish the parent-child structure necessary for native roll-up calculations.
2
Configure the Roll-Up Summary field
Create a Roll-Up Summary field on the Community Event object that aggregates the 'Hours' field from the child junction object records.
Roll-Up Summary fields are a declarative feature supported exclusively on the master side of a Master-Detail relationship.

Key Concept

Junction Objects and Master-Detail Relationships
Question 1177Question

A Service Cloud administrator at an architectural software company is configuring Case Escalation Rules to ensure high-priority support tickets adhere to strict Service Level Agreements (SLAs). Which two automated actions can the administrator configure directly within an escalation rule entry when a case escalates? (Select TWO answers.)

Select all that apply

Show answer & explanation

Answer: Reassigning the case to a designated user or support queue; Sending an automated email notification to the case owner, manager, or designated internal recipients

Answer

The correct capabilities are reassigning the case to a designated user or support queue, and sending an automated email notification to the case owner, manager, or designated internal recipients.
Case Escalation Rules execute automated actions when a case remains open past a defined SLA time limit. Within an escalation rule entry, an administrator can configure actions to reassign ownership of the case to a specified user or queue, as well as send email notifications to internal parties such as the case owner, their manager, or designated team members.

Step-by-Step Solution

1
Identify the primary function of Case Escalation Rules
Escalation rules track open cases and trigger automated actions when predefined time limits pass without case resolution.
Understanding what escalation rules manage helps distinguish their available actions from assignment and auto-response rules.
2
Determine available actions within escalation rule entries
Escalation actions support reassigning case ownership (to a user or queue) and notifying internal stakeholders via email.
These actions ensure SLA breaches are actively addressed by reassigning ownership and notifying managers or team members.
3
Differentiate from Case Assignment and Auto-Response Rules
Initial case ownership assignment is governed by Case Assignment Rules, and immediate confirmation emails to submitters are handled by Case Auto-Response Rules.
Recognizing functional boundaries prevents misconfiguring case automation features.

Key Concept

Case Escalation Actions Capabilities
Question 1178Question

Support representatives using the Salesforce Integration with Gmail report that they cannot view shared team email templates or populate custom object merge fields when drafting responses from the integration pane. Which two administrative actions must be taken to resolve these issues and enable full Lightning Email Template functionality in the integration side panel?

Select all that apply

Show answer & explanation

Answer: Enable Folders and Enhanced Sharing under Lightning Email Template settings in Setup.; Assign a permission set containing the Access Lightning Email Templates in Outlook and Gmail system permission.

Answer

The correct actions are enabling Folders and Enhanced Sharing under Lightning Email Template settings in Setup and assigning a permission set containing the Access Lightning Email Templates in Outlook and Gmail permission.
Enabling Folders and Enhanced Sharing grants granular folder-level permissions (View/Edit) for Lightning Email Templates. Additionally, assigning the Access Lightning Email Templates in Outlook and Gmail system permission provides users the capability to access and insert those templates directly from the Gmail integration panel.

Step-by-Step Solution

1
Identify template folder access controls
Determine that shared access to Lightning Email Templates requires enabling Folders and Enhanced Sharing in Setup.
Without enhanced folder sharing enabled, users cannot access public or shared folders containing team templates.
2
Identify integration side-panel permissions
Determine that users need the system permission Access Lightning Email Templates in Outlook and Gmail.
This specific permission allows end users to search for and insert Lightning templates directly from the integration pane.

Key Concept

Salesforce Integration with Gmail and Lightning Email Template Folder Permissions
Question 1179Question

A system administrator needs to import 15,000 Lead records into Salesforce while ensuring that existing matching rules are used to prevent duplicate records during the import process. Which Salesforce tool should the administrator use to accomplish this requirement?

Show answer & explanation

Answer: Data Import Wizard, because it supports Lead imports under 50,000 records and offers native duplicate detection.

Answer

Data Import Wizard, because it supports Lead imports under 50,000 records and offers native duplicate detection.
The choice recommending the Data Import Wizard is correct because the import volume (15,000) is below the 50,000 limit, Leads are a supported standard object, and the tool natively offers duplicate detection during the wizard process.

Step-by-Step Solution

1
Evaluate record volume requirement
The record count of 15,000 is within the 50,000 record threshold of the Data Import Wizard.
Data Import Wizard supports up to 50,000 records, while Data Loader handles up to 5,000,000 records.
2
Check object support
Leads are supported standard objects in Data Import Wizard.
Data Import Wizard supports Accounts, Contacts, Leads, Solutions, and Custom Objects.
3
Check duplicate detection capabilities
Data Import Wizard provides native options to check for duplicates by email or name during the wizard setup.
Native duplicate prevention settings are a core feature of the Data Import Wizard interface.

Key Concept

Selecting data management tools based on volume limit (50,000 vs 5,000,000), standard object support, and built-in duplicate detection capabilities.
Question 1180Question

An administrator is configuring a custom record page for the Operations team using Lightning App Builder. Management requires specific fields and record action buttons to appear on the page only when an Opportunity reaches the 'Negotiation' stage, without modifying underlying security permissions. Which two capabilities are provided by Dynamic Forms and Dynamic Actions to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Individual Field components and Field Sections can be placed anywhere on the Lightning page and assigned conditional visibility rules based on record field values.; Action buttons in the record header can be conditionally rendered based on record stage, field criteria, or user profile settings.

Answer

The two supported capabilities are: placing individual Field components with conditional visibility rules based on record values, and conditionally rendering header action buttons based on record or user attributes.
Dynamic Forms and Dynamic Actions allow administrators to break down traditional record page layouts into modular components within Lightning App Builder. Fields, field sections, and action buttons can be assigned conditional component visibility rules driven by record field values (such as stage) or user context, while respecting existing security settings.

Step-by-Step Solution

1
Evaluate Dynamic Forms capability for field placement and visibility
Dynamic Forms enables upgrading standard page layouts to flexible Lightning page components where fields and sections can have component visibility rules applied.
This meets the requirement to display specific fields dynamically without altering object metadata.
2
Evaluate Dynamic Actions capability for button management
Dynamic Actions allows administrators to manage actions directly in Lightning App Builder and set filters based on record fields or user context.
This fulfills the requirement to show action buttons conditionally when the Opportunity stage reaches 'Negotiation'.
3
Verify security boundary enforcement
Neither Dynamic Forms nor Dynamic Actions override or alter FLS, object permissions, or API accessibility.
UI visibility is strictly distinct from core Salesforce data security controls.

Key Concept

Dynamic Forms and Dynamic Actions UI Visibility vs Field-Level Security
PreviousPage 59 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin