Salesforce ADM-201 - Salesforce Certified Platform Administrator (Plat-Admn-201)

To route new leads to the correct sales person based on the lead address, the administrator should use lead assignment rules that specify criteria based on lead fields such as City, State/Province, or Country, and assign leads that match those criteria to queues or users. Lead assignment rules can be triggered automatically when leads are created or manually by users. Creating a formula field, assigning with an escalation rule, or configuring a validation rule will not route leads to sales people. References: https://help.salesforce.com/s/articleView?id=sf.leads_assignment_rules.htm &type=5

The Assignment Rule checkbox is a checkbox that appears on manual case creation pages when assignment rules are defined for cases. The Assignment Rule checkbox determines whether or not to apply assignment rules to manually created cases. If the Assignment Rule checkbox is selected by default, then any manually created cases will be assigned according to assignment rules instead of being owned by the agent creating them. To prevent this from happening, an administrator can either deselect the Assignment Rule checkbox when creating cases manually; or change the default setting for this checkbox under setup by selecting or deselecting Use active assignment rules by default. References: https://help.salesforce.com/s/articleView?id=sf.customize_casesupport_assign.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

Native debug feature is a tool that can be used to identify the problem with the new flow. Native debug feature allows users to test a flow by running it with different input values and inspecting the output values at each element. Users can also see error messages and warnings that indicate where the flow failed or might fail. References: https://help.salesforce.com/s/articleView?id=sf.flow_debug.htm &type=5

A lookup field is a type of field that allows administrators to create a relationship between two objects by linking records from one object to another object. For example, a lookup field can link an account record to a purchase record by storing the account ID on the purchase record. A lookup field allows users to select an existing record from a pop-up window or create a new record from the same window. References: https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm &type=5

Process builder can be used to create a record-triggered flow that executes when an opportunity is closed as won and creates a follow-up task for the owner. Field update can be used to update a date field on the opportunity that can be referenced by a time-dependent workflow rule to create another task after 60 days. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_time_action_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

To require users to choose a specific search engine from a picklist when lead source is “Search Engine”, and hide it otherwise, the administrator should create a picklist for specific search engine on the same screen as lead source, and set conditional visibility so that it is only shown when lead source is “Search Engine”. This will make sure that users see only relevant fields based on their input. A decision element will create an extra screen that may disrupt user experience. An assignment element will not affect field visibility. A validation rule will not hide fields but only show errors when values are invalid. References: https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screen_components_picklist.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screen_components_conditional_visibility.htm &type=5

To require the Amount field during the negotiation stage for sales users but allow their managers to make changes, the administrator should configure a validation rule that checks if the user profile is not a sales manager, the stage is negotiation, and the amount is blank. This will prevent sales users from saving the record without entering an amount, but allow sales managers to do so. Making the field required for all users will not meet the requirement. Creating a formula field or assigning the administrator profile to the managers will not affect field requirement. References: https://help.salesforce.com/s/articleView?id=sf.validation_rules_overview.htm &type=5

A permission set group is a collection of permission sets that can be assigned to users as one unit; it simplifies permission management by reducing the number of permission assignments needed for users who require multiple permission sets. A permission set is a collection of settings and permissions that give users access to various tools and functions in Salesforce; it can be used to extend users’ access beyond their profile without changing their profile. Creating permission sets and assigning permission set groups can help Cloud Kicks give access to new custom object with custom fields to more than one user by creating permission sets that include access to new custom object with custom fields and assigning permission set groups that contain those permission sets to users who need them. Adding users to manual sharing list or editing organization-wide defaults are not options for giving access to new custom object with custom fields to more than one user; they either do not apply to custom objects or do not grant object-level access. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.perm_set_groups_overview.htm &type=5