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

A dependent picklist and a custom picklist are the two features that can be used to fulfill the requirement. A global picklist and a multi-select picklist are not features that can be used to fulfill the requirement.

Here is a more detailed explanation of why A and B are the correct answers:

• A. Dependent Picklist

A dependent picklist is a picklist whose values are dependent on the value selected in another picklist. This is useful for ensuring that only valid values are selected for a field. In this case, the administrator can create a dependent picklist for the category field on accounts and cases, with the values for the picklist being dependent on the record type selected. This will ensure that only the relevant picklist values are available for selection based on the record type selected.

For example, the administrator could create a dependent picklist for the category field on accounts and cases with the following values:

• Record Type: New Account
• Picklist Values: Residential, Commercial
• Record Type: Existing Account
• Picklist Values: Renewal, Upsell, Cross-sell

This would ensure that only the relevant picklist values are available for selection when creating a new account or an existing account.

• B. Custom Picklist

A custom picklist is a picklist that is created by the administrator. This is useful for creating picklists with values that are specific to the organization's needs. In this case, the administrator can create a custom picklist for the category field on accounts and cases, with the values for the picklist being specific to the organization's needs. This will ensure that the picklist values are relevant to the organization and its customers.

For example, the administrator could create a custom picklist for the category field on accounts and cases with the following values:

• Picklist Values: Residential, Commercial, Land, Multi-Family

This would ensure that the picklist values are relevant to the organization and its customers.

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

Screen flow allows you to create a form that collects user input and performs actions based on that input. You can use screen components to display questions and instructions, and use flow logic to update records or send notifications.

References: https://trailhead.salesforce.com/content/learn/modules/screen-flows/get-started-with-screen-flows https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.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

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

Flow Builder and Process Builder are two automation tools that should be used to accomplish this request. Flow Builder can be used to create a flow that defines the logic and actions for creating a renewal opportunity, such as setting the stage, close date, and amount. Process Builder can be used to create a process that triggers the flow when an opportunity is closed won. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.process_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

To use Data Loader to mass import new records to a custom object from a new API, the administrator will need to append their security token at the end of their password to login. The security token is an alphanumeric code that is required for API access when logging in from an IP address that is not trusted by Salesforce. The security token can be obtained from the user’s personal settings or by resetting it via email. Adding a permission set, resetting the password and the security token, or using the Data Import Tool are not necessary for using Data Loader. References: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_token.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

A lookup field is a type of field that creates a relationship between two objects and allows users to select a record from one object as a value for another object. A lookup relationship creates a one-to-many relationship between two objects, where each parent record can have many child records but each child record can have only one parent record. A lookup relationship also allows limited access to child records, meaning that users can see only those child records that they have access to based on their profile permissions and sharing settings. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5

To require users to choose a specific search engine from a picklist when lead source is “Search Engine”, and hide it otherwise, the administrator should create a picklist for specific search engine on the same screen as lead source, and set conditional visibility so that it is only shown when lead source is “Search Engine”. This will make sure that users see only relevant fields based on their input. A decision element will create an extra screen that may disrupt user experience. An assignment element will not affect field visibility. A validation rule will not hide fields but only show errors when values are invalid. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screen_components_picklist.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screen_components_conditional_visibility.htm &type=5

Log in as the user is a feature that can be used to validate the error the user is receiving. Log in as the user allows an administrator to access Salesforce as another user and perform actions on their behalf, such as editing an opportunity. This can help troubleshoot issues that are specific to a user’s profile, role, or permissions. References: https://help.salesforce.com/s/articleView?id=sf.admin_login.htm &type=5

To re-assign cases that meet the 24 hour SLA to the next tier queue, the administrator should use a case escalation rule that defines the criteria for escalating cases, such as age or priority, and the actions to perform when those criteria are met, such as changing owner or sending email alerts. Case escalation rules can help ensure that cases are handled in a timely manner and escalated to appropriate users or queues. Einstein Case Routing, Auto-response rule, and Case assignment rule are not able to re-assign cases based on SLA or age. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm &type=5

Security Health Check is a tool that can be used to identify and fix potential session vulnerabilities. Security Health Check scans the security settings in an org and compares them to a baseline set of standards, such as the Salesforce Baseline Standard or the Salesforce Optimized Standard. Security Health Check provides a health check score and a list of issues and recommendations for improving the security settings. References: https://help.salesforce.com/s/articleView?id=sf.security_health_check.htm &type=5

Minimum password length and password complexity requirement are two settings that administrators can configure to increase the security of user passwords in Salesforce. They determine how long and how complex the passwords must be to meet the security standards. Password different than username and prevent common words are not valid settings in Salesforce, although they are good practices for creating strong passwords. References: https://help.salesforce.com/s/articleView?id=sf.admin_password_policies.htm &type=5

Assignment rules and queue configuration are two options that should be used to help the support team work on some of UC’s cases. Assignment rules can be used to automatically assign cases to a queue based on certain criteria, such as case origin or priority. Queue configuration can be used to add Case as an available object to the existing queue and specify which users or groups can access the queue. References: https://help.salesforce.com/s/articleView?id=sf.case_assignment_rules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_queues.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

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

A user with manager role above the agent can change ownership on multiple cases that are owned by the agent or by users below the agent in the role hierarchy. A user with the System Administrator profile can change ownership on any case, regardless of the owner or role hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.case_change_owner.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_userperms.htm &type=5

To share report folders with different groups of users with different levels of access, an administrator can use folder sharing settings under setup. Folder sharing settings allow administrators to share report folders with public groups, roles, roles and subordinates, territories, or portal roles with view or edit access. In this case, the administrator can share the Helpdesk folder with Support Agents with view access so they can run Helpdesk reports but not edit them; and share the R&D folder with Support Managers with edit access so they can view and edit R&D reports. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_folders_sharing.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

Flow builder and approval process are two tools that can be used by Ursa Major Solar to assist users with a guided expense report process to simplify submissions, routing, and authorizations. Flow builder is a tool that allows administrators to create flows, which are guided processes that collect data and perform actions in Salesforce; it can be used to create a screen flow that guides users through the steps of submitting an expense report, such as entering expense details, uploading receipts, etc. Approval process is a tool that allows administrators to create approval processes, which are automated processes that require approval from one or more approvers; it can be used to create an approval process that routes expense reports to the appropriate managers for authorization based on certain criteria, such as amount, type, etc. Validation rule, quick action are not tools for building a guided expense report process; they are used for different purposes such as enforcing data quality or creating records. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5

One of the possible causes for being unable to add a new user in Salesforce is that the username is already in use by another organization. Usernames must be globally unique across all Salesforce orgs, so if another user has claimed that username before, it cannot be used again. To fix this issue, choose a different username that is not taken by anyone else. The username is not restricted to a domain specific to my domain unless specified by an administrator. The email address used for the username does not have to match a contact record. The email used for the username can be any valid email address. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgmt_add.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

When users log in to Salesforce via the user interface, the system checks for authentication based on their profile settings and permissions. One of the settings is login hours, which specify the time range when users can log in to Salesforce based on their profile. Another setting is Two-Factor Authentication for User Interface Logins permission, which requires users to enter a verification code along with their username and password when they log in to Salesforce via the user interface. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_loginhours.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_2fa_perm_ui_logins.htm &type=5

Record types are a way to assign different page layouts and picklist values to different users based on their business needs. To use two different page layouts for customer and partner accounts, create one record type for each account type and assign them to the appropriate page layouts and profiles. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

Creating a dashboard with the running user set as someone who can see all opportunities is a way to create an enterprise-wide dashboard of all open opportunities in the pipeline without changing any sharing settings. The running user determines what data is displayed on the dashboard based on their access level and permissions; if the running user can see all opportunities, then the dashboard will show all opportunities regardless of who views it. Updating the dashboard folder settings to manager for the sales reps role does not create an enterprise-wide dashboard; it only controls who can access the dashboard folder, not what data is displayed on the dashboard. Adding a filter to the dashboard to filter the opportunities by owner role does not create an enterprise-wide dashboard either; it only shows opportunities owned by users in certain roles, not all opportunities. Building individual dashboards for profiles that need to see the enterprise results is not a feasible solution; it would require creating multiple dashboards for different profiles and maintaining them separately, which is inefficient and redundant. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_running_user.htm &type=5

Report folders are used to organize and secure reports in Salesforce. You can set different levels of access for different users or groups on each report folder. To preserve the integrity of the source reports for dashboards, you can create a new report folder with viewer access only and move the dashboard reports to that folder. This way, users can view the reports but not edit them. References: https://help.salesforce.com/s/articleView?id=sf.reports_folders.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_dashboard_folder_access.htm &type=5

To test the impact of a critical update before it is auto-activated, you should activate it in a sandbox first. This way, you can verify that your customizations and integrations work as expected without affecting your production org.

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

A roll-up summary field is a type of field that calculates values from related records, such as the count of child records or the sum of a field on child records. In this case, the administrator can add a roll-up summary field to the open house object to track the number of visitors by counting the child records on the visitors object. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.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

Data Export Wizard allows administrators to export data from Salesforce in CSV files. It can be used to export data for backup purposes or to analyze data in external tools. Data Import Wizard is used to import data into Salesforce, not export. Data Loader is a desktop tool that can also export data, but it is more complex and requires installation. Report Builder is used to create reports in Salesforce, not export data. References: https://help.salesforce.com/s/articleView?id=sf.data_export.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

To use as an identifier when importing and updating records from a separate system, an administrator should use External ID field type on an object. External ID fields allow storing unique identifiers from external systems and using them for matching records during import or update operations. External ID fields can also be used for upsert operations that insert new records or update existing ones based on external ID values. For example, an administrator can create an External ID field on Account object that stores account numbers from an external ERP system and use it for importing or updating accounts from that system. Rich Text field, Record ID, and Auto-Number field are not suitable for using as identifiers when importing and updating records from a separate system. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_field_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_loader_upsert.htm &type=5

Flow Builder supports creating a screen that can launch a simple discount calculator when a button is clicked on an opportunity.

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

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

Business hours are used to specify the days and hours when your company’s employees work. You can create multiple sets of business hours for different time zones or regions and assign them to users based on their location or function. To meet the requirement of having different business hours for reps on pacific time and eastern time, you need to create one set of business hours per time zone and assign them accordingly. References: https://help.salesforce.com/s/articleView?id=sf.customize_supporthours.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_supporthours_assign.htm &type=5

To access the account object in Salesforce, users need to have permission to the account object on their profile or permission set. Permission to an object determines what users can do with records of that object, such as create, read, edit, delete, view all, or modify all. If users do not have permission to an object, they will not be able to see or access that object in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_permissions.htm &type=5

Picklist values, help text, and decimal places are three aspects of standard fields that an administrator can customize to suit their business needs. Picklist values are the options that users can choose from a picklist field; they can be added, edited, or deleted by administrators. Help text is the text that appears when users hover over a field; it can be customized by administrators to provide additional information or guidance for users. Decimal places are the number of digits that appear after the decimal point in a number or currency field; they can be changed by administrators to adjust the precision of the field values. Field history tracking and field name are not aspects of standard fields that can be customized; they are only available for custom fields. References: https://help.salesforce.com/s/articleView?id=sf.customize_picklists.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_fields_edit.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_fields_number.htm &type=5

A master-detail relationship is a parent-child relationship in which the master object controls certain behaviors of the detail object. The master object can be a standard or custom object, but not all standard objects support being a master. Roll-up summaries are fields that calculate the sum, count, min, or max of child records. The owner field on the detail records is not available and is automatically set to the owner of the master record.

References: https://www.forcetalks.com/blog/master-detail-relationship-in-salesforce/ https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.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

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

Custom object and master detail field are two steps that should be configured to meet this requirement. Custom object can be used to create a new object for shoe design that can store information about different designs and stages. Master detail field can be used to create a relationship between Product and Shoe Design that prevents deletion of Shoe Design records and allows multiple designs for one product. References: https://help.salesforce.com/s/articleView?id=sf.customize_customobjects.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

Process Builder is a tool that can be used to automate business processes by creating record-triggered flows that execute actions when certain conditions are met. In this case, Process Builder can be used to create a flow that executes when an opportunity is closed won and creates a client welcome task and a welcome email for the primary contact. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5

An escalation rule is a tool that allows administrators to automatically escalate cases based on certain criteria and time triggers. For example, an escalation rule can change the owner of a case, send an email notification, or update a field value when a case has been open for more than 7 days. An escalation rule consists of multiple rule entries that define the criteria and actions for each escalation scenario. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation.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

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 are a way to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. They can be used to require users to follow the status values as they are on the path and prevent them from reverting the case back to a previous status by using formulas that compare the old and new values of the status field. Global value picklists are a way to create and maintain picklist values that can be shared across multiple fields, but they do not enforce any logic or order on the values. Predefined field values are a way to set default values for fields on path settings, but they do not prevent users from changing them later. Dependent picklists are a way to filter the values of one picklist based on the value of another picklist, but they do not prevent users from going back to a previous value. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

Two reasons that would prevent a user from being deactivated are that the user is part of a territory hierarchy or that the user is assigned in workflow email alert. A territory hierarchy is a structure that defines how territories are related to each other in Salesforce; if a user is part of a territory hierarchy, they cannot be deactivated until they are removed from all territories. A workflow email alert is an action that sends an email to one or more recipients when a workflow rule is triggered; if a user is assigned in workflow email alert, they cannot be deactivated until they are removed from all email alerts. The user being in a custom hierarchy field or being the highest role in role hierarchy are not reasons that would prevent deactivation; they may affect data visibility or record ownership after deactivation, but they do not block deactivation itself. References: https://help.salesforce.com/s/articleView?id=sf.users_deactivate_considerations.htm &type=5

One possible reason why a manager receives an error when trying to approve a record is that the user in the next approver step is inactive or missing, which means there is no valid user to assign the record to after approval. To troubleshoot this issue, an administrator should check if the user in the next approver step is active and exists in Salesforce; if not, they should activate or create the user or change the approval process to assign the record to another user. Adding a delegated approver for the next approver in the process does not solve this issue because delegated approvers are only used when approvers are unavailable; they do not replace approvers who are inactive or missing. Updating the field level security to view on fields that are updated in the process does not solve this issue because field level security does not affect approval processes; it only affects what fields users can see or edit on page layouts. Reviewing the page layout to ensure fields updated in the process are visible does not solve this issue because page layouts do not affect approval processes; they only affect what fields users can see or edit on page layouts. References: https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5

Splits is a feature that should be used to meet this requirement. Splits allows users to assign credit to opportunity team members based on the level of effort contributed by each person toward each deal. Users can create different types of splits, such as revenue or overlay splits, and specify the percentage or amount of credit for each team member. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_splits_overview.htm &type=5

Escalation rules allow you to escalate cases based on certain criteria, such as time or priority. You can use escalation rules to transfer unassigned cases to the appropriate service representative within a specified time frame.

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

Fault connector and screen component are two features that can be used to address the issue of users seeing error messages when they use one of their screen flows. Fault connector can be used to handle errors that occur when a flow element fails, such as a record create or update element. Screen component can be used to display a message to the user with text explaining what went wrong and how to correct it. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_connector_fault.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp_display_text.htm &type=5

Validation rules allow you to enforce data quality by preventing users from saving records that do not meet certain criteria.

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

Manual sharing allows record owners to share individual records with other users or groups. This is useful when one-off sharing is needed for a specific situation. Hierarchical sharing, criteria-based sharing and owner-based sharing are not suitable for this scenario because they are based on predefined rules or roles that do not match the requirement. References: https://help.salesforce.com/s/articleView?id=sf.sharing_overview.htm &type=5

Case escalation rules are a way to automatically escalate cases that meet certain criteria, such as being open for more than a specified time or having a certain priority. Escalation rules can assign cases to a different owner or queue and send email notifications to the support manager or other recipients. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation.htm &type=5

To create a many-to-many relationship between two existing custom objects, the administrator needs to create a junction object that has two master-detail relationships, one to each of the custom objects. This will allow each record of one object to be linked to multiple records from another object and vice versa. References: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm &type=5

Page layout and field level security are two factors that determine whether a user can see a new field on a record. To troubleshoot this issue, the administrator should ensure that the page layout for the user’s profile has been updated to include the new field and that the field level security of the field for the user profile allows read or edit access. References: https://help.salesforce.com/s/articleView?id=sf.customize_layoutoverview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_fls.htm &type=5

An ID variable is a type of variable that can store an ID value of a record or a record type in a flow. It can be used to store the ID of a record type for later use in a flow, such as assigning it to a record or using it in a condition. A boolean variable is a type of variable that can store a true or false value in a flow. A text variable is a type of variable that can store a text value in a flow. A record variable is a type of variable that can store one or more field values of a record in a flow. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_variables.htm &type=5

Outbound message allows you to send information to an external system as part of a workflow rule or approval process. You can use outbound message to specify which fields to send and which endpoint URL to send them to.

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

The Assignment Rule checkbox is a checkbox that appears on manual case creation pages when assignment rules are defined for cases. The Assignment Rule checkbox determines whether or not to apply assignment rules to manually created cases. If the Assignment Rule checkbox is selected by default, then any manually created cases will be assigned according to assignment rules instead of being owned by the agent creating them. To prevent this from happening, an administrator can either deselect the Assignment Rule checkbox when creating cases manually; or change the default setting for this checkbox under setup by selecting or deselecting Use active assignment rules by default. References: https://help.salesforce.com/s/articleView?id=sf.customize_casesupport_assign.htm &type=5

A lookup field is a type of field that allows administrators to create a relationship between two objects by linking records from one object to another object. For example, a lookup field can link an account record to a purchase record by storing the account ID on the purchase record. A lookup field allows users to select an existing record from a pop-up window or create a new record from the same window. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5

To display the screen flow, the administrator should create a tab and add the screen flow to the page. The administrator can also use a flow element and add the screen flow to the record page.

The other options are not relevant to this scenario. Adding the flow in the utility bar of the console will not display the screen flow. Installing an app from the AppExchange is not necessary to display the screen flow.

Here are the steps on how to create a tab and add the screen flow to the page:

• Go to Setup > Tabs.
• Click New.
• Enter a name and label for the tab.
• Select the Screen Flow tab type.
• Select the screen flow that you want to display.
• Click Save.

Here are the steps on how to use a flow element and add the screen flow to the record page:

• Go to Setup > Customize > Lightning App Builder.
• Select the record page that you want to add the screen flow to.
• Click Edit.
• Drag the Flow element from the Palette to the canvas.
• Select the screen flow that you want to display.
• Click Save.

A validation rule is a feature that allows administrators to define criteria for data entry or import operations and display an error message when those criteria are not met. For example, a validation rule can require users to select a product type or check a needs review box when saving an opportunity by using an OR function that evaluates both fields. If neither field is populated, then the validation rule will prevent users from saving records with an error message. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

To update the shipping address on selected orders associated with an account when the shipping address is changed on the account, the administrator should create a screen flow on the account page that lets the reps choose which orders they want to update with the new address. This will give them more control and flexibility over which orders are affected by the change. An autolaunched flow on either object will not allow reps to select specific orders, and may cause unwanted updates or errors. A screen flow on the order page will not be able to update multiple orders at once. References: https://help.salesforce.com/s/articleView?id=sf.flow_build_screen.htm &type=5

To debug a screen flow that creates contacts, one of the possible causes for a variable missing on the debug screen is that the available for input checkbox was unchecked for that variable. This means that variable cannot be set by external sources such as debug inputs or URL parameters. To fix this issue, check this checkbox for any variable that needs to be set externally. The flow version or field type does not affect variable availability for input. The available for output checkbox only affects whether variables can be passed out of flows or subflows. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_variables.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_debugging.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

Component visibility allows you to restrict the visibility of a related list based on a permission set.

References: https://help.salesforce.com/s/articleView?id=sf.dynamic_forms_component_visibility.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

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. References: 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

A permission set group is a collection of permission sets that can be assigned to users as one unit; it simplifies permission management by reducing the number of permission assignments needed for users who require multiple permission sets. A permission set is a collection of settings and permissions that give users access to various tools and functions in Salesforce; it can be used to extend users’ access beyond their profile without changing their profile. Creating permission sets and assigning permission set groups can help Cloud Kicks give access to new custom object with custom fields to more than one user by creating permission sets that include access to new custom object with custom fields and assigning permission set groups that contain those permission sets to users who need them. Adding users to manual sharing list or editing organization-wide defaults are not options for giving access to new custom object with custom fields to more than one user; they either do not apply to custom objects or do not grant object-level access. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.perm_set_groups_overview.htm &type=5