Salesforce Salesforce-Certified-Administrator Salesforce Certified Administrator (SU24) Exam Practice Test

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: &type=5

To use as an identifier when importing and updating records from a separate system, an administrator should use External ID field type on an object. External ID fields allow storing unique identifiers from external systems and using them for matching records during import or update operations. External ID fields can also be used for upsert operations that insert new records or update existing ones based on external ID values. For example, an administrator can create an External ID field on Account object that stores account numbers from an external ERP system and use it for importing or updating accounts from that system. Rich Text field, Record ID, and Auto-Number field are not suitable for using as identifiers when importing and updating records from a separate system. References: &type=5 &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: &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: &type=5 &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: &type=5 &type=5

Lightning record page is a type of page that should be created to meet this requirement. Lightning record page allows an administrator to customize the layout and components for a specific object record page in Lightning Experience or the Salesforce mobile app. To create tabs for account details, related lists, and chatter feeds, use the Tabs component in the Lightning App Builder and drag the desired components to each tab. References: id=sf.app_builder_record_page.htm&type=5 &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: &type=5

A restricted picklist is a type of picklist that enforces the integrity of the picklist values by allowing only values defined in the picklist during data entry or import operations. If the restricted picklist checkbox is checked for a picklist field, then any records with values not defined in the picklist will cause errors during import operations. However, if the restricted picklist checkbox is unchecked for a picklist field, then any records with values not defined in the picklist will be imported without errors. References: &type=5

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: &type=5

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

Case escalation rules are a feature that can be used to meet this requirement. Case escalation rules can automatically escalate cases that meet certain criteria, such as being open for more than a specified time or having a certain priority. Escalation rules can assign cases to a different owner or queue and send email notifications to the support manager or other recipients. References: &type=5

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

References: &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: &type=5

To provide appropriate access to a report that contains shoe records for all of the sales reps on their team, the administrator should configure three items:

• A custom report type that includes the shoe object and its fields
• A folder access that grants access to the sales manager and their team members to view and run reports in that folder
• A field level security that allows the sales manager and their team members to see all the fields on the shoe object Report subscription, while useful for scheduling and delivering reports, does not affect access to the report itself. References: https://help.salesforce.com/s/articleView?id=sf.reports_builder_create_report_type.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.reports_manage_folders.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_fls.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: &type=5

Web-to-Case and Email-to-Case are two solutions that allow customers to create cases from a web form or an email. Web-to-Case generates HTML code for a web form that you can place on your website. Email-to-Case converts incoming emails into cases.

References: &type=5 &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: &type=5

Paths allow you to display key fields and guidance for each stage of an opportunity. Kanban list views allow you to update records by dragging them between columns.

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

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

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: &type=5

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

References: &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: &type=5 &type=5 &type=5

A scheduled flow is a type of flow that runs at scheduled times on batches of records that meet certain criteria. It can be used to count the number of open cases associated with each account and update the account with this value every Friday evening by using an assignment element to loop through the accounts and cases and assign the count value to a field on the account record. Using a record trigger flow, a scheduled process builder, or a roll-up summary field are not suitable options for this requirement because they would not run at scheduled times or on batches of records; they would run every time a record is created or updated, which may not reflect the accurate count of open cases at the end of each week. References: &type=5

Prebuilt email templates are email templates that have been created and provided by Salesforce for common use cases such as sending welcome messages, confirmation emails, etc. They can be used by Cloud Kicks to have consistency when communicating with customers on cases via email channel with categories to help search for the proper message. Prebuilt email templates can be accessed from the email action in the case feed or from the email composer in Lightning Experience. They can also be filtered by category to find the most relevant template for each case. Prebuilt quick texts, prebuilt flow templates, and prebuilt auto-responses are not solutions for having consistency when communicating with customers on cases via email channel; they are used for different purposes such as inserting common phrases, creating guided processes, or sending automated replies. References: &type=5 &type=5

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

A validation rule is a feature that allows administrators to define criteria for data entry or import operations and display an error message when those criteria are not met. For example, a validation rule can ensure that house showings are scheduled within the current year by comparing the showing date field with a formula that returns the current year. If the showing date field contains a date outside of the current year, then the validation rule will prevent users from saving or importing records with an error message. References: &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: &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 field permissions for leads, and then assign it to the users. References: &type=5

To automate an outbound message, the administrator should use a workflow rule that defines the criteria for sending the message and the actions to perform when those criteria are met. One of the actions available for workflow rules is sending an outbound message to a designated endpoint URL with specified fields as parameters. Process builder, task assignment, and flow builder are not able to send outbound messages directly. References: &type=5 &type=5

To transfer data from a lead custom field to an opportunity field upon lead conversion, an administrator needs to create a custom field on the opportunity object that matches the data type and length of the lead custom field, and then map the two fields using the lead field mapping tool under setup. This will ensure that the value of the product category field on the lead is copied to the corresponding field on the opportunity when the lead is converted. References: &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: &type=5

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

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

References: &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: &type=5

Two considerations for preventing users from accessing Salesforce from outside of their network are:

• IP address restrictions are set on the profile or globally for the org, which limit login access based on IP ranges specified by an administrator
• Restrict U2F Security Keys on the user’s profile to enforce login hours, which require users to use security keys during certain hours of day Assigning single sign-on to a permission set or enforcing Login IP Ranges on Every Request will not prevent users from accessing Salesforce from outside of their network. References: https://help.salesforce.com/s/articleView?id=sf.security_networkaccess.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.security_keys_restrict.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: &type=5 &type=5

Setup audit trail is a tool that allows administrators to review recent configuration changes made in their org. It shows a list of up to 180 days of setup changes made by anyone in the org, including the date, time, user, and type of change. It can help administrators track who made what changes and when, and troubleshoot any issues caused by configuration changes. Critical updates are notifications that inform administrators of new features or enhancements that may impact their org; they do not show configuration changes made by users. Debug logs are records of database operations, system processes, and errors that occur when executing a transaction or running unit tests; they do not show configuration changes made by users either. Field history tracking is a feature that allows administrators to track changes to the values of certain fields on records; it does not show configuration changes made in setup. References: &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: &type=5

Case escalation rules allow you to escalate cases based on certain criteria, such as time or priority.

References: &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: &type=5 &type=5

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

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

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

References: &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: &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: &type=5 &type=5

To boost productivity by providing insights at the start of each day, the administrator should add three sales-specific standard Lightning components to the homepage:

• Activities, which shows tasks and events related to records that matter most to users
• Assistant, which provides personalized suggestions and reminders for key updates and actions
• Key Deals, which highlights important opportunities that need attention or are close to closing Path and Performance Chart are not standard Lightning components, but custom components that can be added to specific objects or pages. References: https://help.salesforce.com/s/articleView?id=sf.home_components.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: &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: &type=5 &type=5

A lookup relationship is a type of relationship that links two objects together, but does not affect security or deletion. It can be used to create a relationship between shipments and accounts where shipments should have a lookup to accounts; this way, shipments can show related account information on their records, but when an account is deleted, the shipments remain. Accounts should have a lookup to shipments is not a valid option because it does not match the requirement of seeing all shipment items from an account page; it would show related account information on shipment records instead. Shipments should have a master-detail to accounts or accounts should have a master-detail to shipments are not valid options either because they do not match the requirement of keeping shipments when an account is deleted; they would delete shipments along with their master account records. References: &type=5

Roll-up summary fields allow you to calculate the sum of a field from child records related to a parent record.

References: &type=5

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

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

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

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

References: &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: &type=5 &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: &type=5

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

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

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

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: &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: &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: &type=5

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