B. Permissions and tab visibility

Answer Description

The best option for restricting access to deal records entirely would be to adjust Permissions and tab visibility.

Here’s why:

Permissions: The service team likely still has access to the deal records through either object-level permissions (View All or Read permissions on the Deal object) or sharing rules. By removing or adjusting these permissions, you can prevent the team from accessing deal records entirely.

Tab visibility: If the Deal tab is visible, the users may still have access to search and find these records, even if they don't have direct access via list views. Adjusting the tab visibility can help hide it from their search.

Other options:

Record setting and search index: Adjusting record settings or search index wouldn't fully restrict access; this is more about improving search efficiency, not controlling access.

App permissions and search terms: App permissions focus on which apps users can access, not object-level record restrictions, and search terms don’t control record access.

Page layouts and field-level security: These control how data is displayed or hidden within records but don’t prevent access to the records themselves.

Therefore, adjusting Permissions and tab visibility is the correct approach to fully restrict access to deal records for the service team.

A.

Uncheck grant access using Hierarchies.

Answer Description

Grant access using Hierarchies is a setting that can be used to configure the
custom object to meet this requirement. Grant access using Hierarchies determines whether access to records of the custom object is granted through the role hierarchy. If this setting is unchecked, managers are unable to see the feedback records from their staff, unless they are given access by other means, such as sharing rules or manual sharing.
References:https://help.salesforce.com/s/articleView?id=sf.security_sharing_owd_
custom_objects.htm&type=5

C. Enable the creation of recurring tasks.

D.

Lookup field

Answer Description

A lookup field is a type of field that allows administrators to create a relationship between two objects by linking records from one object to another object. For example, a lookup field can link an account record to a purchase record by storing the account ID on the purchase record. A lookup field allows users to select an existing record from a pop-up window or create a new record from the same window.
References:https://help.salesforce.com/s/articleView?id=sf.relationships_lookup.htm&type=5

D.

Add the Salesforce Mobile and Lightning Experience action to the page layout.

Answer Description

To make a quick action available on the Salesforce mobile app, you need to add it to the Salesforce Mobile and Lightning Experience Actions section of the page layout. You can use the Page Layout Editor to drag and drop the quick action onto the section.
References: https://help.salesforce.com/s/articleView?id=sf.actions_in_lex.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.customize_page_layouts.htm&type=5

B. Object layouts should be configured to include the groups related list.
C. The Add Record action must be configured in the group publisher.

D.

Junction object

Answer Description

A junction object is a type of custom object that allows administrators to
create many-to-many relationships between two other objects. A many-to-many
relationship means that each record of one object can be related to multiple  records of another object, and vice versa. For example, a junction object can represent that a contact can be interested in multiple pieces of merchandise, and a piece of merchandise can be of interest to multiple contacts. A junction object has two master-detail relationships with the two objects it connects.
References:https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm&type=5

C.

Flow Builder

Answer Description

Flow Builder allows you tocreate an automated business process that can
update records based on certain criteria. You can use a scheduled flow to run once a week and count the number of open cases related to an account.
References: https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.flow_concepts_scheduled_start.htm&type=5