ADM-201 Salesforce Certified Platform Administrator (Plat-Admn-201) Question and Answers

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

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

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

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.

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

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

Comprehensive and Detailed Explanation From Exact Extract:

Add the Notify Contact checkbox to the Close Case page layout; when selected, Salesforce sends a case closure email.

Email-to-Case allows administrators to set up routing addresses that automatically create cases from incoming emails and assign them to queues based on predefined criteria. This way, emails from customers can generate cases automatically and be sent to the correct queue. A flow is a tool for building automated processes, but it is not designed for email routing. A custom email service is a way to process inbound emails using Apex code, but it requires coding skills and is more complex than Email-to-Case. An escalation rule is a way to escalate cases based on certain conditions, but it does not create cases from emails or assign them to queues. References: https://help.salesforce.com/s/articleView?id=sf.customize_email2case.htm &type=5

Making a field universally required is a way to ensure that the field needs to be filled on every record; it prevents users from saving a record without entering a value in that field. It can be used to ensure that the billing system field needs to be filled on every invoice record by making it universally required in the field settings. Creating a process builder to set the field, defining an approval process for the child, or requiring the field on the record type are not ways to ensure that the field needs to be filled on every record; they either do not enforce data entry or only apply to certain scenarios or users. References: https://help.salesforce.com/s/articleView?id=sf.customize_fields.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

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

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

My Domain is a feature that allows administrators to create a custom domain name for their Salesforce org that replaces their instance URL (such as na35.salesforce.com). My Domain provides benefits such as improved security; enhanced branding; faster navigation; access to Lightning components; etc. However, one of the considerations when enabling My Domain is that it changes how users log in to Salesforce - instead of using their instance URL login (such as login.salesforce.com), they have to use their My Domain login (such as mydomain.my.salesforce.com). This applies to all internal and external users who access Salesforce via web browser or mobile app. References: https://help.salesforce.com/s/articleView?id=sf.domain_name_overview.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

Compact layouts determine which fields appear in the highlights panel on record pages and in the Salesforce mobile app. To create a custom compact layout, go to the Account object manager and select Compact Layouts from the sidebar menu. Then click New and add the desired fields to the layout. References: https://help.salesforce.com/s/articleView?id=sf.compact_layouts_create.htm &type=5

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

Opportunity contact roles allow you to track ROI for contacts that are key stakeholders for opportunities. You need to customize the contact role field and add the related list to the opportunity page layout.

To show different picklist values for sales and marketing users, you can either use record types or profiles. Record types allow you to have different picklist values for different page layouts assigned to different profiles. Profiles allow you to restrict picklist values based on user permissions.

To track assigned licenses and permission sets in Salesforce instead of using a spreadsheet, an administrator should use User Report type on Report object. User Report type allows creating reports that show information about users such as their profile, role, license type, active status, login history etc. It also allows adding fields related to permission sets such as Permission Set Assignments or Permission Set License Assignments. For example, an administrator can create a User Report that shows user name, profile name, user license name, permission set assignments count etc. Login History, Lightning Usage App, or Permission Set Groups are not features that can be used to track assigned licenses and permission sets in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.reports_report_types_standard_user.htm &type=5

Profile assignment and page layout assignment are two assignments that should be used to display a new record type to users. Profile assignment determines which profiles can access a record type and which record type is the default for each profile. Page layout assignment determines which page layout is assigned to each record type and profile combination. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype_assign.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_recordtype_pagelayoutassign.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

Data Import Wizard allows you to import up to 50,000 records at a time.

To protect data with backups by using Data Export Service, two considerations that the administrator should remember when scheduling export are:

Data Backups are limited to weekly or monthly intervals depending on edition and license type

Metadata backups must be run via a separate process such as Metadata API or change sets because Data Export Service only exports data (records) Metadata backups are not limited by sandbox refresh intervals. Data Export Service should be run from production orgs unless testing purposes require otherwise. References: https://help.salesforce.com/s/articleView?id=sf.data_export.htm &type=5

The AppExchange is an online marketplace where you can find solutions to enhance your Salesforce organization. Some of the solutions you can find on the AppExchange are consultants and components. Consultants are certified professionals who can help you with your Salesforce projects, such as implementation, customization, integration, training, etc. Components are reusable building blocks that you can use to create apps or pages in Salesforce, such as charts, calendars, maps, buttons, etc. References: https://appexchange.salesforce.com/consultants https://appexchange.salesforce.com/components

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

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

Path is a feature that can be used to visually see the sales stages on an opportunity page. Path can include guidance and key fields for each stage to help users move opportunities along the sales process. Guidance can provide tips, policy information, or best practices for each stage. Key fields can display important fields that users need to fill in or update for each stage. References: https://help.salesforce.com/s/articleView?id=sf.path_overview.htm &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: https://help.salesforce.com/s/articleView?id=sf.picklist_limitations.htm &type=5

Comprehensive and Detailed Explanation From Exact Extract:

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

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

Muting permission sets allow you to remove permissions that are granted by a permission set group.

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

The contact hierarchy is a feature that allows users to view contacts related to an account in a hierarchical tree structure based on their role or position within the account. The contact hierarchy respects record-level access by user, meaning that users can see only those contacts that they have access to based on their profile permissions and sharing settings. The other options are incorrect because contact hierarchy is not limited to 3,000 contacts at one time (it can display up to 5,000 contacts), customizing hierarchy columns does not change the recently viewed contacts list view (it only affects how contacts are displayed in the hierarchy), and sharing settings are not ignored by contacts displayed in the contact hierarchy (they determine which contacts are visible to users). References: https://help.salesforce.com/s/articleView?id=sf.contacts_hierarchy.htm &type=5

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

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

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/

Comprehensive and Detailed Explanation From Exact Extract:

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

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

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

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

The Knowledge Lightning component is a component that allows users to access articles from the Service Cloud Console app. However, if users want to access articles from a different app that does not use the console, they can use the Knowledge related list instead. The Knowledge related list shows articles related to a record based on data categories and shows article details such as title, summary, rating, and view count. To add the Knowledge related list to a record page, an administrator can use the page layout editor and drag and drop the Knowledge related list to the appropriate section on the page layout. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_lightning_component.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_related_list.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

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

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.

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

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

To customize the campaign member status picklist values themselves, marketing users need two things: a marketing user feature license and edit permission for campaigns. A marketing user feature license enables users to create, edit, and delete campaigns; manage campaign members; and update campaign history via the import wizards or API. Edit permission for campaigns allows users to modify existing campaigns and their related records such as campaign members and campaign member statuses. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_enable.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.campaigns_member_status.htm &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: https://help.salesforce.com/s/articleView?id=sf.monitorsetup.htm &type=5

Knowledge is a feature that can be used to meet this requirement. Knowledge allows users to create, manage, and share articles that provide information and solutions for common issues or questions. Data categories can be used to organize articles into different topics and make them easier to find and access. Users can view related articles from the Case page layout based on the data category of the case. References: https://help.salesforce.com/s/articleView?id=sf.knowledge_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.knowledge_categories.htm &type=5

To help agents fill in event details and request dates for open house events without double-booking them, the administrator should create an approval process on the Campaign object, which is used to manage marketing events in Salesforce. The approval process can define entry criteria based on campaign fields such as type or status, specify initial submission actions such as sending email alerts or updating fields, assign approvers who can review and approve event requests, and specify final approval actions such as creating tasks or updating fields. Creating a workflow rule, a sharing rule, or a campaign will not help agents request event dates or prevent double-booking. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5

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.

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

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

To 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

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.

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

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

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.

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

To help a user who has attempted to log in multiple times and has been locked out of Salesforce, the administrator should reset password on the user’s record detail page and use the unlock button on the user’s record detail page. Resetting password will generate a new temporary password and send it to the user’s email address. Using unlock will restore access for a locked-out user without changing their password or waiting for lockout period to end. Logging in as the user or resetting the password policies will not help a locked-out user log in to Salesforce. References: https://help.salesforce.com/s/articleView? id=sf.users_passwords.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.users_unlock.htm &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.

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

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.

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

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

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/componen t-library/documentation/en/lwc/lwc.create_components https://help.salesforce.com/s/articleView?id=sf.dynamic_forms_component_visibility.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

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

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