Sharing rules are automatic exceptions to organization-wide sharing settings that grant additional

access to records based on record ownership or criteria. By creating a sharing rule on the Account

object for all members of the account services role to have Read/Write access, the administrator can

allow users in that role to edit and change ownership of Accounts owned by any of their team

members, regardless of the organization-wide sharing setting for Account. Reference:

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

Two options that the administrator should use to meet these criteria are:

Share with roles and subordinates of the finance director role. This option allows you to grant access

to records based on the role hierarchy of your org. You can share records with users who are in a

specific role or in roles below that role in the hierarchy. In this case, you can share records with roles

and subordinates of the finance director role, which includes all the members of the finance team.

Create a criteria-based sharing rule where the won field = true. This option allows you to grant access

to records based on certain field values or formulas. You can create a criteria-based sharing rule on

opportunities that grants access to records where the won field is true, which means that the

opportunity stage is closed won.

The other two options are incorrect because:

Make an owner-based sharing rule where the won field = true is not an option because owner-based

sharing rules do not allow you to specify field values or formulas as criteria. Owner-based sharing

rules only allow you to share records based on who owns them or what role or group they belong to.

Select all opportunities owned by the sales manager role is not an option because it does not meet

the criteria of sharing all closed won opportunities. It only shares opportunities that are owned by

users who are in the sales manager role, regardless of their stage.

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

The data masking tool is a tool that allows you to mask sensitive data in your full sandbox by

replacing it with fictitious data. This can help you protect your data privacy and comply with

regulations while testing in a realistic environment. You can use the data masking tool to mask data

for standard and custom objects, including person accounts, and choose from different masking

formats and options. Reference:

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

A rich text component allows administrators to add custom text or images to a Lightning page.

Conditional visibility allows administrators to control when a component is visible based on criteria

such as field values or device type. By using these features, administrators can highlight Canadian

customers as a potential challenge for fulfillment without modifying the page layout or creating a

new record type. Reference:

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

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

The user profile permissions on the Opportunity object is the item that the administrator should

review to find out why the user is unable to delete the duplicate record. The user profile permissions

determine what users can do with records and objects in Salesforce, such as creating, editing,

deleting, viewing, or sharing. In this case, the administrator should check if the user has the Delete

permission on the Opportunity object, which allows them to delete opportunity records that they

own or have access to. If not, the administrator can either grant them this permission or delete the

record for them. Reference:

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

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

The Analyze feature in the Lightning App Builder toolbar is a tool that helps you optimize the

performance of your record pages by providing recommendations and insights on how to improve

page load time and user experience. It can help you identify which fields and components are taking

the most time to load and suggest ways to reduce their impact. You can also compare your page

performance with other pages in your org or with Salesforce best practices. Reference:

https://help.salesforce.com/s/articleView?id=sf.lightning_page_optimize.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

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

To restore the deleted Review records, you need to restore both the Account and Product master

records from the Recycle Bin. A master-detail relationship is a type of relationship that links two

objects together and enforces a parent-child relationship between them. A master-detail relationship

affects the security and deletion of the child records. If you delete a master record, all of its detail

and subdetail records are deleted as well and moved to the Recycle Bin. To restore a detail or

subdetail record, you must first restore its parent record. Reference:

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

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