Salesforce ADM-201 Salesforce Certified Administrator (SP23) Exam Practice Test

Bucket column allows you to categorize report data into groups without creating a formula or custom field. You can create buckets for different ranges of values and assign labels to them.

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

Process Builder is an automation tool that allows you to create processes that perform actions based on criteria that you specify. You can use Process Builder to update fields on related records when a record is created or updated. To meet the requirement of updating the parent object Referral when the Referral Date field is updated on the custom object Referral Source, you need to create a process that triggers when a Referral Source record is updated, checks if the Referral Date field has changed, and updates the Referral Date field on the related Referral record. References: https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5

A related record component is a type of component that allows users to view and edit fields from a parent record on a child record page without leaving the page. For example, a related record component can allow users to update the account status from the case layout by selecting an account record from a drop-down list. A rich text component is a type of component that allows users to display formatted text on a record page using rich text editor tools such as bold font, bullet points, images, and links. For example, a rich text component can display a message in bold font when a case is saved as acriticalrecord type by using conditional visibility rules. References: https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_related_record.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_rich_text.htm &type=5

A list view is a feature that allows users to filter and display records based on certain criteria and fields. A Kanban view is a feature that allows users to view records as cards organized by columns that represent stages in a process such as opportunity stages or case statuses. Users can switch between list view and Kanban view by clicking on a toggle button on any object tab that supports Kanban view such as opportunities or cases. Users can also edit records by dragging and dropping cards from one column to another or by clicking on an inline edit icon on each card. In this case, the administrator can create a list view on the opportunity object that filters opportunities by expected close date in the next 90 days; and recommend users switch the view to Kanban to edit opportunities by drag and drop. References: https://help.salesforce.com/s/articleView?id=sf.lex_list_views.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.kanban_view.htm &type=5

Contract is a standard object that represents a contractual agreement between your company and a customer. Case is a standard object that represents a customer’s question or problem that needs to be resolved by your support team. Account is a standard object that represents an individual or an organization involved in your business, such as customers, competitors, partners, etc. These three objects are commonly used for service use cases in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.contract_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.case_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.account_fields.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

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

Dependent picklist and global picklist are two options that can be used to meet this requirement. Dependent picklist allows users to create a conditional relationship between two picklist fields, where the available values in one field depend on the value selected in another field. Global picklist allows users to create a set of picklist values that can be shared across multiple fields and objects, ensuring consistent values and reducing maintenance. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_dependent_picklists.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.picklist_global_picklists.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

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

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

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

A custom profile is a profile that can be created and customized by administrators to define what users can see and do in Salesforce based on their job function or role. It can be used by Cloud Kicks to give read, create, and edit access for objects and restrict users from deleting any records by creating and assigning a custom profile with delete access removed for each object in the object settings. Assigning the standard system administrator profile to analytical user, giving user view all access and assigning them to highest role in role hierarchy, or creating and assigning permission set that includes read, create, and edit access are not solutions for giving read, create, and edit access for objects and restricting users from deleting any records; they either give too much access or do not remove delete access. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles.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

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

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

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

Support processes allow you to define different status values for different record types on cases.

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

Two functions that an administrator should use when creating a validation rule are:

• Error condition formula, which defines when an error should occur based on record fields and values
• Error message location, which specifies where on the page layout an error message should appear when triggered by an error condition formula Formula return type and rule active date are not functions used for validation rules. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_overview.htm&type=5

A sales process is a set of stages that an opportunity goes through as it moves from creation to close. A record type is a way to offer different business processes, picklist values, and page layouts to different users based on their profiles. A page layout controls the layout and organization of detail and edit pages for a specific object and record type combination. To meet the requirement of having different fields and stages for each team, you need to create three sales processes for each market segment, three record types for each sales process, and three page layouts for each record type. References: https://help.salesforce.com/s/articleView?id=sf.customize_salesprocess.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_layout.htm &type=5

Two options that should be added to Lightning record pages to make sales reps aware when they are speaking with high-profile customers are:

• Custom Component, which can display a custom message or icon on the record page based on certain criteria such as account rating or industry. For example, an administrator can create a custom Lightning Web Component that shows a star icon on account record pages if account rating is Hot or Warm.
• Component Visibility Filter, which can control when a component is visible on a record page based on field values of that record. For example, an administrator can add a component visibility filter to an existing component such as Path or Highlights Panel that makes it visible only if account rating is Hot or Warm. Highlight Panel, Action and Recommendations, and Rich Text Area are not options that can be used to make sales reps aware when they are speaking with high-profile customers. References: https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.create_components https://help.salesforce.com/s/articleView?id=sf.dynamic_forms_component_visibility.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

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

Campaign Status is a standard picklist field on the Campaign object that indicates whether a campaign is planned, in progress, completed, or aborted. Campaign Member Status is a custom picklist field on the Campaign Member object that indicates how a person responded to a campaign, such as sent, responded, registered, attended, etc. To add a new picklist value for Campaign Status, you need to edit the field in Object Manager. To add a new picklist value for Campaign Member Status, you need to modify the field on the Campaign Member Statuses related list on the Campaign page layout. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.campaigns_member_status.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

To ensure extra steps only appear when creating open house records for condominiums, an administrator can use two methods: create two page layouts; and use business processes and record types to display appropriate picklist values. 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. An administrator can create two page layouts for open house records - one for houses and one for condominiums - and include different fields or sections for each page layout based on their requirements. A business process is a feature that allows administrators to define and enforce stages that records must go through based on their record type such as lead status or opportunity stage. 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. An administrator can create two record types for open house records - one for houses and one for condominiums - and assign different business processes and picklist values for each record type based on their requirements. References: https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.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

Permissions and tab visibility are two options that administrators can adjust to fully restrict access to records for certain users or profiles. Permissions determine what users can do with records, such as create, read, edit, delete, view all, or modify all. Tab visibility determines whether users can see a specific object tab in their app launcher or navigation bar. By setting permissions and tab visibility to none or hidden for deal records for service users or profiles, administrators can prevent them from accessing deal records via search or other methods. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_permissions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_tabs.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 enable record sharing and collaboration with groups, you need to add the groups related list to the object layouts and configure the Add Record action in the group publisher.

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

When you delete a custom field, the data in that field is stored for 20 days before it is permanently deleted. During this time, you can restore the field and its data from the Recycle Bin or use Data Loader to export the data. References: https://help.salesforce.com/s/articleView?id=sf.customize_del_field.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

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

Forecasting is a feature that allows you to predict and plan the sales cycle from pipeline to closed sales, and manage sales expectations throughout your organization. Opportunity stages are the steps that an opportunity goes through as it moves from creation to close, and they determine the probability and forecast category of the opportunity. References: https://help.salesforce.com/s/articleView?id=sf.forecasting3_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_opptystages.htm &type=5

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

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

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

A sales process is a set of stages that an opportunity goes through as it moves from creation to close. It can be customized by administrators to match different business models or product lines within an org. Creating a new sales process can help Dreamhouse Realty define a different set of stages for its new home concierge offering that is unlike anything the company has offered in the past and follows a different business model. Creating a quick action, a new approval process, or a new opportunity product are not solutions for creating a customized sales process; they are used for different purposes such as creating records, approving records, or adding products to opportunities. References: https://help.salesforce.com/s/articleView?id=sf.customize_salesprocess.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

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/

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

The $Record global variable allows you to reference the values of the active record the flow is running on.

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

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

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 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 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

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

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

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

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

Two considerations when installing a managed package in a sandbox are:

• The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.
• The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data and metadata with those from its source org. If the source org does not have the package installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. References: https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.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

Flow Solutions are pre-built flows or templates that can be installed from AppExchange and customized to meet specific business needs. For example, Flow Solutions can provide common use cases such as lead generation, document generation, payment processing, and more. In this case, the administrator can use a Flow Solution that provides a mortgage calculator and generates leads for loans. Flow Solutions are easy to install and configure, and can help save time and budget for projects. References: https://help.salesforce.com/s/articleView?id=sf.flow_solutions.htm &type=5

Account teams are groups of users who work together on an account. You can enable account teams in Setup and assign team roles and access levels for each team member. Users can set up a default account team that is automatically added to any account that they own or create. This makes it easier for teams to collaborate with the same customer without manually sharing each account. References: https://help.salesforce.com/s/articleView?id=sf.accountteam.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.accountteam_default.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

There are two possible reasons why users are unable to access a report based on a custom report type created by an administrator. One is that the custom report type is in development mode, which means that it is not deployed and available for use by other users except for administrators and users with manage custom report types permission. The other is that the report is saved in a private folder, which means that it is visible only to its owner and not shared with other users or groups. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_custom_report_types.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_builder_folders.htm &type=5

Expected revenue is calculated as Amount x Probability. If the expected revenue field displays incorrect values, it means that the probability associated with the stage is not accurate. The administrator should change the probability to reflect the actual likelihood of closing the opportunity at that stage. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_expected_revenue.htm &type=5

Flow Builder is a tool that can be used to create an automated way to delete records based on field values. Flow Builder can create flows that define the logic and actions for deleting records, such as finding records that match certain criteria and deleting them in bulk. Flows can be scheduled to run at regular intervals or triggered by other events or processes. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_delete.htm &type=5

To help sales reps prioritize and close more deals, the administrator should use Einstein Opportunity Scoring, which is a feature that assigns each opportunity a score from 1 to 99 based on how likely it is to be won. The score is calculated using historical data and machine learning models, and can help reps focus on the most promising opportunities and take actions to improve their chances of winning. Einstein Activity Capture, Einstein Search Personalization, and Einstein Lead Scoring are not related to opportunity management. References: https://help.salesforce.com/s/articleView?id=sf.einstein_sales_oppty_scoring.htm &type=5

A flow can be active or inactive depending on whether you want it to run or not. An inactive flow cannot be run by users or processes until you activate it. If a flow in production is supposed to create new records but it is not doing so, it could be because the flow is inactive and needs to be activated. References: https://help.salesforce.com/s/articleView?id=sf.flow_distribute_activate.htm &type=5

To require the Amount field during the negotiation stage for sales users but allow their managers to make changes, the administrator should configure a validation rule that checks if the user profile is not a sales manager, the stage is negotiation, and the amount is blank. This will prevent sales users from saving the record without entering an amount, but allow sales managers to do so. Making the field required for all users will not meet the requirement. Creating a formula field or assigning the administrator profile to the managers will not affect field requirement. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_overview.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

The Stage Setup Flow is a tool that allows administrators to customize stages for leads and opportunities based on best practices from Salesforce experts. The Stage Setup Flow guides administrators through a series of questions about their sales process and then creates or updates stages for leads or opportunities accordingly. The Stage Setup Flow also provides tips and resources for each stage such as key fields, guidance for success, reports and dashboards, etc. References: https://help.salesforce.com/s/articleView?id=sf.stages_setup_flow_overview.htm &type=5

To require users to follow the status values as they are on the path and prevent them from reverting back to previous status values, the administrator should use validation rules that check if the status field value is changed from one value to another value that is not allowed by business logic. For example, if status values are New > In Progress > Closed, then a validation rule can check if status is changed from Closed to In Progress or New, and show an error message if true. Predefined Field Values, Global Value Picklists, and Dependent Picklists are not able to enforce status progression or prevent status reversion. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_overview.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

Report type is a tool that can be used to pull contact fields into the custom report for Event. Report type defines the set of records and fields available to a report based on the relationships between a primary object and its related objects. To edit the custom Event report type and add fields related via lookup, go to Setup > Report Types and select the Event report type. Then click Edit Layout and drag the fields from the Contact object to the layout. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_create_report_type.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

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

To identify why a user is unable to log in to Salesforce, the administrator should review the login history for the user. The login history shows the date and time of each login attempt, the source IP address, the browser and platform used, the login type (such as username and password or single sign-on), and the status (such as success or failure). The login history can help troubleshoot common login issues such as incorrect username or password, invalid security token, IP restrictions, or login hours violations. Checking the attempted logins by running the setup audit trail, pulling the password history, or resetting the security token for the profile will not help identify why a user is unable to log in. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5

Chatter broadcast group is a type of group that should be created to meet this request. Chatter broadcast group is a group where only group owners and managers can create posts, but anyone can comment on posts. This can be useful for sharing important updates or announcements with a large audience without cluttering the feed with other posts. References: https://help.salesforce.com/s/articleView?id=sf.collab_groups_create.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

IP address restrictions allow you to prevent users from accessing Salesforce from outside of their network. You can set IP address restrictions on the profile level or globally for the org. To enforce IP restrictions for API logins, you must select Enforce Login IP Ranges on Every Request in Session Settings.

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