Prevent Users from Viewing Opportunities: Salesforce Certified Sales Cloud Consultant Exam

Prevent Users from Viewing Opportunities

Question

The sales director at Cloud Kicks wants to prevent users from viewing each other's Opportunities but wants them to check to see that the Account already exists prior to creating a new Account.

Which organization-wide default should the consultant recommend?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A

To prevent users from viewing each other's Opportunities while still allowing them to check if an Account already exists prior to creating a new one, the recommended organization-wide default would be Option B: Set Account to Public Read Only and Opportunity to Private.

Here's a detailed explanation:

Option A: Set Account to Public Read Only and use a criteria-based sharing rule on Opportunity. This option would make the Account records publicly readable, which is not desirable if the goal is to prevent users from viewing each other's Opportunities. Although a criteria-based sharing rule can restrict access to Opportunities based on specific criteria, it cannot completely prevent users from viewing other Opportunities.

Option B: Set Account to Public Read Only, and Opportunity to Private. This option is the most suitable for the given requirements. Setting the Account to Public Read Only ensures that users can only read the Account records but not modify them. On the other hand, setting the Opportunity to Private restricts access to the Opportunity records to only the record owners and users with higher-level access. This way, users will not be able to view each other's Opportunities but can still check if an Account already exists before creating a new one.

Option C: Set Account and Opportunity to Public Read Only. This option makes both the Account and Opportunity records publicly readable, which does not align with the requirement of preventing users from viewing each other's Opportunities.

Option D: Set Account and Opportunity to Private. This option would completely restrict access to both Account and Opportunity records, which means users would not be able to check if an Account already exists prior to creating a new one. This contradicts the requirement, so it is not the recommended option.

In summary, Option B is the most appropriate choice as it allows users to check the existence of an Account while preventing them from viewing each other's Opportunities.