Recommended Solutions for New Account Process
Question
Cloud Kicks (CK) is Implementing Sales Cloud and expects hundreds of new Accounts will be added into Salesforce on a daily basis. CK has an automated process to assign the Account owners. If no assignment can be made for an Account, it will be assigned to a fictitious owner and a person will manually review and re-assign it at a later date. At any given time, a fictitious owner may have more than 10,000 Account records assigned to it.
Which two solutions should the consultant recommend when CK sets up the new Account process? (Choose two.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.AD
When setting up the new Account process for Cloud Kicks (CK), there are two recommended solutions to consider:
B. Keep the fictitious owner out of public groups that could be used in sharing rules. C. Place the fictitious owner in a separate role at the top of the role hierarchy.
Here's a detailed explanation of these recommendations:
B. Keep the fictitious owner out of public groups that could be used in sharing rules: By keeping the fictitious owner out of public groups that could be used in sharing rules, you ensure that the fictitious owner does not inadvertently gain access to other records or data that they should not have visibility into. Public groups are often used in sharing rules to grant access to specific records or data to a group of users. Since the fictitious owner is only meant to handle records temporarily until manual review and re-assignment, it is best to restrict their access to only the records assigned to them and not expose them to additional data.
C. Place the fictitious owner in a separate role at the top of the role hierarchy: Assigning the fictitious owner to a separate role at the top of the role hierarchy ensures that they have visibility and access to all the Account records assigned to them. Placing them at the top of the role hierarchy means that they will have access to records owned by users in lower roles. Since the fictitious owner may have a large number of Account records assigned to them (potentially more than 10,000), placing them at the top of the role hierarchy avoids any limitations or restrictions that could be imposed by having them in a lower-level role.
These two solutions work together to ensure that the fictitious owner can handle the assigned Account records efficiently and without compromising data security or unnecessarily expanding their access to other records. By keeping the fictitious owner out of public groups, you limit their visibility to only the assigned records. Placing them in a separate role at the top of the role hierarchy ensures they have the necessary access to handle a large volume of Account records efficiently.
