Pass the Salesforce Salesforce Administrator ADM-201 Questions and answers with CertsForce

To enable users to add repeating tasks in Salesforce, the administrator needs to do two things: first, enable the creation of recurring tasks in activity settings under setup; second, add the create recurring series of tasks field on the page layouts for tasks. This will allow users to create a series of tasks that repeat based on a specified frequency and end date. References: https://help.salesforce.com/s/articleView?id=sf.tasks_repeating.htm &type=5

App page and record page are two types of pages that an administrator can build and customize using Lightning App Builder for Salesforce mobile app. App pages are pages that display information or tools that don’t belong to a specific record; they can be accessed from navigation menus or tabs in Salesforce mobile app. Record pages are pages that display information or actions related to a specific record; they can be accessed by opening any record in Salesforce mobile app. User page and dashboard page are not types of pages that can be built using Lightning App Builder for Salesforce mobile app; they are types of pages that can be built using other tools such as Profile settings or Dashboard Builder. References: https://help.salesforce.com/s/articleView?id=sf.app_builder_mobile_pages.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

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

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

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

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

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

A validation rule is a tool that allows administrators to enforce data quality and integrity by preventing users from saving records that do not meet certain criteria or conditions. For example, a validation rule can display an error message if a user enters an invalid value in a field. In this case, the administrator can create a validation rule on the account object that displays an error if the account annual revenue field is below 0 or greater than 100 billion. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

 Discount is not a standard field on the Opportunity object, so you need to create a custom field to capture the discount amount or percentage for each opportunity. To set up an approval process where opportunity discounts over 30% need to be approved by the VP of sales, and any discounts above 10% need to be approved by the user’s manager, you need to configure two separate approval processes with different entry criteria based on the discount field value and different approvers based on their roles. References: https://help.salesforce.com/s/articleView?id=sf.approvals_getting_started.htm &type=5