SALES-CLOUD-CONSULTANT practice question 16 of 25
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?
Full set: 190 questionsThe solution addresses two distinct security requirements using Organization-Wide Defaults (OWD). To prevent users from viewing each other's Opportunities, the Opportunity OWD must be set to Private. This is the most restrictive setting, ensuring only the record owner and users above them in the role hierarchy have access. To allow users to check for existing Accounts before creating new ones, the Account OWD should be set to Public Read Only. This setting allows all users to view all Account records, which helps prevent duplicate data entry, while still restricting editing rights to the record owner. This combination directly fulfills both requirements of the sales director.
A. Set Account and Opportunity to Public Read Only. This is incorrect because setting Opportunity to Public Read Only would allow all users to see each other's Opportunities, directly contradicting the primary requirement.
B. Set Account to Public Read Only and use a criteria-based sharing rule on Opportunity. This is incorrect because a sharing rule is used to grant wider access than the OWD allows. The core requirement is to restrict Opportunity access, which is achieved by setting the OWD to Private.
1. Salesforce Help, Organization-Wide Sharing Defaults: "Private: Only the record owner, and users above that role in the hierarchy, can view, edit, and report on these records... Public Read Only: All users can view and report on records but not edit them. Only the owner, and users above that role in the hierarchy, can edit these records." This documentation directly supports setting Opportunity to Private for restriction and Account to Public Read Only for visibility.
2. Salesforce Security Guide, Page 13, "Define Organization-Wide Defaults": "For the most restrictive access, set the default to Private. When the organization-wide default is Private, a user can view and edit only the records that he or she owns." This confirms that Private is the correct setting for the Opportunity object based on the requirements.
3. Trailhead, Data Security Module, "Control Access to Records" Unit: "Setting an object's organization-wide sharing default to Public Read Only gives all users read access to that object's records... Setting an object's organization-wide sharing default to Private makes it so that a user can only see the records that they own." This educational resource validates the chosen OWD settings for both Account and Opportunity.
Keep practicing
Take the free SALES-CLOUD-CONSULTANT practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other SALES-CLOUD-CONSULTANT practice questions
- Question 1Universal Containers uses Sales Territories and is working with a consultant to reassign …
- Question 2The project at Universal Containers is almost finished and now it is time to test the cha…
- Question 3A consultant for Universal Containers is preparing to migrate the company's legacy CRM to…
- Question 4Cloud Kicks wants to set up contacts and accounts, where contacts can be associated to mu…
- Question 5Universal Containers has a fiscal year that starts in February and ends in January. The S…
- Question 6Universal Containers (UC) hired a consulting company to implement Sales Cloud. This will …
