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

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.

Reference: 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

Changing the field type to a Lookup Relationship will allow deleting the Relationship field without deleting the Runners records. A lookup relationship creates a loose association between two objects, where the child records do not depend on the parent records for their existence. A lookup relationship can be deleted without affecting the child records, unlike a master-detail relationship that enforces cascading deletes.

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

Creating a new quote record for each of the different product configurations and syncing the most likely to be purchased back to the opportunity will ensure that their quotes and opportunities reflect their sales. This way, sales reps can show customers different options and prices, and keep track of which one is most likely to close. Syncing a quote with an opportunity will update the opportunity amount, stage, and expected revenue fields based on the quote information.

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

Giving the account owner Read access to both the Account and the Quota objects will give access to all Item records. Since Item is a junction object between Account and Quota, users need to have at least Read access to both parent objects to see Item records. If users have access to only one parent object, they will not be able to see Item records related to the other parent object.

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

Displaying the related contacts related list and adding the direct field will allow users to distinguish between contacts and related contacts. The related contacts related list shows all contacts that are related to an account, either directly or indirectly. The direct field indicates whether a contact is directly associated with an account or not. By adding this field to the related list, users can easily see which contacts are direct and which are not.

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

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.

Reference: 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

Territory management is a feature that allows you to grant access to accounts and opportunities based on criteria such as geography, industry, product line, or customer size. A territory is a grouping of accounts and users that represents a market segment or business unit. In this case, the administrator should utilize territory management to add the operations team to the East territory, which contains all the accounts and opportunities in the East region. This way, the operations team members can access all the records in their territory regardless of who owns them or what the organization-wide default is.

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

A public group is a grouping of users, roles, roles and subordinates, or other groups that can be used to share access to records or folders. A sharing rule is a rule that grants additional access to records based on certain criteria or ownership. In this case, the administrator should create a public group for the renewals team and create a criteria based sharing rule on opportunities that grants read-only access to the group for all closed won opportunities. This way, the renewals team can see all the opportunities that are eligible for renewal while keeping the account private.

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

Tableau CRM is a product that allows you to create complex dashboards with supporting charts based on data from a variety of sources, including Salesforce data and external data sources. Tableau CRM uses an analytics platform that stores data in datasets and lets you explore and visualize data using lenses and dashboards. You can also use artificial intelligence and machine learning features to discover insights and make predictions from your data. Tableau CRM is integrated with Salesforce and can be accessed from various apps and objects.

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