Salesforce Updated ADM-201 Exam Questions and Answers by malik

Minimum password length and password complexity requirement are two settings that administrators can configure to increase the security of user passwords in Salesforce. They determine how long and how complex the passwords must be to meet the security standards. Password different than username and prevent common words are not valid settings in Salesforce, although they are good practices for creating strong passwords. References: https://help.salesforce.com/s/articleView?id=sf.admin_password_policies.htm &type=5

A related record component is a type of component that allows users to view and edit fields from a parent record on a child record page without leaving the page. For example, a related record component can allow users to update the account status from the case layout by selecting an account record from a drop-down list. A rich text component is a type of component that allows users to display formatted text on a record page using rich text editor tools such as bold font, bullet points, images, and links. For example, a rich text component can display a message in bold font when a case is saved as acriticalrecord type by using conditional visibility rules. References: https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_related_record.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.lightning_page_components_rich_text.htm &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: https://help.salesforce.com/s/articleView?id=sf.accountteam.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.accountteam_default.htm &type=5

Two considerations when installing a managed package in a sandbox are:

• The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.
• The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data and metadata with those from its source org. If the source org does not have the package installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. References: https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm&type=5