Pass the Salesforce Salesforce Administrator Plat-Admn-301 Questions and answers with CertsForce

Identity verification history and login history are two areas that the administrator can review to understand potential root causes of multi-factor authentication issues. Identity verification history shows the methods and results of identity verification attempts for a user, such as email verification, SMS verification, or app verification. Login history shows the status, source, and location of login attempts for a user, as well as any login errors or challenges that occurred. These two areas can help the administrator identify if the user entered the correct verification code, if the user’s device or app is compatible with multi-factor authentication, or if there are any network or security issues that prevent successful verification. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_history.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.monitoring_login_history.htm &type=5

Two options that the administrator can use to solve this scenario are:

Create a custom object. A custom object is an object that you define to store information that is specific to your organization or industry. In this case, you can create a custom object for the form that has more than 30 fields and relates to the account or opportunity object. This way, you can store multiple submissions of the form for each account or opportunity and track their changes over time.

Turn on Field Tracking. Field tracking is a feature that allows you to monitor changes to certain fields on an object and display them in a history related list. In this case, you can turn on field tracking for the fields on the form custom object and see what values were changed from one submission to another.

A before save flow trigger is a type of flow that runs before a record is saved and can update the record without any additional actions or database operations. This can expedite the time required to update the records and improve performance. A before save flow trigger can be used as an alternative to a process builder that updates the same record that triggered it. References: https://help.salesforce.com/s/articleView?id=sf.flow_concepts_trigger.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_triggers.htm &type=5

Delegated Administration allows administrators to delegate certain user management tasks to non-administrators. For example, a delegated administrator can assign permissions sets to users in specified roles or public groups without having full access to modify permission sets. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgt_delegated.htm &type=5

Building a process that updates the record type field to B2C Customer after conversion will correct this issue. The conversion layout for person accounts does not allow selecting different record types for accounts and contacts. The default record type for person accounts is determined by the organization-wide default settings. However, a process can be triggered after conversion to update the record type field based on the lead record type or other criteria. References: https://help.salesforce.com/s/articleView?id=sf.convert_leads_considerations.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.convert_leads_mapping.htm &type=5

A validation rule is a formula that validates the data entered by a user and prevents the record from being saved if the data does not meet certain criteria. In this case, the administrator can create a validation rule to ensure that the custom encrypted field for credit card numbers has exactly 16 digits. The other options are not applicable for encrypted fields. References: https://help.salesforce.com/s/articleView?id=sf.fields_about_encrypted_fields.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm &type=5

Contacts to Multiple Accounts is a feature that allows administrators to relate a contact to multiple accounts without creating duplicate contacts for each account. This feature is useful for scenarios where a contact has business relationships with more than one account, such as consultants, brokers, or loan advisors. By setting up Contacts to Multiple Accounts for loan advisors at DreamHouse Realty, administrators can track which loan advisors work with which customers and which accounts without creating duplicate contacts for each account. References: https://help.salesforce.com/s/articleView?id=sf.contacts_multiple_accounts_overview.htm &type=5

One possible cause of unexpected changes to record values is having multiple automation tools that update the same field on the same object. This can create conflicts and overwrite each other’s values. To resolve this issue, the administrator should consolidate automation tools and use only one tool per object and field combination. This can help avoid confusion and ensure consistent results. References: https://help.salesforce.com/s/articleView?id=sf.process_which_tool.htm &type=5 https://trailhead.salesforce.com/en/content/learn/modules/business_process_automation/automation_considerations

A price book is a list of products and their prices that can be added to an opportunity. A product can have different prices for different markets or segments, and these prices are stored in different price books. In this case, the administrator should create a new price book for the new retail pricing and add the products that are sold to retail locations for resale. This way, the users can select the appropriate price book and products for their opportunities based on the type of customer they are selling to. References: https://help.salesforce.com/s/articleView?id=sf.products_pricebooks.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.products_define.htm &type=5

A summary report with a cross-filter is a type of report that allows you to summarize data by grouping rows and columns and applying filters based on related objects and fields. A cross-filter is a filter that lets you include or exclude records in your report based on related objects and their fields. In this case, you can create a summary report that includes a cross-filter to the Account object with a sub-filter for credit card number equal to null. This will show you all B2C accounts that are missing the credit card number, regardless of whether it is encrypted or not. References: https://help.salesforce.com/s/articleView?id=sf.reports_summary_charts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.reports_cross_filters.htm &type=5