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 proces s, 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/arti cleView?id=sf.customize_salesprocess.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 likel ihood 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 th e 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. Refe rences: https://help.salesforce.com/s/articleView?id=sf.forecasts3_big_deal.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 w ay, 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

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

Permission sets are a flexible way to grant additional access to users without changing their profiles. To provide access to the lead object for a team of support users, create a permission set that includes the appropriate object and f ield permissions for leads, and then assign it to the users. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.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 c onfigure 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 entri es 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

To display only the proper lead sources based on the product category chosen, an admin istrator should create a dependency between the Product Category field and Lead Source field on Lead object. A dependency is a relationship between two picklist fields that restricts the values available in one picklist based on the value selected in anoth er picklist. For example, an administrator can create a dependency that shows only Online Store and Social Media as lead sources if Product Category is Shoes, but shows only Trade Show and Magazine as lead sources if Product Category is Apparel. Creating a page layout for each category, creating business processes and record types for each category, or creating a single business process with record types for each category will not display only the proper lead sources based on the product category chosen. Re ferences: https://help.salesforce.com/s/articleView?id=sf.customize_dependent.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

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_se lling.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 see certain information about one or more cases when referencing the contact r ecord, an administrator can use two methods: edit the Related List component in the Lightning App Builder and choose Related List as the related list type; and use the page layout editor to include the appropriate column in the Cases related list. The Rela ted List component is a component that allows users to view and edit records related to a parent record on a record page. The Related List component has two types: Related List and Enhanced List. The Related List type shows records in a table format with c olumns that match the page layout of the parent record. The Enhanced List type shows records in a compact format with fewer columns and actions. To change the type of the Related List component, an administrator can use the Lightning App Builder and select either Related List or Enhanced List from the properties panel. The page layout editor is a tool that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. To include appro priate columns in a related list, such as case name, case ID, customer name, case reason, case status, and case creation date for cases related to contacts, an administrator can use the page layout editor and drag and drop the desired fields from the palet te to the Cases related list on the contact page layout. References: https://help.salesforce.com/s/articleView?id=sf.lex_related_lists_component.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm & type=5