Salesforce-Certified-Administrator Salesforce Certified Administrator Exam (SP23) Questions and Answers

An external ID is a custom field that has the external ID attribute enabled, which means it can be used as an identifier when importing and updating records from an external system. It allows administrators to match records based on a unique ID value from another system instead of using Salesforce record IDs, which may not be available or consistent across systems. An auto-number field is a custom field that automatically assigns a unique numeric value to each record, but it cannot be used as an identifier when importing and updating records from an external system because it is generated by Salesforce and may not match with the external system’s IDs. A rich text field is a custom field that allows users to enter formatted text, images, and links, but it cannot be used as an identifier when importing and updating records from an external system because it is not unique or consistent across systems. A record ID is an internal ID assigned by Salesforce to each record, but it cannot be used as an identifier when importing and updating records from an external system because it may not be available or consistent across systems. References: https://help.salesforce.com/s/articleView?id=sf.custom_field_attributes.htm &type=5

Flow builder is an automation tool that allows administrators to create flows that guide users through screens, collect data, and perform actions on records. It can be used to simplify the account creation process by creating a screen flow that shows only the essential fields for creating an account and hides any unnecessary fields or sections from the page layout. Approval process, workflow rule, and validation rule are not automation tools that can simplify the account creation process; they are used for different purposes such as approving records, updating fields, or enforcing data quality. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5

Page layout editor is a tool that allows you to customize the layout and organization of detail and edit pages for a specific object and record type combination. You can use page layout editor to make fields editable or read-only on page layouts for different profiles or record types. After resetting a password, the user may be required to activate their device by entering a verification code sent to their email address or phone number before they can log in to Salesforce. This is a security feature that helps prevent unauthorized access to Salesforce from unknown devices or browsers. References: https://help.salesforce.com/s/articleView?id=sf.customize_layoutedit.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.identity_verification.htm &type=5

A criteria-based sharing rule is a tool that allows administrators to share records with certain users based on field values rather than ownership. For example, a criteria-based sharing rule can share all opportunities with a cross-sell opportunity type with a specific group of users. A public group is a collection of individual users, roles, roles and subordinates, or other groups that can be used to simplify sharing settings and other processes. In this case, the administrator can add the subject matter experts to a public group and give them access to records with a criteria-based sharing rule that matches the cross-sell opportunity type. References: https://help.salesforce.com/s/articleView?id=sf.sharing_criteria_rules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.public_groups.htm &type=5

Quick actions allow you to initiate expense reports from Salesforce to an external HR system. Approval processes allow you to review the expense reports by managers and directors.

References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.quick_actions_overview.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. References: 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

One scenario that could prevent an administrator from changing the relationship between work item and project custom objects from master-detail to lookup is that roll-up summary fields exist on the master object (project). Roll-up summary fields are fields that calculate values from related records in a master-detail relationship; they cannot be used in a lookup relationship. If roll-up summary fields exist on the project object, they would prevent the administrator from changing the relationship type unless they are deleted first. A junction object is not required to support a lookup relationship; it is only used when creating many-to-many relationships between two objects using two master-detail relationships. The lookup field in all the records containing a value or the lookup field being required for saving records are not scenarios that would prevent changing the relationship type; they are scenarios that would allow changing the relationship type without losing data or functionality. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

The equals operator is an operator that compares two values and returns true if they are equal or false if they are not equal; it can be used in decision elements in flow builder to check if two values match certain criteria. The {!$GlobalConstant.True} value is a global constant value that represents true in flow builder; it can be used in decision elements in flow builder as one of the values being compared. Using equals operator and {!$GlobalConstant.True} as value can help Cloud Kicks update screen flow so that if checkbox field High Value Customer is set true first screen is skipped by using equals operator compare High Value Customer field value with {!$GlobalConstant.True} value in decision element output connector conditions; if condition is met first screen is skipped else first screen is shown. Using equals operator “High Value Customer” as value contains operator {!$GlobalConstant.False} as value contains operator “High Value Customer” as value are not valid options for updating screen flow skip first screen if checkbox field High Value Customer is set true because they either use wrong values wrong operators compare checkbox field values. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_operators.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_decision.htm &type=5

Record types and sales processes allow you to have different page layouts, fields, required fields, and picklist values for different types of opportunities.

References: https://www.salesforceben.com/salesforce-record-types/ https://trailhead.salesforce.com/content/learn/projects/create-an-opportunity-record-type-for-npsp/create-and-manage-stages-and-sales-processes

One of the possible reasons why an administrator is unable to add a new user in Salesforce is that the username is already in use by another user in any Salesforce org. Usernames must be globally unique across all Salesforce orgs, so the administrator needs to choose a different username for the new user. References: https://help.salesforce.com/s/articleView?id=sf.users_add.htm &type=5

A formula field is a type of field that calculates a value based on an expression or formula that references other fields or constants. For example, a formula field can display today’s date by using the TODAY() function. In this case, the administrator can create a formula field on the account object that updates the audited date field with today’s date when the status of the account is changed to ‘Audited’. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_formulas.htm &type=5

Knowledge articles are documents that provide information or solutions about products, services, or processes in Salesforce. You can use knowledge articles to respond to customers quickly and consistently with accurate information. You can create different types of articles with different templates and fields, such as FAQ articles, troubleshooting articles, how-to articles, etc. To meet the requirement of responding to customers with the top five troubleshooting tips that could help solve their issue, you need to create knowledge articles with those tips and attach them to your email responses or case comments. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_article_types.htm &type=5

Contacts to multiple accounts is a feature that allows you to associate a single contact with multiple accounts, both business and person accounts. This way, you can maintain the historical accuracy of the contact record without creating duplicate records for each account. References: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.htm &type=5

Process Builder is a tool that can be used to implement this request. Process Builder can create record-triggered flows that execute actions when certain conditions are met. In this case, Process Builder can create a flow that executes when a contact with a title of CEO is created and updates the contact’s account record with the CEO’s name. References: https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5

Record types allow you to update the options in a picklist based on the kind of opportunity.

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

Conditional visibility is a feature that allows administrators to show or hide screen components in a flow based on certain conditions or criteria. For example, conditional visibility can show only one question on a screen depending on the value of another field or variable. Conditional visibility consists of one or more rules that define when to show or hide a component based on an expression that evaluates to true or false. In this case, the administrator can use conditional visibility to hide the unnecessary question on the screen flow based on the scenario. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp.htm &type=5

Master-detail lookup is a type of relationship field that can be used to create a relationship between Account and Shoe and prevent orphaned Shoe records. Master-detail lookup establishes a parent-child relationship between two objects, where the parent record controls certain behaviors of the child record, such as security, ownership, and deletion. If the parent record is deleted, all the child records are deleted as well. References: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

Process builder can be used to create a record-triggered flow that executes when an opportunity is closed as won and creates a follow-up task for the owner. Field update can be used to update a date field on the opportunity that can be referenced by a time-dependent workflow rule to create another task after 60 days. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_time_action_considerations.htm &type=5

Two ways that marketing users can now access converted leads for editing are:

• Find them in the global search result, by entering the lead name or other keywords in the global search box and selecting Leads from the drop-down menu. Converted leads will appear in the search result with a check mark icon next to them.
• Utilize a list view where lead status equals Qualified, by creating or modifying a list view on the Leads tab and adding a filter for Lead Status equals Qualified. Converted leads will have Qualified as their lead status and will be visible in the list view. Searching the Recent Records component on the homepage or using Data Import Wizard will not allow users to access converted leads for editing. References: https://help.salesforce.com/s/articleView?id=sf.leads_view_converted.htm&type=5

To acknowledge cases with a Case Reason of Installation immediately via email and assign them to appropriate agents, and escalate cases that are still in New status after 4 hours to support management, an administrator should use Auto-response rules, Queues, and Escalation Rules for case management. Auto-response rules allow sending automatic email responses to customers based on case criteria. Queues allow grouping cases that share common characteristics and assigning them to a group of users who can access and work on them. Escalation rules allow escalating cases that meet certain criteria to higher-level users or groups and sending email notifications. Macros and Entitlements are not case management tools that can be used for this requirement. References: https://help.salesforce.com/s/articleView?id=sf.case_autoresponse.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.queues_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm &type=5

Before Save Flows are a type of record-triggered flow that run before a record is saved and can update fields on that record without any additional actions or DML operations. They are faster and more efficient than workflow rules or process builder for simple field updates when a record is created or updated. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_before_save_update.htm &type=5

Lightning app pages, Chatter, and dashboards are three items that are available in the mobile navigation menu. The mobile navigation menu allows users to access different items in the Salesforce mobile app, such as objects, apps, or utilities. Users can customize their mobile navigation menu by adding or removing items and changing their order. References: https://help.salesforce.com/s/articleView?id=sf.app_nav_setup.htm &type=5

A standard fiscal year starts on January 1 and ends on December 31. A custom fiscal year can be set to start on any month and end on any month. In this case, Cloud Kicks wants its fiscal year to start on February 1 and end on January 31. This can be achieved by setting the fiscal year to Custom and the starting month to February.

Setting the fiscal year to Standard and the starting month to February will not work, as the standard fiscal year starts on January 1. Setting the fiscal year to Custom and the duration to 4 quarters will not work, as the duration of a fiscal year is 12 months. Setting the fiscal year to Standard and the duration to 12 months will not work, as the standard fiscal year starts on January 1.

Custom fiscal years are fiscal years that follow a custom-defined structure that differs from the Gregorian calendar. They can be used by organizations that have fiscal years that start on a different month than January or have fiscal years that are divided into custom periods such as quarters or weeks. To set up a custom fiscal year that starts on February 1 and has 12 months, an administrator needs to set the fiscal year to custom and the starting month as February in the fiscal year settings. Setting the fiscal year to standard or the duration to 4 quarters does not meet the requirement of having a custom fiscal year that starts on February 1. References: https://help.salesforce.com/s/articleView?id=sf.admin_fiscal_year.htm &type=5

Assignment rules are tools that allow administrators to automatically route records to users or queues based on certain criteria. For example, an assignment rule can assign cases to different queues based on case priority, origin, type, or other fields. Assignment rules can be triggered when records are created manually, via email, web, or API. Assignment rules consist of multiple rule entries that define the criteria and actions for each assignment scenario. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadrules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesupport_assign.htm &type=5

The likely cause for why a rehired user is no longer able to access records they worked on before leaving the company is that the records were manually shared with the user. Manual sharing allows granting access to individual records to specific users or groups. However, manual sharing is removed when a record owner changes or when a user’s role changes. When a user is deactivated, their role is removed and any manual sharing involving that user is deleted. When a user is reactivated, their role is restored but manual sharing is not. Therefore, the rehired user will not have access to records that were manually shared with them before deactivation. The stage of Opportunity records, permission sets, or record type of Opportunity records are not likely causes for why a rehired user is no longer able to access records they worked on before leaving the company. References: https://help.salesforce.com/s/articleView?id=sf.sharing_manual.htm &type=5

One thing that an administrator should be aware of before changing an auto-number field to text field is that this change is prevented by Salesforce; it cannot be done because it would cause data loss and inconsistency. Auto-number fields are fields that automatically assign unique numeric values to each record; they cannot be changed to text fields because text fields do not have this functionality and may allow duplicate or invalid values. Existing field values remaining unchanged, being converted, or being deleted are not things that would happen before changing an auto-number field to text field because this change cannot happen at all. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_auto_number.htm &type=5

Formula fields are types of fields that calculate a value based on an expression or formula that references other fields or constants. Formula fields prevent administrators from changing their field type once they are created because they may be referenced by other functionalities such as reports, validation rules, workflow rules, etc., that depend on their data type and value. If a formula field is referenced by other functionalities, then changing its field type may cause errors or unexpected results. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_formulas.htm &type=5

To create a contact and an opportunity from a lead that is associated with a campaign, and keep the campaign member history, the administrator should convert the lead from the campaign member detail page. This will automatically create a contact, an account, and an opportunity that are linked to the campaign. Deleting, cloning, or adding a contact will not preserve the campaign member history. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_leads.htm &type=5

Lightning page allows you to customize a record page and add a screen flow as a component. You can use the Lightning App Builder to drag and drop the Flow component onto the page and select the screen flow you want to display.

References: https://help.salesforce.com/s/articleView?id=sf.flow_distribute_lightning_page.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm &type=5

Big Deal Alerts allow you to notify users when an opportunity reaches a certain amount or probability.

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

Two-factor authentication requires users to verify their identity with two pieces of information when they log in to Salesforce. One piece is their username and password, and the other is a verification code from an authenticator app or email or SMS.

References: https://help.salesforce.com/s/articleView?id=sf.identity_2fa_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.identity_2fa_login_flow.htm &type=5

Making a field universally required is a way to ensure that the field needs to be filled on every record; it prevents users from saving a record without entering a value in that field. It can be used to ensure that the billing system field needs to be filled on every invoice record by making it universally required in the field settings. Creating a process builder to set the field, defining an approval process for the child, or requiring the field on the record type are not ways to ensure that the field needs to be filled on every record; they either do not enforce data entry or only apply to certain scenarios or users. References: https://help.salesforce.com/s/articleView?id=sf.customize_fields.htm &type=5

A cross object formula field is a type of formula field that references fields from related objects using relationships such as lookup or master-detail. It can be used to display data from one object on another object without creating another relationship or copying data. A cross object formula field can be created on opportunity object to display data from industry field on account object using account ID lookup relationship. A custom account field, a standard account field, or a master-detail relationship field are not types of fields that can display data from industry field on account object on opportunity page layout; they either do not exist or do not reference related objects. References: https://help.salesforce.com/s/articleView?id=sf.cross_object_formulas.htm &type=5

Delegated approver is a feature that should be used to fulfill this requirement. Delegated approver allows users to delegate their approval authority to another user for a specified period of time, such as when they are out on vacation. Users can specify which approval requests they want to delegate and who they want to delegate them to. References: https://help.salesforce.com/s/articleView?id=sf.approvals_delegate.htm &type=5

Permission sets are used to grant additional permissions and access settings to individual users without changing their profiles or requiring a new profile to be created. You can use permission sets to extend users’ functional access without changing their existing profiles. To meet the request of giving comprehensive edit access on Campaigns to a few marketing users who have read-only access by default, you need to create a permission set with edit access on Campaigns and assign it to those users. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5

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. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

The AppExchange is an online marketplace where customers can find apps, components, consultants, developers, and more to extend Salesforce functionality or solve specific business challenges. Some of the actions that can be accomplished via AppExchange are finding certified developers and consultants who can help with custom development or implementation projects; installing industry-specific solution templates that provide preconfigured apps, dashboards, reports etc., for various industries such as manufacturing or healthcare; downloading free tools or components that enhance productivity or user experience; browsing reviews or ratings from other customers who have used certain products or services; etc. References: https://appexchange.salesforce.com/

Field update and email alert are two types of automated actions that can be added as part of the approval process. Field update allows you to change the value of a field on a record when it is submitted, approved, rejected, or recalled. Email alert allows you to send an email to one or more recipients when a record is submitted, approved, rejected, or recalled.

References: https://help.salesforce.com/s/articleView?id=sf.approvals_automated_actions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_creating_approval_actions.htm &type=5

A junction object is a type of custom object that allows administrators to create many-to-many relationships between two other objects. A many-to-many relationship means that each record of one object can be related to multiple records of another object, and vice versa. For example, a junction object can represent that a contact can be interested in multiple pieces of merchandise, and a piece of merchandise can be of interest to multiple contacts. A junction object has two master-detail relationships with the two objects it connects. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm &type=5

To allow a user to add new Campaign Members or update Member statuses, the administrator should make sure that Marketing User Checkbox is checked on the user record page. This checkbox enables users to create, edit, and delete campaigns, configure advanced campaign setup, import leads, manage campaign members, and update campaign history via mass update. The checkbox also requires users to have Read and Edit permissions on campaigns and leads/contacts. Creating a permission set, providing access to both Leads and Contacts, or running a Campaign report will not enable users to manage Campaign Members. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_enable.htm &type=5

Lightning pages are custom layouts that let you design pages for your Salesforce org using Lightning App Builder. You can assign different Lightning pages for different apps, record types, and profiles using Lightning page assignments. To meet the requirement of displaying different Lightning pages for Accounts in Sales Console and Service Console, you need to assign Lightning pages as app default for each app. References: https://help.salesforce.com/s/articleView?id=sf.lightning_page_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.lightning_page_assignments.htm &type=5

Big Deal Alerts are notifications that are sent to users when an opportunity reaches a certain amount, probability, or stage. They can be configured by administrators to alert sales reps or managers when they have a high likelihood of winning a big deal. Key Deals are a feature of Einstein Opportunity Scoring that shows the top opportunities based on their score and stage, but they do not send notifications. Activity Timeline is a component of Lightning Experience that shows the past and upcoming activities related to a record, but it does not notify users of big deals. Performance chart is a type of report chart that shows how well users or teams are performing against their goals, but it does not alert users of big deals. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_big_deal.htm &type=5

Grant access using Hierarchies is a setting that can be used to configure the custom object to meet this requirement. Grant access using Hierarchies determines whether access to records of the custom object is granted through the role hierarchy. If this setting is unchecked, managers are unable to see the feedback records from their staff, unless they are given access by other means, such as sharing rules or manual sharing. References: https://help.salesforce.com/s/articleView?id=sf.security_sharing_owd_custom_objects.htm &type=5

A record type is a feature that allows administrators to offer different business processes, picklist values, page layouts, etc., to different users based on their profile or role. A page layout is a feature that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. In this case, since Universal Containers has three separate lines of business with specific fields for each line; and since sales team needs different fields than service team; the administrator should create three record types for each line of business; and create two page layouts for each record type - one for sales team and one for service team. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm &type=5

Flow Builder supports creating a wizard that can collect user input and perform actions.

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

To make a quick action available on the Salesforce mobile app, you need to add it to the Salesforce Mobile and Lightning Experience Actions section of the page layout. You can use the Page Layout Editor to drag and drop the quick action onto the section.

References: https://help.salesforce.com/s/articleView?id=sf.actions_in_lex.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_page_layouts.htm &type=5

Validation rules allow you to prevent users from changing an opportunity close date to a date in the past.

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

Two data loss considerations when changing a custom field type from Text to Picklist are:

• Assignment and escalation rules may be affected, because the values in the picklist may not match the values that were previously entered in the text field, and the rules may not trigger as expected.
• Any list view based on the custom field is deleted, because the filter criteria for the list view may not be valid for the new field type, and the list view cannot be displayed. There will be no data loss with use of a global value set or auto updates to Visualforce references, because these are not related to changing a custom field type from Text to Picklist. References: https://help.salesforce.com/s/articleView?id=sf.fields_changing_type_considerations.htm&type=5

Standard objects are objects that are included with Salesforce by default, such as Account, Contact, Lead, Opportunity, etc. They have predefined fields and functionality that support common business processes. Custom objects are objects that you create to store information that is specific to your organization or industry. You can create new standard objects using the Object Manager in Setup. References: https://trailhead.salesforce.com/en/content/learn/modules/data_modeling/standard_and_custom_objects

Freezing a user is a way to temporarily prevent them from logging in to Salesforce without deactivating their user record. This is useful when you need to perform some cleanup tasks before deactivating a user, such as removing them from being referenced in a hierarchy field like Direct Manager. References: https://help.salesforce.com/s/articleView?id=sf.users_freeze.htm &type=5

To ensure Market Segment field from Lead is copied to converted Account record in routine manner without manual intervention , an administrator should ensure Market Segment field on Lead is mapped to right field on Account using Lead Field Mapping tool under Lead Settings. This tool allows mapping custom fields from Lead object to custom fields on Account , Contact , or Opportunity objects so that data is transferred when leads are converted . For example , an administrator can map Market Segment field on Lead to Market Segment field on Account using this tool . Ensuring Account has a field that has same name as new Lead field , writing validation rule , or writing record-triggered flow are not necessary for copying custom fields from Lead to Account . References : https :// help . salesforce . com / s / articleView ? id = sf . leads_custom_field_mapping . htm & type = 5

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. Creating a separate Lead Lightning App or updating the active Lead Assignment Rules will not affect lead identification. Setting up Web-to-Lead form will not work if the interns are entering leads manually in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.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. References: https://help.salesforce.com/s/articleView?id=sf.omnichannel_overview.htm &type=5

Knowledge is a feature that can be used to meet this requirement. Knowledge allows users to create, manage, and share articles that provide information and solutions for common issues or questions. Data categories can be used to organize articles into different topics and make them easier to find and access. Users can view related articles from the Case page layout based on the data category of the case. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_categories.htm &type=5

To track all cases that reference the new product and give read/write access to the product’s two lead engineers, the administrator should create a queue and a criteria-based sharing rule. The queue will allow assigning cases that meet certain criteria, such as having a specific value in the Product field, to a group of users. The criteria-based sharing rule will grant read/write access to the queue members for cases that match the same criteria. References: https://help.salesforce.com/s/articleView?id=sf.queues_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.sharing_criteria.htm &type=5

A pending Chatter post is a post that has been scheduled to be published at a future date and time. However, if the user who created the pending Chatter post is deactivated before the scheduled date and time, then the pending Chatter post will be canceled and will not be published. This is because deactivated users cannot create or edit posts in Chatter. References: https://help.salesforce.com/s/articleView?id=sf.collab_scheduled_posts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.collab_deactivated_users.htm &type=5

A validation rule is a tool that allows administrators to enforce data quality and integrity by preventing users from saving records that do not meet certain criteria or conditions. For example, a validation rule can display an error message if a user enters an invalid value in a field. In this case, the administrator can create a validation rule on the account object that displays an error if the account annual revenue field is below 0 or greater than 100 billion. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

A Chatter private group is a type of Chatter group that allows members to share feedback and ideas with each other in a secure and exclusive space; only members can see and post in a private group. It can be used by Ursa Major Solar to create a space for product owners to collaborate with just the product team by creating a Chatter private group and adding product owners as members. Using quick actions to log communication, configuring a Chatter public group, or adding activity history to document tasks are not solutions for creating a space for product owners to collaborate with just the product team; they either do not provide privacy or do not support collaboration. References: https://help.salesforce.com/s/articleView?id=sf.collab_groups_overview.htm &type=5

Email-to-Case allows you to create cases from incoming emails. You need to enable this feature and set up routing addresses and case creation settings.

References: https://help.salesforce.com/s/articleView?id=sf.customizesupport_email_to_case.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. References: https://help.salesforce.com/s/articleView?id=sf.flow_build_overview.htm &type=5

To make sure that all of the Salesforce users log in using the branded login URL after deploying my domain, and give them a grace period for updating their bookmarks, the administrator should set the Redirect policy to Redirect with a warning to the same page within the domain. This will redirect users who try to log in from https://login.salesforce.com or another domain to https://nto.my.salesforce.com, and show them a warning message that they need to update their bookmarks. Setting the Login policy or preventing login from https://login.salesforce.com will not redirect users or give them a warning. Filtering with Form Factor will not affect login URL. References: https://help.salesforce.com/s/articleView?id=sf.domain_mgmt_redirect.htm &type=5

Get Records is a flow element that allows you to retrieve one or more records from an object that meet certain conditions and store them in a collection variable or a record variable for use later in the flow. You can also choose which fields from those records you want to store in variables. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_data_getrecords.htm &type=5

Maximum invalid login attempts, password complexity requirements, and number of days until expiration are three password policies that an administrator can configure to encourage employees to choose secure and appropriate passwords for their Salesforce accounts. Maximum invalid login attempts determines how many times a user can enter an incorrect password before being locked out of Salesforce. Password complexity requirements determine how complex a user’s password must be based on criteria such as length, case sensitivity, alphanumeric characters, etc. Number of days until expiration determines how often users must change their passwords. References: https://help.salesforce.com/s/articleView?id=sf.security_password_policies.htm &type=5

Guided selling, validation rules, and required fields on the page layout are three options that can be used to ensure sales reps fill out key fields when working on an opportunity through the process. Guided selling allows administrators to add prompts and guidance at each stage of the path to help reps move forward with confidence. Validation rules allow administrators to enforce data quality and business logic by preventing reps from saving records that do not meet certain criteria. Required fields on the page layout allow administrators to make certain fields mandatory for reps to enter before saving records. Configuring opportunity path can help reps visualize and update key fields at each stage, but it does not make them required or prevent them from moving forward without entering them. Using flow to mark fields required is not possible because flows cannot modify page layouts or field properties. References: https://help.salesforce.com/s/articleView?id=sf.path_guided_selling.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.fields_defining_field_properties.htm &type=5

Utility bar is a feature that is available in a Lightning app where visibility is limited to the Salesforce mobile app. Utility bar allows users to access common productivity tools, such as notes, history, recent items, and more, from any page in the app. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_utility_bar.htm &type=5

When you mark a field as required in Object Manager, the field is universally required to save a record on that object in the user interface. However, the field is not required to save records via the API on that object, unless you also mark it as required on the page layout.

References: https://help.salesforce.com/s/articleView?id=sf.fields_about_required_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_profile_picklists.htm &type=5

The User Licenses related list in Company Information shows the types of licenses that have been purchased for an org and how many are available or used. It also shows the expiration date of each license type if applicable. This information can help administrators plan for license purchases and manage user access. Searching for license types in setup does not show how many licenses have been purchased or how many are available or used. User Management settings in setup does not show license information either, but rather settings related to user login, session, identity, etc. Usage-based entitlement related list in company information shows information about usage-based licenses such as API requests or sandboxes, but not user licenses. References: https://help.salesforce.com/s/articleView?id=sf.users_understanding_license_types.htm &type=5

Lead assignment rule is a feature that can be used to route new leads to the correct sales person based on the lead address. Lead assignment rule can assign leads to users or queues based on certain criteria, such as lead source, industry, or location. Lead assignment rule can also send email notifications to the new lead owners or other recipients. References: https://help.salesforce.com/s/articleView?id=sf.leads_assignment_rules.htm &type=5

Auto-response rules are used to automatically send email responses to lead or case submissions based on the criteria you define. You can create one auto-response rule per object (lead or case) and configure multiple rule entries with different criteria and actions within that rule. To meet the requirement of sending different email notifications based on case priority, you need to create one auto-response rule for cases and configure three rule entries with filters for low-priority, medium-priority, and high-priority cases respectively. Then you need to select the appropriate email template for each rule entry action. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadsautor.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesautor.htm &type=5

Contact, lead, and person account are three objects that will have the individual field available for tracking data privacy information when data protection and privacy is enabled for an org. The individual object is an object that stores data privacy preferences and requests for customers who are subject to privacy regulations such as GDPR; it can be linked to contact, lead, or person account records using the individual field. Case and opportunity, account and user, or individual, user, and account are not combinations of objects that will have the individual field available for tracking data privacy information; they either do not store customer data or do not support individual object relationships. References: https://help.salesforce.com/s/articleView?id=sf.individual_object.htm &type=5

Recurring tasks are tasks that repeat at regular intervals, such as daily, weekly, monthly, etc. They can be created by users who have the permission to create recurring tasks, which can be enabled by administrators in the user profile settings. Flow, workflow rule, and recurring activities are not valid options for creating recurring tasks in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.tasks_recurring.htm &type=5