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

Auto-response rules are used to automatically send email responses to lead or case submissions based on the criteria you define. You can create one auto-response rule per object (lead or case) and configure multiple rule entries with different criteria and actions within that rule. To meet the requirement of sending different email notifications based on case priority, you need to create one auto-response rule for cases and configure three rule entries with filters for low-priority, medium-priority, and high-priority cases respectively. Then you need to select the appropriate email template for each rule entry action. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadsautor.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesautor.htm &type=5

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: https://help.salesforce.com/s/articleView?id=sf.email_templates_prebuilt.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.email_templates_use.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 make sure that all of the Salesforce users log in using the branded login URL after deploying my domain, and give them a grace period for updating their bookmarks, the administrator should set the Redirect policy to Redirect with a warning to the same page within the domain. This will redirect users who try to log in from https://login.salesforce.com or another domain to https://nto.my.salesforce.com, and show them a warning message that they need to update their bookmarks. Setting the Login policy or preventing login from https://login.salesforce.com will not redirect users or give them a warning. Filtering with Form Factor will not affect login URL. References: https://help.salesforce.com/s/articleView?id=sf.domain_mgmt_redirect.htm &type=5

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

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

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

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

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

To free up user licenses for new users, the administrator should deactivate the former employees user record. This will prevent them from logging in and using Salesforce resources, but preserve their historical activities and data. Deleting or freezing user records will not release user licenses. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgmt_licensing.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

A PriceBook is a feature that allows administrators to define different prices for the same products based on different criteria such as customer segment, region, channel, etc. For example, a PriceBook can provide reseller partners with discounted prices on the products they purchase compared to regular customers. A PriceBook consists of one or more PriceBook entries that specify the product ID, pricebook ID, list price, currency, and active status for each product-pricebook combination. References: https://help.salesforce.com/s/articleView?id=sf.pricebook_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

Contacts to multiple accounts is a feature that allows you to associate a single contact with multiple accounts, both business and person accounts. This way, you can maintain the historical accuracy of the contact record without creating duplicate records for each account. References: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts.htm &type=5

Page layout editor is a tool that allows you to customize the layout and organization of detail and edit pages for a specific object and record type combination. You can also use page layout editor to customize related lists on detail pages by adding or removing fields, changing column order, sorting records, etc. To meet the requirement of showing different fields on the Case related list from the Account record for Sales and Customer Care users, you need to use page layout editor to modify the related list properties for each page layout assigned to those users. References: https://help.salesforce.com/s/articleView?id=sf.customize_layoutrelatedlists.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

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

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

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 standard fiscal year starts on January 1 and ends on December 31. A custom fiscal year can be set to start on any month and end on any month. In this case, Cloud Kicks wants its fiscal year to start on February 1 and end on January 31. This can be achieved by setting the fiscal year to Custom and the starting month to February.

Setting the fiscal year to Standard and the starting month to February will not work, as the standard fiscal year starts on January 1. Setting the fiscal year to Custom and the duration to 4 quarters will not work, as the duration of a fiscal year is 12 months. Setting the fiscal year to Standard and the duration to 12 months will not work, as the standard fiscal year starts on January 1.

Custom fiscal years are fiscal years that follow a custom-defined structure that differs from the Gregorian calendar. They can be used by organizations that have fiscal years that start on a different month than January or have fiscal years that are divided into custom periods such as quarters or weeks. To set up a custom fiscal year that starts on February 1 and has 12 months, an administrator needs to set the fiscal year to custom and the starting month as February in the fiscal year settings. Setting the fiscal year to standard or the duration to 4 quarters does not meet the requirement of having a custom fiscal year that starts on February 1. References: https://help.salesforce.com/s/articleView?id=sf.admin_fiscal_year.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

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

Custom object and master detail field are two steps that should be configured to meet this requirement. Custom object can be used to create a new object for shoe design that can store information about different designs and stages. Master detail field can be used to create a relationship between Product and Shoe Design that prevents deletion of Shoe Design records and allows multiple designs for one product. References: https://help.salesforce.com/s/articleView?id=sf.customize_customobjects.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm &type=5

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

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

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

An escalation rule is a tool that allows administrators to automatically escalate cases based on certain criteria and time triggers. For example, an escalation rule can change the owner of a case, send an email notification, or update a field value when a case has been open for more than 7 days. An escalation rule consists of multiple rule entries that define the criteria and actions for each escalation scenario. References: https://help.salesforce.com/s/articleView?id=sf.case_escalation.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

Flow builder and approval process are two tools that can be used by Ursa Major Solar to assist users with a guided expense report process to simplify submissions, routing, and authorizations. Flow builder is a tool that allows administrators to create flows, which are guided processes that collect data and perform actions in Salesforce; it can be used to create a screen flow that guides users through the steps of submitting an expense report, such as entering expense details, uploading receipts, etc. Approval process is a tool that allows administrators to create approval processes, which are automated processes that require approval from one or more approvers; it can be used to create an approval process that routes expense reports to the appropriate managers for authorization based on certain criteria, such as amount, type, etc. Validation rule, quick action are not tools for building a guided expense report process; they are used for different purposes such as enforcing data quality or creating records. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.approvals_considerations.htm &type=5

Process Builder is a tool that can be used to implement this request. Process Builder can create record-triggered flows that execute actions when certain conditions are met. In this case, Process Builder can create a flow that executes when a contact with a title of CEO is created and updates the contact’s account record with the CEO’s name. References: https://help.salesforce.com/s/articleView?id=sf.process_overview.htm &type=5

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

A record type is a feature that allows administrators to offer different business processes, picklist values, page layouts, etc., to different users based on their profile or role. A page layout is a feature that allows administrators to control how fields, related lists, buttons, etc., are arranged on a record detail or edit page for each object. In this case, since Universal Containers has three separate lines of business with specific fields for each line; and since sales team needs different fields than service team; the administrator should create three record types for each line of business; and create two page layouts for each record type - one for sales team and one for service team. References: https://help.salesforce.com/s/articleView?id=sf.customize_recordtype.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm &type=5

Record types and sales processes allow you to have different page layouts, fields, required fields, and picklist values for different types of opportunities.

Creating a dashboard with the running user set as someone who can see all opportunities is a way to create an enterprise-wide dashboard of all open opportunities in the pipeline without changing any sharing settings. The running user determines what data is displayed on the dashboard based on their access level and permissions; if the running user can see all opportunities, then the dashboard will show all opportunities regardless of who views it. Updating the dashboard folder settings to manager for the sales reps role does not create an enterprise-wide dashboard; it only controls who can access the dashboard folder, not what data is displayed on the dashboard. Adding a filter to the dashboard to filter the opportunities by owner role does not create an enterprise-wide dashboard either; it only shows opportunities owned by users in certain roles, not all opportunities. Building individual dashboards for profiles that need to see the enterprise results is not a feasible solution; it would require creating multiple dashboards for different profiles and maintaining them separately, which is inefficient and redundant. References: https://help.salesforce.com/s/articleView?id=sf.dashboards_running_user.htm &type=5

Assignment rules and queue configuration are two options that should be used to help the support team work on some of UC’s cases. Assignment rules can be used to automatically assign cases to a queue based on certain criteria, such as case origin or priority. Queue configuration can be used to add Case as an available object to the existing queue and specify which users or groups can access the queue. References: https://help.salesforce.com/s/articleView?id=sf.case_assignment_rules.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.customize_queues.htm &type=5

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.

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

To show a component that shows LinkedIn data only to sales users when they are on their mobile phones, the administrator should filter the component visibility with two conditions:

User > Profile > name = sales User, which checks if the user’s profile name is “sales User”

Form Factor = phone, which checks if the user’s device is a phone Filtering with view or role will not achieve the desired result. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_page_visibility_rules.htm &type=5

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

Fault connector and screen component are two features that can be used to address the issue of users seeing error messages when they use one of their screen flows. Fault connector can be used to handle errors that occur when a flow element fails, such as a record create or update element. Screen component can be used to display a message to the user with text explaining what went wrong and how to correct it. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_connector_fault.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp_display_text.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.

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

Role hierarchy and sharing rules are two features that should be used to open up access to Opportunity records for sales users working on collaborative deals. Role hierarchy can be used to grant access to records owned by or shared with users who are below them in the hierarchy. Sharing rules can be used to extend sharing access to users in public groups, roles, or territories based on certain criteria, such as record owner or field value. References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules.htm &type=5

Web-to-Case allows you to create cases from a form on your website.

To make sure the custom picklist field values are populated on contact when leads are converted, you need to create a custom picklist field on contact and map it to the corresponding field on lead.

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

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

The dashboard’s running user determines the data that is displayed on the dashboard. If the running user has access to more data than the intended viewers, the dashboard will show more data than expected. To prevent this, the admin can set the running user to a specific user or a logged-in user, depending on the use case1. Alternatively, the admin can use dynamic dashboards to show data based on each viewer’s access level2.

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

A pending Chatter post is a post that has been scheduled to be published at a future date and time. However, if the user who created the pending Chatter post is deactivated before the scheduled date and time, then the pending Chatter post will be canceled and will not be published. This is because deactivated users cannot create or edit posts in Chatter. References: https://help.salesforce.com/s/articleView?id=sf.collab_scheduled_posts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.collab_deactivated_users.htm &type=5

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

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

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

Quick actions allow you to initiate expense reports from Salesforce to an external HR system. Approval processes allow you to review the expense reports by managers and directors.

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.

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

Two data loss considerations when changing a custom field type from Text to Picklist are:

Assignment and escalation rules may be affected, because the values in the picklist may not match the values that were previously entered in the text field, and the rules may not trigger as expected.

Any list view based on the custom field is deleted, because the filter criteria for the list view may not be valid for the new field type, and the list view cannot be displayed. There will be no data loss with use of a global value set or auto updates to Visualforce references, because these are not related to changing a custom field type from Text to Picklist. References: https://help.salesforce.com/s/articleView?id=sf.fields_changing_type_considerations.htm &type=5

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

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

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

A cross object formula field is a type of formula field that references fields from related objects using relationships such as lookup or master-detail. It can be used to display data from one object on another object without creating another relationship or copying data. A cross object formula field can be created on opportunity object to display data from industry field on account object using account ID lookup relationship. A custom account field, a standard account field, or a master-detail relationship field are not types of fields that can display data from industry field on account object on opportunity page layout; they either do not exist or do not reference related objects. References: https://help.salesforce.com/s/articleView?id=sf.cross_object_formulas.htm &type=5

Currency locale and default language are two of the company settings that an administrator can configure in Salesforce. Currency locale determines how currency amounts are formatted and displayed in reports and other places. Default language determines the language used for labels, buttons, tabs, and other elements in Salesforce. References: https://help.salesforce.com/s/articleView?id=sf.admin_supported_currencies.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.admin_supported_languages.htm &type=5

 Geolocation fields allow you to store the latitude and longitude coordinates of a location. They can be used to calculate distances between records and display maps of accounts, contacts, leads, or other custom objects. References: https://help.salesforce.com/s/articleView?id=sf.customize_geoloc.htm &type=5

A roll-up summary field is a type of field that calculates values from related records, such as the count of child records or the sum of a field on child records. In this case, the administrator can add a roll-up summary field to the open house object to track the number of visitors by counting the child records on the visitors object. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm &type=5

Description: The Account object in Salesforce is used to store information about individual customers or businesses that your organization interacts with. It holds essential data such as company name, contact information, industry, and related activities.

Use Case: Accounts are used to represent the organizations (or individuals) your support team is assisting. They serve as a central repository for tracking customer information and interactions.

Out of the Box Features: Includes fields like Account Name, Account Owner, Industry, Phone, and Address. It also supports relationships with Contacts, Opportunities, Cases, and other objects.

Description: The Case object is used to track and manage customer issues, complaints, requests, or inquiries. Each case represents a single customer interaction and can be used to manage the resolution process.

Use Case: Cases are fundamental to customer support operations. They help support agents keep track of customer problems, assign cases to appropriate team members, and ensure timely resolution.

Out of the Box Features: Includes fields like Case Number, Subject, Status, Priority, and Origin. It supports workflows, escalation rules, and case assignment rules.

Description: The Contract object stores information about the agreements between your company and your customers. These contracts define the terms of service, support levels, and other legal agreements.

Use Case: Contracts are useful for managing service level agreements (SLAs) and ensuring that support teams adhere to the agreed-upon terms. They can be linked to Accounts and Cases to provide context and track compliance.

Out of the Box Features: Includes fields like Contract Start Date, End Date, Contract Term, Status, and Account. It supports related lists to associate contracts with cases, assets, and other records.

Accounts:

Salesforce Account Object Documentation

Trailhead: Manage Your Customer Data

Cases:

Salesforce Case Object Documentation

Trailhead: Set Up Case Management

Contracts:

Salesforce Contract Object Documentation

Trailhead: Administer Salesforce Contracts

Account Object2. Case Object3. Contract ObjectReferences

Big Deal Alerts are notifications that are sent to users when an opportunity reaches a certain amount, probability, or stage. They can be configured by administrators to alert sales reps or managers when they have a high likelihood of winning a big deal. Key Deals are a feature of Einstein Opportunity Scoring that shows the top opportunities based on their score and stage, but they do not send notifications. Activity Timeline is a component of Lightning Experience that shows the past and upcoming activities related to a record, but it does not notify users of big deals. Performance chart is a type of report chart that shows how well users or teams are performing against their goals, but it does not alert users of big deals. References: https://help.salesforce.com/s/articleView?id=sf.forecasts3_big_deal.htm &type=5

Lightning page allows you to customize a record page and add a screen flow as a component. You can use the Lightning App Builder to drag and drop the Flow component onto the page and select the screen flow you want to display.

Before Save Flows are a type of record-triggered flow that run before a record is saved and can update fields on that record without any additional actions or DML operations. They are faster and more efficient than workflow rules or process builder for simple field updates when a record is created or updated. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_before_save_update.htm &type=5

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

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