ADM-201 Exam Dumps - Salesforce Certified Administrator (SU24)

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

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

A dependent picklist and a custom picklist are the two features that can be used to fulfill the requirement. A global picklist and a multi-select picklist are not features that can be used to fulfill the requirement.

Here is a more detailed explanation of why A and B are the correct answers:

• A. Dependent Picklist

A dependent picklist is a picklist whose values are dependent on the value selected in another picklist. This is useful for ensuring that only valid values are selected for a field. In this case, the administrator can create a dependent picklist for the category field on accounts and cases, with the values for the picklist being dependent on the record type selected. This will ensure that only the relevant picklist values are available for selection based on the record type selected.

For example, the administrator could create a dependent picklist for the category field on accounts and cases with the following values:

• Record Type: New Account
• Picklist Values: Residential, Commercial
• Record Type: Existing Account
• Picklist Values: Renewal, Upsell, Cross-sell

This would ensure that only the relevant picklist values are available for selection when creating a new account or an existing account.

• B. Custom Picklist

A custom picklist is a picklist that is created by the administrator. This is useful for creating picklists with values that are specific to the organization's needs. In this case, the administrator can create a custom picklist for the category field on accounts and cases, with the values for the picklist being specific to the organization's needs. This will ensure that the picklist values are relevant to the organization and its customers.

For example, the administrator could create a custom picklist for the category field on accounts and cases with the following values:

• Picklist Values: Residential, Commercial, Land, Multi-Family

This would ensure that the picklist values are relevant to the organization and its customers.

Flow Builder is a tool that can be used to create an automated way to delete records based on field values. Flow Builder can create flows that define the logic and actions for deleting records, such as finding records that match certain criteria and deleting them in bulk. Flows can be scheduled to run at regular intervals or triggered by other events or processes. References: https://help.salesforce.com/s/articleView?id=sf.flow_builder.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_concepts_delete.htm &type=5

When users log in to Salesforce via the user interface, the system checks for authentication based on their profile settings and permissions. One of the settings is login hours, which specify the time range when users can log in to Salesforce based on their profile. Another setting is Two-Factor Authentication for User Interface Logins permission, which requires users to enter a verification code along with their username and password when they log in to Salesforce via the user interface. References: https://help.salesforce.com/s/articleView?id=sf.users_profiles_loginhours.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.security_2fa_perm_ui_logins.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

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 automate an outbound message, the administrator should use a workflow rule that defines the criteria for sending the message and the actions to perform when those criteria are met. One of the actions available for workflow rules is sending an outbound message to a designated endpoint URL with specified fields as parameters. Process builder, task assignment, and flow builder are not able to send outbound messages directly. References: https://help.salesforce.com/s/articleView?id=sf.workflow_define.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_action_outboundmessaging.htm &type=5