All practice questions

1784 questions

Question 1201Question

An administrator at a subscription management company needs to enable sales representatives to create a related Renewal Opportunity directly from a custom Contract record page in Lightning Experience. The new Opportunity must automatically populate its Account Name and Primary Contact fields using context from the originating Contract record, and the action button must only be accessible from the Contract object's page layout. Which configuration should the administrator implement to fulfill these requirements?

Show answer & explanation

Answer: Create an Object-Specific Quick Action on the Contract object to create an Opportunity record and define Predefined Field Values for the target fields.

Answer

The administrator should create an Object-Specific Quick Action on the Contract object that creates a related Opportunity record and configures Predefined Field Values for the Account Name and Primary Contact fields.
Creating an Object-Specific Quick Action on the Contract object enables administrators to create related Opportunity records while automatically populating target fields using Predefined Field Values. Because it is object-specific, it retains record context and can be assigned directly to the Contract object page layout.

Step-by-Step Solution

1
Navigate to Object Manager, select the Contract object, and create a new Quick Action of type 'Create a Record' targeting the Opportunity object.
An object-specific action layout and configuration context tied directly to Contract records is established.
Object-specific quick actions inherit parent record context, which is required to automatically populate related fields.
2
Define Predefined Field Values for the Account Name and Primary Contact fields using formulas derived from the originating Contract record.
The target fields on the newly created Opportunity are automatically populated upon clicking the action.
Predefined field values streamline data entry and enforce data consistency without requiring manual user input.
3
Add the newly created Quick Action to the Lightning Experience Actions section of the Contract Page Layout.
The action button becomes available specifically on the Contract record page UI.
Actions must be explicitly assigned to the page layout or Dynamic Actions bar to appear for end users.

Key Concept

Object-Specific Quick Actions and Predefined Field Values
Question 1202Question

Match each Einstein Activity Capture (EAC) sync direction configuration setting to its corresponding data flow behavior.

Click a left item, then click its matching right item

Items

Both ways
Salesforce to Exchange
Exchange to Salesforce
Don't sync

Matches

Show answer & explanation

Answer

Einstein Activity Capture sync directions control data movement: 'Both ways' provides bidirectional synchronization, 'Salesforce to Exchange' pushes changes outward from Salesforce, 'Exchange to Salesforce' imports changes inward into Salesforce, and 'Don't sync' disables event synchronization between systems.
Each Einstein Activity Capture sync setting directly dictates the flow of data between Salesforce and connected email/calendar servers. 'Both ways' maintains parity in both applications, 'Salesforce to Exchange' propagates changes outward only, 'Exchange to Salesforce' imports external updates inward only, and 'Don't sync' halts background event synchronization.

Step-by-Step Solution

1
Analyze bidirectional sync requirements.
'Both ways' pairs with automatic updates occurring across both platforms.
Bidirectional sync ensures updates in either application reflect in the other.
2
Analyze unidirectional sync options.
'Salesforce to Exchange' pushes outward only, while 'Exchange to Salesforce' imports inward only.
Unidirectional settings restrict event updates to flowing in one designated direction.
3
Analyze the zero-sync configuration.
'Don't sync' pairs with no automated background transfer.
Choosing not to sync prevents data transfer between Salesforce and connected email accounts.

Key Concept

Einstein Activity Capture Sync Directions
Question 1203Question

An organization recently implemented a Web-to-Case form on its public website. During a marketing campaign, several prospective customers submitted inquiries that triggered custom validation rules on the Case object. While cases adhering to the validation rules were created successfully, the submissions violating the validation rules failed to generate Case records, and web users received no onscreen error notifications. Which location should the Salesforce Administrator check to inspect the details and data of these failed Web-to-Case submissions?

Show answer & explanation

Answer: The email inbox of the Default Case Owner designated in Support Settings

Answer

The administrator should check the email inbox of the Default Case Owner designated in Support Settings.
Because Web-to-Case forms do not interactively surface Salesforce validation errors back to end-users on external websites, Salesforce routes any failed record creation attempts (such as those caused by custom validation rules or missing required fields) via email to the Default Case Owner configured in Support Settings. This notification includes the submitted form values so the administrator or support team can manually review and create the case if necessary.

Step-by-Step Solution

1
Analyze Web-to-Case exception handling behavior in Salesforce.
Web-to-Case operates asynchronously from an HTML form POST request and does not display native Salesforce validation error messages back to external web visitors on custom websites.
Web-to-Case is designed as a simplified HTML intake channel without interactive client-side error rendering.
2
Identify the system target for failed record creation alerts.
When a Web-to-Case submission fails due to custom validation rules, duplicate rules, or required field restrictions, Salesforce rejects the record and sends an error notification email.
Salesforce routes error notifications containing the raw form submission key-value pairs directly to the Default Case Owner configured under Support Settings.
3
Evaluate potential log locations for intake errors.
No persistent error log view exists in the Setup UI for standard Web-to-Case failures, making the Default Case Owner email the primary diagnostic source.
Understanding fallback notification paths ensures administrators can recover lost data and adjust validation rules or form fields accordingly.

Key Concept

Web-to-Case Error Handling and Default Case Owner Fallback
Question 1204Question

An administrator at an enterprise technology firm is setting up a Salesforce Campaign for a global virtual summit. The marketing team requires that when prospective leads register and attend the summit, their engagement is accurately counted as a response in Campaign hierarchy statistics and reporting. Additionally, the team needs existing campaign history to remain associated when these leads are converted into contacts. Which configuration step should the administrator take to ensure campaign responses are accurately tracked?

Show answer & explanation

Answer: Edit the Campaign Member Statuses for the campaign to ensure the 'Attended' status value has the 'Responded' checkbox selected.

Answer

Edit the Campaign Member Statuses for the campaign to ensure the 'Attended' status value has the 'Responded' checkbox selected.
In Salesforce Campaign Management, responses are tracked by setting the 'Responded' checkbox on specific Campaign Member Status values (e.g., 'Attended'). When a member's status is changed to a status flagged as 'Responded', Salesforce updates campaign metrics such as Total Responses. Furthermore, when a lead is converted, Salesforce automatically links all existing Campaign Member history to the newly created Contact record without requiring custom lead field mapping.

Step-by-Step Solution

1
Navigate to the Campaign record or Advanced Setup for Campaign Member Statuses.
Access the list of campaign member statuses defined for the campaign.
Campaign response tracking relies on individual status settings rather than general lead or campaign fields.
2
Add or modify the 'Attended' status value and check the 'Responded' box.
Members assigned the 'Attended' status are officially flagged as responded in Salesforce.
Salesforce aggregates campaign response metrics based on member statuses marked as 'Responded'.
3
Verify lead conversion behavior with existing Campaign Members.
Lead conversion natively preserves Campaign Member records and links them to the resulting Contact.
No custom field mapping is required for standard Campaign Member history to carry over during lead conversion.

Key Concept

Campaign Member Status Response Tracking and Lead Conversion Behavior
Question 1205Question

A system administrator needs to set up an automated nightly process to upsert 40,000 Account and Contact records into Salesforce from an external system using a custom External ID field. The process must execute on a scheduled basis without requiring manual interaction in the browser interface. Which utility should the administrator select to meet these requirements?

Show answer & explanation

Answer: Data Loader executed via the Command Line Interface (CLI), because it supports automated batch processes and upsert operations using External IDs.

Answer

Data Loader executed via the Command Line Interface (CLI) should be selected because it supports automated batch operations, scheduled execution without manual intervention, and upserts based on External IDs.
Selecting Data Loader executed via the Command Line Interface (CLI) is correct because Data Loader provides a CLI component that can be integrated with OS schedulers to automatically perform batch data operations, such as upserts matching on External IDs, without user intervention.

Step-by-Step Solution

1
Analyze the operational requirements
Identified key constraints: automated nightly execution (no manual UI steps), upsert capability using External IDs, and record volume of 40,000 records across Accounts and Contacts.
Tool selection requires evaluating automation capabilities alongside record volume and object support.
2
Evaluate Data Import Wizard against requirements
Data Import Wizard supports 40,000 records and Accounts/Contacts with External IDs, but it is purely browser-based and cannot be run headlessly via scheduled automation script.
Automated nightly jobs require CLI or API automation.
3
Evaluate Data Loader against requirements
Data Loader can be run via CLI using batch configuration files and scheduled tasks (e.g., Windows Task Scheduler or cron jobs) to perform automated upserts via External ID.
Data Loader CLI is designed specifically for automated unattended data loading operations.

Key Concept

Data Loader CLI vs Data Import Wizard Automation
Estimated Time:2m 0s
Question 1206Question

A sales representative has recently left the company, and an administrator must reassign all of their Account records to a new representative using the native Salesforce Mass Transfer Records wizard. The transfer must also include open opportunities and related contacts owned by the former representative. Arrange the steps in the correct chronological order to complete this process.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps begins by navigating to Setup and opening the Mass Transfer Accounts tool. Next, set the 'Transfer from' user to the former representative and the 'Transfer to' user to the replacement representative. Third, select the appropriate configuration checkboxes to include open opportunities, open activities, and related contacts. Finally, define any filter criteria, run the search query, select the targeted account records, and click Transfer.
The correct order follows the natural workflow of the Salesforce Mass Transfer Accounts wizard: first opening the wizard in Setup, defining the current owner and recipient, enabling the checkboxes for related records (contacts, open opportunities, open activities), and lastly filtering, selecting, and transferring the records.

Step-by-Step Solution

1
Locate and open the Mass Transfer Accounts tool in Setup.
Access to the Mass Transfer Accounts wizard interface.
The Mass Transfer Records utility in Setup is designed for standard objects like Accounts, Leads, and Custom Objects.
2
Specify the user mapping (source and target owners).
Defines who currently owns the accounts and who will receive them.
Salesforce requires explicit identification of the current owner ('Transfer from') and new owner ('Transfer to') before filtering records.
3
Configure options for transferring child records.
Ensures associated open opportunities, open activities, and contacts are transferred alongside the account.
Account transfers can automatically transfer child records if the corresponding checkboxes are selected in the wizard setup.
4
Execute search, review results, select accounts, and click Transfer.
Ownership of selected accounts and specified child records is successfully updated.
The search and selection step isolates the exact records to be updated before executing the bulk ownership update.

Key Concept

Mass Transfer Records in Salesforce Core Administration
Estimated Time:1m 30s
Question 1207Question

A customer support administrator at a solar energy installation company has enabled Salesforce Knowledge and assigned the Knowledge User feature license to Tier 1 support agents. The agents have Read and Create object permissions on Knowledge articles. However, when agents search for published troubleshooting articles assigned to the 'Solar Inverters' Data Category, no articles appear in the search results, even though Support Managers can view them without issue. Which configuration change should the administrator make to allow Tier 1 agents to view these articles?

Show answer & explanation

Answer: Configure the Data Category Visibility settings for the Tier 1 agents' roles or profiles to grant access to the Solar Inverters category.

Answer

The administrator should update the Data Category Visibility settings on the Tier 1 support agents' profiles or roles to grant access to the Solar Inverters category group.
In Salesforce Knowledge, visibility of published articles is directly linked to Data Category Groups. Even if users have the Knowledge User feature license and object-level Read access, they cannot search for or view published articles tagged with specific categories unless their Role, Profile, or Permission Set grants them access to those Data Categories. Adjusting the Data Category Visibility settings resolves the visibility blockage.

Step-by-Step Solution

1
Identify the mechanism controlling article visibility in Salesforce Knowledge.
Recognize that visibility for published Knowledge articles is controlled by Data Category Group visibility.
Object permissions (Read/Create) grant access to the Knowledge object, but Data Categories filter which specific articles a user can view.
2
Compare support manager access with Tier 1 agent access.
Determine that support managers have custom or parent category visibility, while Tier 1 agents have default or restricted category visibility.
If Data Category visibility is set to 'None' or restricted for a role/profile, articles mapped to those categories remain hidden in search and views.
3
Select the correct administrative fix.
Modify the Data Category Visibility settings for the affected role or profile.
Granting visibility to the required category group ensures published articles in that category appear for the Tier 1 agents.

Key Concept

Data Category Visibility in Salesforce Knowledge
Question 1208Question

A Salesforce administrator is setting up recurring data backups using the native Data Export Service. Which two statements accurately describe the standard behavior and capabilities of the Data Export Service? (Choose 2 options)

Select all that apply

Show answer & explanation

Answer: Data exports can be scheduled to run automatically at weekly or monthly intervals depending on the Salesforce edition.; An email notification containing a secure download link is sent to the designated user when the export process completes.

Answer

The Data Export Service allows scheduling automated exports at weekly or monthly intervals, and it sends an email notification containing a download link when the export files are ready.
The Data Export Service natively supports automated scheduling (weekly or monthly based on Salesforce edition) and alerts administrators via email with a download link once processing finishes.

Step-by-Step Solution

1
Identify native backup capabilities in Salesforce Setup.
Recognize that Data Export Service generates downloadable zip files containing CSV data and file attachments.
Data Export Service is designed for scheduled bulk CSV extractions.
2
Verify execution scheduling and notification mechanisms.
Confirm exports can be scheduled weekly/monthly and send email links upon completion.
These are standard administrative features of the native service.
3
Evaluate retention and restoration limitations.
Disqualify statements claiming indefinite storage or auto-restoration.
Files expire after 48 hours and restoration requires manual import operations.

Key Concept

Data Export Service Capabilities and Limits
Question 1209Question

A healthcare software vendor utilizes an Experience Cloud site to provide self-service support to clinic administrators holding standard Customer Community licenses. The organization's Default External Access (Org-Wide Default) for Cases is configured as Private. Management requires clinic administrators to view and edit all support cases associated with their specific clinic's Account record, regardless of which individual logged the case. Which two configurations should the system administrator implement to meet these access and security requirements?

Select all that apply

Show answer & explanation

Answer: Create a Sharing Set for the Customer Community profile that grants Read/Write access to the Case object using the User:Account = Case:Account mapping.; Maintain the Case External Org-Wide Default as Private to restrict record visibility across different clinic accounts.

Answer

To grant Customer Community users access to all cases under their Account while maintaining security boundaries between different accounts, the administrator must keep the Case External Org-Wide Default set to Private and configure a Sharing Set that maps the User's Account field to the Case's Account field with Read/Write permissions.
For standard Customer Community licenses, sharing record access within an account requires a Sharing Set that matches the User record's Account field to the Case record's Account field. To ensure data privacy between different external accounts, the Case object's External Org-Wide Default must remain Private so that access is granted strictly through the defined sharing set rules.

Step-by-Step Solution

1
Evaluate the capabilities and limitations of standard Customer Community user licenses.
Standard Customer Community users do not utilize roles, the role hierarchy, or administrative permissions like View All / Modify All.
Understanding license constraints prevents misconfiguration attempts involving role hierarchy or elevated profile permissions.
2
Determine baseline security requirements using External Org-Wide Defaults.
Set Case External Org-Wide Default to Private.
Setting baseline access to Private ensures cases from one clinic account are strictly inaccessible to users from another clinic account.
3
Configure record-level sharing access for external portal users.
Establish a Sharing Set mapping User:Account to Case:Account with Read/Write access for the Customer Community profile.
Sharing Sets grant community users access to records matching shared criteria (such as account association) without requiring role hierarchy or heavy sharing infrastructure.

Key Concept

Experience Cloud Sharing Sets and External Org-Wide Defaults
Question 1210Question

An administrator created two record types on a custom object named Inspection__c: 'Safety Inspection' and 'Quality Inspection'. After assigning distinct page layouts to each record type for the Operations profile, users report that creating a Safety Inspection record still displays Quality-specific values, such as 'Packaging Defect', inside the Status picklist field. What action should the administrator take to ensure only Safety-related values appear in the Status picklist for Safety Inspection records?

Show answer & explanation

Answer: Navigate to the Safety Inspection record type configuration on the Inspection object and edit the available values for the Status picklist.

Answer

Edit the available values for the Status picklist directly within the Safety Inspection record type configuration on the custom object.
Editing the available picklist values under the specific Record Type settings is the standard Salesforce mechanism for displaying different picklist options per record type. Record types allow administrators to customize picklist value subsets independently of page layout assignments.

Step-by-Step Solution

1
Identify where picklist value availability per record type is governed in Salesforce setup.
Recognize that Record Types control picklist value sets independently of Page Layouts.
Creating a Record Type allows administrators to define a subset of master picklist values specifically for records of that type.
2
Navigate to Object Manager > Inspection__c > Record Types > Safety Inspection.
Locate the 'Picklists Available for Editing' section for the target record type.
This setup screen lists all editable picklist fields associated with the object for that specific Record Type.
3
Edit the Status picklist field assignment to remove 'Packaging Defect' and save.
Only relevant Safety Inspection status values remain selected in the enabled values list.
Saving this configuration updates the picklist choices presented to users when creating or editing Safety Inspection records.

Key Concept

Record Type Picklist Value Assignment
Question 1211Question

A Salesforce Administrator at an enterprise software firm needs to model a relationship between a custom Application__c object and a custom Security_Audit__c object. The business requires that deleting an Application__c record must automatically delete all associated Security_Audit__c records. Additionally, managers must be able to view the total count of completed Security_Audit__c records directly on the Application__c record page without using custom code. Which two configuration steps should the administrator take to fulfill these requirements? (Choose 2 answers)

Select all that apply

Show answer & explanation

Answer: Create a Master-Detail relationship field on the Security_Audit__c object referencing the Application__c object.; Create a Roll-Up Summary field on the Application__c object using the COUNT function to aggregate related Security_Audit__c records.

Answer

The administrator must create a Master-Detail relationship field on the Security_Audit__c object pointing to Application__c, and create a Roll-Up Summary field on the Application__c object to count related audit records.
To satisfy both business requirements—automatic deletion of child records upon master deletion and Declarative aggregate calculations—a Master-Detail relationship must be implemented. Creating the Master-Detail relationship field on the Security_Audit__c object establishes Application__c as the master, enabling cascading deletes. Creating a Roll-Up Summary field on Application__c allows the administrator to count related audit records without custom code.

Step-by-Step Solution

1
Determine the required relationship type for cascading deletion and roll-up capabilities.
Identify that Master-Detail relationships are required because deleting a Master automatically deletes detail records, and Master-Detail is mandatory for Roll-Up Summary fields.
Lookup relationships do not support native Roll-Up Summary fields or standard cascade deletion for custom objects.
2
Define the Master-Detail relationship on the child object.
Create the Master-Detail field on Security_Audit__c (detail) pointing to Application__c (master).
Relationship fields are defined on the child/detail object.
3
Create the aggregation field on the parent object.
Create a Roll-Up Summary field on Application__c using the COUNT summary type filtered for completed audit records.
Roll-Up Summary fields reside on the master object to aggregate child record data.

Key Concept

Master-Detail Relationships and Roll-Up Summary Fields
Question 1212Question

A Service Cloud administrator at an electric vehicle charging network provider is configuring automated ticket processing for hardware support inquiries. Place the following case execution steps in the correct order in which Salesforce processes them upon case creation.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for case creation automation evaluation is Validation Rules, followed by Case Assignment Rules, Case Auto-Response Rules, and finally Case Escalation Rules.
In standard Salesforce automated case processing, incoming cases are validated first. Once validated, Case Assignment Rules execute to route the case to a user or queue. Next, Case Auto-Response Rules process to issue automated confirmation messages to the submitter. Finally, Case Escalation Rules evaluate to schedule SLA escalation actions.

Step-by-Step Solution

1
Evaluate record integrity
Validation rules run first to ensure incoming data satisfies custom and system entry requirements.
If validation fails, record creation stops immediately before automation rules run.
2
Determine owner assignment
Case Assignment Rules evaluate entry criteria to set the Case Owner field to a user or queue.
Ownership must be established early so downstream communication and tracking reflect correct routing.
3
Send customer notification
Case Auto-Response Rules evaluate criteria to dispatch an automated email response to the contact.
Auto-response rules rely on initial case attributes and run specifically after assignment.
4
Establish SLA and escalation timers
Case Escalation Rules evaluate criteria to schedule escalation actions if the case remains open.
Escalation rules set up execution targets based on case creation or modification time.

Key Concept

Salesforce Order of Execution for Case Automation Rules
Question 1213Question

A Salesforce administrator is tasked with performing a cleanup to delete 1,500 inactive Case records that have been closed for over three years. When attempting to perform this operation using the standard Mass Delete Records tool in Salesforce Setup, the administrator realizes the tool cannot finish the entire job in a single batch submission. Which limitation explains why the standard wizard cannot complete this in one request, and what is the appropriate administrative solution?

Show answer & explanation

Answer: The standard Mass Delete Records wizard is capped at a maximum of 250 records per operation, so the administrator should use Data Loader to perform the mass deletion.

Answer

The standard Mass Delete Records wizard is capped at 250 records per operation, requiring the use of Data Loader for larger record sets.
The standard Mass Delete Records wizard built into Salesforce Setup allows administrators to delete standard objects (such as Accounts, Leads, Contacts, Opportunities, Products, and Cases), but it restricts each search and delete operation to a maximum of 250 records at a time. To mass delete 1,500 records efficiently, Data Loader is the recommended tool.

Step-by-Step Solution

1
Identify the record volume and tool limitations
The requirement asks to delete 1,500 Cases. The standard Mass Delete Records tool UI in Setup enforces a limit of 250 records per operation.
Understanding native UI governor limits determines when to transition from Setup wizards to external client tools.
2
Select the appropriate data management utility
Data Loader supports mass deletion of supported standard objects including Cases beyond the 250 UI threshold.
Data Loader uses the SOAP or Bulk API to process bulk DML delete operations efficiently.

Key Concept

Mass Delete Records limits and Data Loader capabilities
Question 1214Question

A Salesforce administrator is evaluating native data utilities to satisfy four specific administrative requirements for an enterprise organization:

1. Importing 65,000 custom object records using an External ID for upsert operations.
2. Importing 35,000 Lead records while applying existing duplicate rules to prevent creating duplicate records.
3. Executing an automated, nightly scheduled upsert of Opportunity records.
4. Performing a hard delete of 150,000 inactive custom object records to immediately bypass the Recycle Bin.

Which two utility configurations should the administrator implement to successfully fulfill these requirements? (Choose 2 options)

Select all that apply

Show answer & explanation

Answer: Use Data Import Wizard to process the 35,000 Lead records because it natively supports Lead imports under 50,000 records and allows matching against lead deduplication criteria.; Use Data Loader via command-line interface (CLI) to execute both the automated nightly Opportunity upserts and the bulk hard deletion of custom object records.

Answer

The administrator should use Data Import Wizard for the 35,000 Lead import to enforce duplicate prevention rules, and Data Loader (via CLI) for the 65,000 custom object upsert, the automated nightly Opportunity upsert, and the hard delete operation.
Data Import Wizard is optimal for importing under 50,000 Lead records with duplicate detection. Data Loader is required for automated CLI tasks, Opportunity operations, data loads exceeding 50,000 records, and hard deletion of records.

Step-by-Step Solution

1
Evaluate record volume limits for the data operations.
The 65,000 custom object record import exceeds the 50,000 record ceiling of the Data Import Wizard, requiring Data Loader.
Data Import Wizard cannot process data loads exceeding 50,000 total records in a single job.
2
Evaluate object type support and feature capabilities.
Lead import (35,000 records) fits within the Data Import Wizard limits and benefits from native duplicate matching rules. Opportunity operations are unsupported by Data Import Wizard.
Data Import Wizard supports Accounts, Contacts, Leads, Solutions, and Campaign Members, but does not support Opportunities or automated background CLI schedules.
3
Assess automation and deletion requirements.
Nightly scheduled upserts and Hard Delete operations require Data Loader.
Hard Delete (bypassing Recycle Bin) and scheduled unattended execution via command-line interface are features exclusive to Data Loader.

Key Concept

Selecting between Data Import Wizard and Data Loader based on record volume limits, object support, duplicate prevention capabilities, and command-line automation.
Question 1215Question

An administrator is customizing the Salesforce Mobile App experience for a team of field sales representatives. The administrator configures a custom Lightning App with tailored navigation tabs designed for mobile field workflows. However, when field sales representatives log into the Salesforce Mobile App on their mobile devices, they continue to see the legacy default 'Mobile Only' navigation menu items rather than the newly configured custom Lightning App navigation. Which action must the administrator take to ensure the field representatives see the custom Lightning App navigation items when using the Salesforce Mobile App?

Show answer & explanation

Answer: Verify that the custom Lightning App's supported form factors setting includes Phone (or Desktop and Phone) and that the field sales representatives' Profile is assigned to the Lightning App.

Answer

The administrator must verify that the custom Lightning App's supported form factors setting includes Phone (or Desktop and Phone) and ensure the field representatives' profile is granted access to the app.
The correct answer identifies that for custom navigation tabs to appear in the Salesforce Mobile App, the Lightning App must be configured with a form factor that includes 'Phone' (or 'Desktop and Phone') within the App Manager, and the users' profile must have access to that app. Once configured and assigned, mobile users can select the app from the App Launcher in the mobile app, displaying the tailored navigation items.

Step-by-Step Solution

1
Identify why the custom Lightning App navigation tabs are not appearing in the Salesforce Mobile App.
Determine that Lightning Apps must be explicitly enabled for mobile form factors to function in the Salesforce Mobile App.
If a Lightning App is configured for 'Desktop' only, mobile users cannot switch to it in the mobile app launcher and fall back to the default 'Mobile Only' navigation.
2
Navigate to App Manager in Setup and edit the custom Lightning App options.
Set the Supported Form Factors to 'Desktop and Phone'.
This enables the app and its customized navigation bar items to render when accessed on mobile devices.
3
Verify user profile assignments for the Lightning App.
Ensure the target user profile has access to the Lightning App.
Users can only see and select Lightning Apps in the App Launcher (desktop or mobile) if their assigned profile or permission sets permit access.

Key Concept

Salesforce Mobile App Navigation and Lightning App Form Factors
Question 1216Question

A system administrator needs to insert 3,000 new Contact records into Salesforce while ensuring that duplicate records are automatically detected and blocked during the import process. Which data utility should the administrator use to accomplish this task?

Show answer & explanation

Answer: Data Import Wizard

Answer

Data Import Wizard should be used because it supports importing standard objects like Contacts (up to 50,000 records) and natively includes duplicate detection features.
The Data Import Wizard is the appropriate tool for this scenario because it supports standard objects like Contacts up to 50,000 records and includes native duplicate detection capabilities.

Step-by-Step Solution

1
Evaluate record volume and target object
The requirement involves inserting 3,000 Contact records, which is well below the 50,000 limit for Data Import Wizard.
Data Import Wizard supports standard objects such as Accounts, Contacts, Leads, and Solutions up to 50,000 records.
2
Evaluate functional requirements
The operation requires automatic duplicate detection during import.
Data Import Wizard natively provides duplicate matching options (e.g., matching by Email or Name) during the setup steps.

Key Concept

Data Import Wizard vs Data Loader features and limits
Question 1217Question

A Salesforce administrator is configuring email integration features and template access controls across various department units. Match each business requirement scenario with its appropriate Salesforce administrative setup or feature capability.

Click a left item, then click its matching right item

Items

Restrict access to a specific folder of sales email templates so that only members of a designated Public Group can view and use them in Outlook or Gmail integrations.
Enable sales representatives to insert Lightning Email Templates in the integration panel that automatically populate merge data from related custom object fields.
Allow service agents using Gmail Integration to send template-based emails that include persistent file attachments without re-uploading documents manually.
Grant power users the ability to build visually rich email templates using drag-and-drop component layouts without granting them full system administrator privileges.

Matches

Show answer & explanation

Answer

Each scenario maps directly to its specific administrative feature: restricting template folder visibility to a Public Group requires enabling Folders and Enhanced Sharing for Email Templates; populating cross-object fields dynamically relies on Handlebars Merge Language (HML); incorporating automatic attachments requires attaching Salesforce Files directly to the template record; and delegating template design capability without administrative rights requires the Access Email Template Builder permission set.
The pairings correctly match each operational requirement with its Salesforce administrator feature: folder-level group restriction requires enhanced folder sharing; dynamic cross-object field insertion requires Handlebars Merge Language (HML); reusable email attachments require Salesforce Files attached to the template record; and visual template creation rights require the Access Email Template Builder permission.

Step-by-Step Solution

1
Analyze the folder access requirement for Public Groups.
Determined that standard email sharing lacks Public Group folder controls until Folders and Enhanced Sharing for Email Templates is enabled.
Enhanced sharing extends folder-level permissions (View/Edit) to Public Groups and Roles.
2
Analyze the requirement for dynamic field merge across standard and custom objects in integration panes.
Identified Handlebars Merge Language (HML) in Lightning Email Templates.
HML supports rich field substitution across parent and related records in modern Salesforce email templates.
3
Analyze the requirement for pre-attached files when inserting templates from Gmail/Outlook panes.
Identified attaching Salesforce Files directly to the Lightning Email Template record.
Lightning Email Templates automatically link attached Salesforce Files when the template is selected in an integration.
4
Analyze permission requirements for drag-and-drop template builder tool access.
Identified the 'Access Email Template Builder' permission set assignment.
This permission explicitly grants access to the visual builder interface without requiring system administration rights such as 'Customize Application'.

Key Concept

Salesforce Integration Pane & Lightning Email Template Administration
Question 1218Question

An administrator at a financial firm needs to configure a Chatter group for a sensitive compliance audit. The requirements state that the group must not appear in search results or be discoverable by non-members, membership must be strictly by invitation without allowing users to request to join, and only group owners and managers should be permitted to create new posts while members can only comment. Which combination of Chatter group settings satisfies these requirements?

Show answer & explanation

Answer: Set Access Type to Unlisted and select the Broadcast Only checkbox.

Answer

Set Access Type to Unlisted and select the Broadcast Only checkbox.
The correct answer combines setting the group access type to Unlisted with selecting the Broadcast Only option. Unlisted groups ensure that non-members cannot find the group via search, view its feed, or submit membership request forms. Meanwhile, the Broadcast Only setting restricts post creation solely to group managers and owners, allowing regular members to interact only via comments.

Step-by-Step Solution

1
Evaluate the visibility and discoverability requirement.
Identify that Unlisted Chatter groups hide group feeds, membership, and search presence from non-members and disable join requests, whereas Private groups are discoverable in search and allow join requests.
Unlisted groups provide complete privacy from non-members compared to Public or Private groups.
2
Evaluate the posting restriction requirement.
Identify that checking the 'Broadcast Only' checkbox on the group configuration page restricts creating posts to group owners and managers while allowing members to comment.
Broadcast Only is the native Chatter setting for announcement-style communication control within any group access type.
3
Combine the settings to meet all audit group requirements.
The combination of Unlisted access type and Broadcast Only configuration satisfies all specified constraints.
Only this combined configuration ensures strict privacy and restricted posting permissions.

Key Concept

Chatter Group Access Types and Broadcast Settings
Question 1219Question

A Salesforce Administrator at a financial services firm is configuring user interface elements to streamline advisor workflows. Match each specific business requirement to the appropriate Salesforce action, button, or link feature.

Click a left item, then click its matching right item

Items

Create a related Compliance Audit record directly from an Account page while automatically linking to the Account and pre-populating predefined field values.
Allow wealth advisors to log a general client inquiry record from anywhere in Lightning Experience, regardless of which page they are currently viewing.
Open an external regulatory web page in a new browser tab while dynamically passing the Account record's tax identification number as a URL parameter.
Provide a action on the Case detail page that allows support agents to modify specific Case fields using a focused, simplified field layout.

Matches

Show answer & explanation

Answer

Requirement 1 matches Object-Specific Quick Action (Create a Record); Requirement 2 matches Global Quick Action (Create a Record); Requirement 3 matches Custom Link; Requirement 4 matches Object-Specific Quick Action (Update a Record).
Each feature selection satisfies the exact context, availability, and functional requirements specified: Object-Specific Create actions handle parent record context; Global actions handle context-free record creation from anywhere; Custom Links handle parameterized URL navigation; and Object-Specific Update actions provide streamlined field editing for the target record.

Step-by-Step Solution

1
Evaluate record creation with parent context (Requirement 1)
Creating a child record from a parent record context with auto-populated parent lookups requires an Object-Specific Quick Action.
Global actions lack source record context and cannot inherit parent field values automatically.
2
Evaluate universal record creation (Requirement 2)
Creating a record from anywhere in the application interface requires a Global Quick Action.
Global quick actions are available on global layouts and navigation bars regardless of the current record.
3
Evaluate external web navigation with dynamic parameters (Requirement 3)
Passing field values via merge fields to an external site is achieved using a Custom Link.
Custom Links support URL parameter encoding using standard merge field syntax.
4
Evaluate targeted record field updates (Requirement 4)
Updating designated fields on the target record via a dedicated pop-up layout requires an Object-Specific Update Record Quick Action.
Update record quick actions provide a focused action layout for updating specific record fields.

Key Concept

Selecting the correct Salesforce UI feature (Object-Specific Quick Actions, Global Quick Actions, Custom Links, or Custom Buttons) based on record context, global availability, and action type requirements.
Question 1220Question

An organization requires a monthly offline archive of all Salesforce record data and file attachments for regulatory compliance. Which native feature should an administrator configure to schedule automated periodic backups of all organizational data?

Show answer & explanation

Answer: Data Export Service

Answer

The Data Export Service is the native Salesforce feature used to schedule automated weekly or monthly backups of all organizational data and images/attachments.
The Data Export Service (also known as Weekly/Monthly Data Export) is built into Setup and enables administrators to schedule automated periodic exports of all Salesforce records and attachments directly without third-party tools.

Step-by-Step Solution

1
Identify the organizational requirement
The requirement calls for a native, scheduled automated backup of all record data and file attachments.
Understanding whether manual execution or automated native scheduling is needed dictates tool selection.
2
Evaluate native Salesforce capabilities
The Data Export Service (Weekly/Monthly Data Export) provides native browser setup for automated recurring exports.
Other tools like Data Loader require external scripts for automated scheduling, whereas Data Export Service runs natively.

Key Concept

Salesforce Data Export Service for Backup Management
Estimated Time:45s
PreviousPage 61 / 90Next
All practice questions — Salesforce Certified Administrator | Examkin