Salesforce-Certified-Administrator Salesforce Certified Administrator (SU24) Questions and Answers

The login history is a tool that allows administrators and users to view information about recent login attempts, such as date, time, status, source IP address, browser type, platform, application, and login type. Administrators can use this tool to identify why a user is unable to login to Salesforce by checking for any failed login attempts and their corresponding error messages or reasons. References: https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5

When an administrator deletes a custom field, Salesforce moves it to the deleted fields list for 15 days, during which time it can be undeleted or erased permanently. If the administrator undeletes the field within 15 days, most of its properties and data are restored, except for its field history data, which remains deleted and cannot be recovered. References: https://help.salesforce.com/s/articleView?id=sf.custom_field_delete.htm &type=5

To provide a summary of org’s security health, an administrator should run a Health Check that compares org’s settings against baseline settings defined by Salesforce Security Baseline Standard or industry standards such as CIS (Center for Internet Security) Benchmark Standard. Health Check generates an overall health score based on how org’s settings match with baseline settings for various security categories such as Password Policies, Network Access, Session Settings etc. Health Check also provides recommendations for improving org’s security health score by adjusting settings that do not match with baseline settings. Changing Org-Wide Default to private, turning on Event Monitoring, or downloading user login data will not provide a summary of org’s security health. References: https://help.salesforce.com/s/articleView?id=sf.security_health_check.htm &type=5

The Opportunity Stage Duration report is a standard report that shows how long opportunities spend in each stage before they are closed. It can be used to measure the average stage duration for all closed opportunities by grouping and summarizing the data by stage name and duration fields. Using process builder to capture the daily average on each opportunity is not feasible because it would require creating multiple fields and formulas on the opportunity object and updating them every day. Adding formula fields to track stages on each opportunity is also not practical because it would require creating multiple fields and formulas on the opportunity object and maintaining them every time a stage changes. Refreshing weekly reporting snapshots for closed opportunities is not necessary because the report can run on real-time data without snapshots. References: https://help.salesforce.com/s/articleView?id=sf.reports_opportunity_stage_duration_report.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

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

Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can be created on the Opportunity object to display an error message if the Stage field is Closed lost and the Loss Reason field is blank. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm &type=5

A dashboard filter is a feature that allows users to filter dashboard components by one or more field values without changing the underlying report data. For example, a dashboard filter can allow users to view cases by origin, status, or owner. A dashboard filter consists of a filter name, one or more source fields, and one or more filter values. Users can apply one or more filters to see different views of the dashboard data. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_filters.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

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

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

To capture the expiration date of warranty based on installation date and warranty length (1 year by default), the administrator should use a formula as the default value of Warranty Expiration Date field on Installation object. The formula can calculate one year from installation date using DATE function or DATEVALUE function. For example, DATE(YEAR(Installation_Date__c) + 1 , MONTH(Installation_Date__c) , DAY(Installation_Date__c)) will return one year from installation date. Creating a formula field, adding a validation rule, or including Warranty Expiration Date field on mobile page layout will not capture expiration date based on installation date and warranty length. References: https://help.salesforce.com/s/articleView?id=sf.formula_using_date_datetime.htm &type=5

To advertise on TV, radio, print, and social under one banner called New Runners and aggregate total statistics for this marketing effort, an administrator should use Parent campaign field on Campaign object. This field allows creating hierarchical relationships between campaigns by specifying one campaign as parent of another campaign. Parent campaigns roll up statistics from child campaigns such as number of leads generated, amount of revenue won etc. For example, an administrator can create four child campaigns for TV, radio, print and social ads respectively and link them to one parent campaign called New Runners using Parent campaign field. Junction object, lookup relationship, and master-detail relationship are not features related to Campaign object or hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_parent.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

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

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

Case escalation rules are used to escalate cases that have not been resolved within a certain time frame by changing the case owner, sending email notifications, or triggering workflow actions. You can use these actions to alert the appropriate users or groups when a case needs urgent attention or escalation. References: https://help.salesforce.com/s/articleView?id=sf.customize_caseesc.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

Einstein Opportunity Scoring is a feature that helps sales reps prioritize and close more deals by assigning each opportunity a score from 1 to 99 based on how likely it is to be won. The score is calculated using artificial intelligence and machine learning based on historical data and patterns from similar opportunities. Sales reps can use the score to focus on high-value opportunities and take actions to improve low-scoring ones. References: https://help.salesforce.com/s/articleView?id=sf.einstein_sales_oppty_scoring.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

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

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

A gauge component shows a single value along with its percentage of a total value within predefined ranges using colors (red-yellow-green). It is useful for showing key performance indicators (KPIs) such as total sales amount and progress towards sales goal. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_gauge_component_type.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

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

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

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

To 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

Account and contact are two records that can be created when using the lead conversion process. The lead conversion process converts a lead into an account, a contact, and optionally, an opportunity. References: https://help.salesforce.com/s/articleView?id=sf.convert_lead.htm &type=5

Component visibility filters are a way to make the record pages more dynamic and easier to use by showing or hiding components based on certain criteria. For example, users can see different components based on their profile, role, record type, or field values. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_component_visibility.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

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

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

A support process is a feature that allows administrators to define and enforce the stages that a case or work order must go through based on its record type. A support process determines which values are available for the status field for each record type. If a support process omits a certain value for the status field, such as Closed, then users will not be able to see or select that value when working with cases or work orders of that record type. References: https://help.salesforce.com/s/articleView?id=sf.customize_supporthome.htm &type=5

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

To track shoe designs by products, prevent them from being deleted, and allow multiple designs for one product across various stages, the administrator should create a custom object for shoe designs and configure a custom lookup field for shoe designs on the Product object. This will create a one-to-many relationship between products and shoe designs, and allow users to link multiple shoe designs to one product record. To prevent shoe designs from being deleted, the administrator can use validation rules or permissions. Adding a custom master-detail field for shoe designs on the Product object will create a many-to-one relationship, which is not desired. Using the standard object for designs or configuring a validation rule will not meet the requirement. References: https://help.salesforce.com/s/articleView?id=sf.customize_object_relationships_overview.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

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

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

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

Flow Builder supports creating a scheduled flow that can run at specified intervals and perform actions on a set of records that meet certain criteria.

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

Themes are a way to customize the look and feel of Salesforce by changing the colors, images, and logos that appear on Lightning Experience pages. However, there are some limitations and considerations when using themes, such as: only one theme can be active at a time, and a theme applies to the entire org; themes apply only to Lightning Experience and do not affect Salesforce Classic or the Salesforce mobile app; up to 300 custom themes can be created, modified, or cloned from the built-in themes; Chatter external users see the built-in Lightning theme only and cannot see custom themes. References: https://help.salesforce.com/s/articleView?id=sf.themes_overview.htm &type=5

Validation rule is a tool that can be used to enforce data quality and business logic by preventing users from saving records that do not meet certain criteria. In this case, a validation rule can be created on the Lead object to display an error message if the Lead Status field is marked as qualified and the Budget field is blank. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.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

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

To prevent users from selecting more than one value on a picklist field, the administrator needs to change the field type from a multi-select picklist to a regular picklist, and select the “Choose only one value” checkbox on the field definition page. This will ensure that only one value can be selected on the record page and in reports and filters. References: https://help.salesforce.com/s/articleView?id=sf.customize_picklists.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

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

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

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

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

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

To identify new leads entered by interns from existing leads, the administrator should define a record type and assign it to the interns. This will allow them to select a different record type when creating leads, and distinguish them from other leads based on record type. Setting up Web-to-Lead form will not work if the interns are entering leads manually in Salesforce. Creating a separate Lead Lightning App or updating the active Lead Assignment Rules will not affect lead identification. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5

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

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

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

Campaign influence is a feature that allows users to track how campaigns have influenced opportunities and measure the return on investment (ROI) of marketing efforts. Users can see which campaigns have influenced an opportunity on the related list and assign different attribution models to calculate the campaign influence. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_influence.htm &type=5

Campaign hierarchy is a feature that allows administrators to organize campaigns into a parent-child relationship, where the parent campaign represents a larger initiative and the child campaigns represent smaller or more specific activities within that initiative. Using campaign hierarchy can help Ursa Major Solar report on campaign ROI by month and series by creating a parent campaign for the series of networking events and creating individual child campaigns for each monthly event. The parent campaign can show the aggregated metrics and ROI for the entire series, while the child campaigns can show the metrics and ROI for each month. Adding different record types for the monthly event types, creating individual campaigns that all have the same name, or configuring campaign member statuses to record which event members attended are not solutions for reporting on campaign ROI by month and series; they either do not group campaigns into a hierarchy or do not track campaign metrics or ROI. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_hierarchy.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

Probability is a standard percentage field on the Opportunity object that indicates how likely an opportunity will close successfully. It is automatically calculated based on the opportunity stage unless you make it editable on page layouts. To allow sales reps to change the probability field value of their opportunities, you need to make the field editable on page layouts. References: https://help.salesforce.com/s/articleView?id=sf.opportunity_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_layoutedit.htm &type=5

Mass delete records and data loader are two tools that can be used by Ursa Major Solar administrator undo import records into object mistake. Mass delete records tool allows administrators delete large numbers records meet certain criteria once setup interface; it can used undo import records into object mistake selecting records imported mistake deleting them mass delete records tool setup interface Data loader tool allows administrators import export delete large numbers records using CSV files command line interface API calls; it can used undo import records into object mistake using CSV file contains IDs records imported mistake deleting them data loader tool command line interface API calls Weekly data export data import wizard are not tools undo import records into object mistake because they either export import records but not delete them. References: https://help.salesforce.com/s/articleView?id=sf.admin_massdelete.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.data_loader.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

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

Dashboards show data from source reports as visual components that provide a snapshot of key metrics and performance indicators. Dashboards need to be refreshed manually or scheduled to run on a regular basis to reflect the most recent data from the reports. The running user of a dashboard determines whose security settings are applied when the dashboard is run. If the running user is different from the viewer of the dashboard, they may see different data based on their permissions and sharing settings. References: https://trailhead.salesforce.com/en/content/learn/modules/lex_implementation_dashboards_and_reports/dashboards

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

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

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

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

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

Dynamic dashboards allow you to display data according to the security settings of the running user. If users have different access levels to data on dashboards, you can use dynamic dashboards to show them only what they are allowed to see.

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

Running the flow using it to create contacts and using debug to test the flow in Flow Builder are two key components of testing a new screen flow that creates contacts. Running the flow allows the administrator to see how the flow behaves in real time and check for any errors or unexpected results. Debugging the flow allows the administrator to simulate how the flow runs with different inputs and outputs and check for any logic or syntax errors. Setting up a flow interview or testing the flow in a sandbox are not necessary for testing a screen flow that creates contacts. References: https://help.salesforce.com/s/articleView?id=sf.flow_test.htm &type=5

Default language and currency locale are two options that an administrator should configure in the company settings to support a global team of Salesforce users. Default language determines the language that is used for labels, buttons, tabs, help text, and messages in Salesforce for all users unless they override it in their personal settings. Currency locale determines the format of currency fields and numbers in Salesforce for all users unless they override it in their personal settings or enable multiple currencies. References: https://help.salesforce.com/s/articleView?id=sf.admin_supported_languages.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_supported_currencies.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.

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