Salesforce Certified Administrator Practice Test - Questions Answers, Page 18

To identify new leads entered by interns from existing leads, the administrator should define a record type and assign it to the interns. This will allow them to select a different record type when creating leads, and distinguish them from other leads based on record type. Setting up Web-to-Lead form will not work if the interns are entering leads manually in Salesforce. Creating a separate Lead Lightning App or updating the active Lead Assignment Rules will not affect lead identification.

Reference: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm&type=5

To boost productivity by providing insights at the start of each day, the administrator should add three sales-specific standard Lightning components to the homepage:

Activities, which shows tasks and events related to records that matter most to users

Assistant, which provides personalized suggestions and reminders for key updates and actions

Key Deals, which highlights important opportunities that need attention or are close to closing Path and Performance Chart are not standard Lightning components, but custom components that can be added to specific objects or pages.

Reference: https://help.salesforce.com/s/articleView?id=sf.home_components.htm&type=5

To make it easy for approvers to respond to approval requests, the administrator should configure three settings:

Update the organization's chatter setting to allow approvals, which enables approvers to approve or reject requests from chatter feeds or email notifications

Enable the organization's Email approval response setting, which allows approvers to reply to approval request emails with keywords such as APPROVE or REJECT

Add the Items to approve component to the approvers home page, which shows a list of pending approval requests that can be acted upon with one click Specifying initial submission actions within the approval process will not affect how approvers respond to requests. Creating a flow to automatically approve all records will bypass the approval process altogether.

Reference: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_email.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_one_click.htm&type=5

To route new leads to the correct sales person based on the lead address, the administrator should use lead assignment rules that specify criteria based on lead fields such as City, State/Province, or Country, and assign leads that match those criteria to queues or users. Lead assignment rules can be triggered automatically when leads are created or manually by users. Creating a formula field, assigning with an escalation rule, or configuring a validation rule will not route leads to sales people.

Reference: https://help.salesforce.com/s/articleView?id=sf.leads_assignment_rules.htm&type=5

To assign agent capacity and skill set, the administrator should enable Omni-Channel, which is a feature that allows agents to work on multiple cases or chats at once based on their availability and expertise. Omni-Channel can route work items to agents based on their predefined capacity and skills, ensuring that they are working on the right tasks at the right time. Knowledge Management, Escalation Rules, and Territory Management are not related to agent capacity and skill set.

Reference: https://help.salesforce.com/s/articleView?id=sf.omnichannel_overview.htm&type=5

To show a component that shows LinkedIn data only to sales users when they are on their mobile phones, the administrator should filter the component visibility with two conditions:

User > Profile > name = sales User, which checks if the user's profile name is ''sales User''

Form Factor = phone, which checks if the user's device is a phone Filtering with view or role will not achieve the desired result.

Reference: https://help.salesforce.com/s/articleView?id=sf.app_builder_page_visibility_rules.htm&type=5

To automate applying discounts on opportunity products when an opportunity is won, the administrator should use Flow Builder, which is a tool that allows creating complex business processes with clicks. The administrator can create an autolaunched flow that runs when an opportunity is updated, checks if its stage is ''Closed Won'', and updates its related opportunity products with discounts from a formula or variable. Approval Process, Prebuilt Macro, and Formula Field are not able to update related records based on criteria.

Reference: https://help.salesforce.com/s/articleView?id=sf.flow_build_overview.htm&type=5

To help agents fill in event details and request dates for open house events without double-booking them, the administrator should create an approval process on the Campaign object, which is used to manage marketing events in Salesforce. The approval process can define entry criteria based on campaign fields such as type or status, specify initial submission actions such as sending email alerts or updating fields, assign approvers who can review and approve event requests, and specify final approval actions such as creating tasks or updating fields. Creating a workflow rule, a sharing rule, or a campaign will not help agents request event dates or prevent double-booking.

Reference: https://help.salesforce.com/s/articleView?id=sf.campaigns_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm&type=5

To protect data with backups by using Data Export Service, two considerations that the administrator should remember when scheduling export are:

Data Backups are limited to weekly or monthly intervals depending on edition and license type Metadata backups must be run via a separate process such as Metadata API or change sets because Data Export Service only exports data (records) Metadata backups are not limited by sandbox refresh intervals. Data Export Service should be run from production orgs unless testing purposes require otherwise.

Reference: https://help.salesforce.com/s/articleView?id=sf.data_export.htm&type=5