The Salesforce Certified Administrator (SU24) (Salesforce-Certified-Administrator)

To create a contact and an opportunity from a lead that is associated with a campaign, and keep the campaign member history, the administrator should convert the l ead from the campaign member detail page. This will automatically create a contact, an account, and an opportunity that are linked to the campaign. Deleting, cloning, or adding a contact will not preserve the campaign member history. References: https://help.salesforce.com/s/articleView?id=sf.campaigns_leads. htm & type=5

Two data loss considerations when changing a custom field type from Text to Picklist are:

Assignment and escalation rules may be affected, because the values in the picklist may not match the values that were previously entered in the text field, and the rules may not trigger as expected.

Any list view based on the custom field is deleted, because the filter criteria for the list view may not be valid for the new field type, and the list view cannot be displayed. There will be no data loss with use of a global value set or auto updates to Visualforce references, because these are not related to changing a custom field type from Text to Picklist. References: https://help.salesforce.com/s/articleView?id=sf.fields_changing_type_considerations.htm & type=5

Campaign influence is a feature that allows users to track how campaigns have influenced opportunities and measure the return on investment (ROI) of marketing efforts. Users can see which cam paigns have influenced an opportunity on the related list and assign different attribution models to calculate the campaign influence. References: https://help. salesforce.com/s/articleView?id=sf.campaigns_influence.htm & type=5

To free up user licenses for new users, the administrator should deactivate the former employees user record. This will prevent them from log ging in and using Salesforce resources, but preserve their historical activities and data. Deleting or freezing user records will not release user licenses. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgmt_licensing.htm & type=5

Auto-response rules are used to automatically send email responses to lead or case submissions based on the criteria you define. You can create one auto-response rule per object (lead or case) and c onfigure multiple rule entries with different criteria and actions within that rule. To meet the requirement of sending different email notifications based on case priority, you need to create one auto-response rule for cases and configure three rule entri es with filters for low-priority, medium-priority, and high-priority cases respectively. Then you need to select the appropriate email template for each rule entry action. References: https://help.salesforce.com/s/articleView?id=sf.customize_leadsautor.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.customize_casesautor.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 t he 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

Report folders are used to organize and secure reports in Salesforce. You can set different levels of access for different users or groups on each report folder. To preserve the integrity of the source reports for dashboards, you can create a new report folder with viewer access only and move the dashboard reports to that folder. This w ay, users can view the reports but not edit them. References: https://help.salesforce.com/s/articleView?id=sf.reports_folders.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.reports_dashboard_folder_access.htm & type=5

Two-factor authentication requires users to verify their identity with two pieces of information when they log in to Salesforce. One piece is their username and password, and the other is a verification code from an authenticator app or email or SMS.

References: https://help.salesforce.com/s/articleView?id=sf.identity_2fa_overview.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.identity_2fa_login_flow.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 S alesforce 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 recor ds 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 f rom an external system because it may not be available or consistent across systems. References: https://help.salesforce.com/s/articleView?id=sf.custom_fiel d_attributes.htm & type=5