Salesforce Certified Advanced Administrator (CRT-211) Practice Test - Questions Answers, Page 19

The issue is that the Company field is being populated on B2C Leads, which is causing the Lead Conversion Layout to only display Business Account record types. To correct this, the administrator should use a validation rule to ensure that the Company field is blank on B2C Leads. This will prevent the Lead Conversion Layout from displaying Business Account record types and will allow the administrator to select the B2C Customer record type.

The Automated Case User is the default user for cases created via Email-to-Case. This user needs to have permissions to the new record type in order to assign it to the incoming cases. If the Automated Case User does not have the permissions, the cases will receive a different record type based on the organization-wide default settings.

Reference: https://help.salesforce.com/s/articleView?id=sf.case_email_to_case.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.case_automated_user.htm&type=5

The Show Unique Count option on the account name column will create a report showing all open opportunities and the total number of accounts represented. This option will count each account only once, even if it has multiple opportunities. The report can be grouped by account name or any other field to show more details.

Reference: https://help.salesforce.com/s/articleView?id=sf.reports_builder_unique_count.htm&type=5

Read permission is required on at least one master record to be able to see the solar panel records. Since Item is a junction object between Doc and Solar Panel, users need to have access to either Doc or Solar Panel to see Item records. If users have access to both Doc and Solar Panel, they can see all Item records related to either object.

Reference: https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm&type=5

A validation rule on the Opportunity Product object to require custom date fields based on the product family will ensure that the data is captured properly. A validation rule can check if the product family matches the service plan and if so, require the start and end date fields to be filled out. This way, AW Computing can capture the term length for each service plan sold.

Reference: https://help.salesforce.com/s/articleView?id=sf.fields_about_validation_rules.htm&type=5

Data Loader with Bulk API Enabled is a tool that can import a large amount of historical data (more than 100,000 records) from another system. Data Loader can insert, update, delete, or export Salesforce records. Bulk API is an API that allows fast and parallel processing of large batches of records.

Reference: https://help.salesforce.com/s/articleView?id=sf.data_loader.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.loader_api.htm&type=5

Configuring one app per department and activating record pages for each app will ensure that users view records in a way that makes sense for each department. An app is a collection of items that work together to serve a particular function. An app can have different record pages for different objects and profiles. By activating record pages for each app, the administrator can customize what users see based on their app context.

Reference: https://help.salesforce.com/s/articleView?id=sf.app_manager_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.app_builder_customize_lex_pages_assign.htm&type=5

Creating a master-detail relationship on the Payment with a Roll-up Summary field on the Invoice will build this functionality. A master-detail relationship creates a parent-child relationship between two objects, where the child records inherit the sharing and security settings of their parent. A Roll-up Summary field calculates values from related child records, such as count, sum, min, or max. In this case, the Roll-up Summary field on the Invoice can calculate the sum of all Payments related to it and subtract it from the Invoice amount to get the current outstanding value.

Reference: https://help.salesforce.com/s/articleView?id=sf.relationships_considerations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fields_about_roll_up_summary_fields.htm&type=5

To help with this issue, the administrator can do the following options:

Move some page components behind a tab. This will reduce the number of components that load initially and improve performance.

Remove some of the fields displayed. This will reduce the amount of data that needs to be retrieved and rendered on the page.

Reduce the number of related lists displayed. This will also reduce the amount of data that needs to be retrieved and rendered on the page.

Reference: https://help.salesforce.com/s/articleView?id=sf.lex_performance_considerations.htm&type=5