Preventing Incorrect Edits: CK Sales Cloud Consultant Exam Answer
Question
Cloud Kicks (CK) uses a sales model where pre-defined groups of reps work collaboratively on Accounts. Each group is also responsible for specific Accounts. CK has organization-wide default access set to Public Read/Write for Accounts. CK discovered this caused issues with data quality where reps edited Accounts outside their scope of responsibility. CK wants to allow reps to view any Account, but restrict editing to only reps who are responsible for those specific Accounts.
Which two steps should a consultant recommend to allow reps to continue to collaborate while eliminating incorrect edits? (Choose two.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.BC
To address the issue of incorrect edits by reps outside their scope of responsibility, the consultant should recommend the following two steps:
A. Change Account organization-wide defaults to Private. By changing the organization-wide default access for Accounts to Private, the consultant ensures that only the record owner and users with appropriate sharing access can view and edit the records. This restricts editing to reps who are responsible for specific Accounts, preventing unauthorized edits by other reps. With this change, reps can still collaborate and view any Account, but their ability to edit will be limited to their assigned Accounts.
B. Enable Account Teams to allow owners to grant Read/Write access. Enabling Account Teams provides a mechanism for the record owner to share the record with other users and grant them specific access levels. With Account Teams, reps can collaborate on Accounts by being added as team members. The record owner can assign Read/Write access to team members responsible for specific Accounts, while restricting access for other reps. This way, reps can view any Account but only make edits to the Accounts they are responsible for.
Explanation: A. Changing Account organization-wide defaults to Private ensures that the default access to Accounts is restricted to the record owner. This prevents unauthorized edits by reps outside their scope of responsibility. However, it doesn't address the requirement to allow reps to collaborate and view any Account.
B. Changing Account organization-wide defaults to Public/Read-Only would make all Accounts accessible to all reps, but it doesn't address the issue of incorrect edits. Reps would still be able to edit any Account, even if they are not responsible for it.
C. Enabling Account Teams provides a way for the record owner to share access with other users and control their level of access. This allows reps to collaborate on Accounts while ensuring that only the responsible reps have Read/Write access. It aligns with the requirement to restrict editing to only reps who are responsible for specific Accounts.
D. Creating an Account sharing rule to grant Read/Write access to all Accounts would not address the requirement to restrict editing to reps responsible for specific Accounts. It would grant Read/Write access to all reps, resulting in the same data quality issues experienced with the original setup.
Therefore, options A and C are the correct choices to allow reps to collaborate while eliminating incorrect edits.
