ADM-201 Practice Test

Create one set of business hours per timezone.

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

Edit the Related List component in the Lightning App Builder and choose Related List as the related list type.

Use the page layout editor to include the appropriate column in the Cases related list.

To see certaininformation about one or more cases when referencing the
contact record, an administrator can use two methods: edit the Related List component in the Lightning App Builder and choose Related List as the related list type; and use the page layout editor to include the appropriate column in the Cases related list. The Related List component is a component that allows users to view and edit records related to a parent record on a record page. The Related List component has two types: Related List and EnhancedList. The Related List type shows records in a table format with columns that match the page layout of the parent record. The Enhanced List type shows records in a
compact format with fewer columns and actions. To change the type of the Related List component, an administrator can use the Lightning App Builder and select either Related List or Enhanced List from the properties panel. The page layout editor is a tool that allows administrators to control how fields, related lists, buttons, etc., are arrangedon a record detail or edit page for each object. To include appropriate columns in a related list, such as case name, case ID, customer name, case reason, case status, and case creation date for cases related to contacts, an administrator can use the page layout editor and drag and drop the desired fields from the palette to the Cases related list on the contact page layout.
References: https://help.salesforce.com/s/articleView?id=sf.lex_related_lists_component.htm&type=5htt
ps://help.salesforce.com/s/articleView?id=sf.customize_pagelayouts_overview.htm&type=5

Minimum password length.

Password complexity requirement.

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_p
olicies.htm&type=5

Use a scheduled flow

Ascheduled 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 requirementbecause 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

Check if the user in the nextapprover is inactive or missing.

One possible reason why a manager receives an error when trying to
approve a record is that the user in the next approver step is inactive or missing, which means there is no valid user to assign the record to after approval. To troubleshoot this issue, an administrator should check if the user in the next approver step is active and exists in Salesforce; if not, they should activate or create the user or change the approval process to assign the record to another user. Adding a delegated approver for the next approver in the process does not solve this issue because delegated approvers are only
used when approvers are unavailable; they do not replace approvers who are inactive or missing. Updating the field level security to view on fields that are updated in the process does not solve this issue because field level security does not affect approval processes; it only affects what fields users can see or edit on page layouts. Reviewing the page layout to ensure fields updated in the process are visible doesnot solve this issue because page layouts do not affect approval processes; they only affect what fields users can see or edit on page
layouts.
References:https://help.salesforce.com/s/articleView?id=sf.approvals_consideratio
ns.htm&type=5