Universal Containers is realigning sales territories and needs to update ownership across its 400,000 accounts. The organization-wide default for Accounts is Private.
Which two factors should the consultant consider when updating the sales territories and Account owners? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D.BC
When updating sales territories and account owners in Salesforce, there are several factors that need to be considered. Two important factors to keep in mind are:
The update of sales territories and account owners may require recalculating the sharing settings and access permissions for the 400,000 accounts. This process can be resource-intensive and may impact system performance. Therefore, it is recommended to schedule the data update during off-peak hours when the system usage is low. This helps minimize any potential disruptions or slowdowns for users who rely on Salesforce during regular business hours. Option A, "The data update will cause sharing recalculations and should be completed during off-peak hours," addresses this consideration.
The organization-wide default for accounts is set to Private, meaning that by default, account records are only accessible to their owners and users with higher-level access permissions. When updating account ownership, it is important to ensure that the appropriate access and sharing settings are configured to align with the new sales territories.
Option B, "The organization-wide default should be set to Public before the update can be performed," suggests changing the organization-wide default to Public. This statement is incorrect because changing the organization-wide default to Public may result in unintended data exposure and compromise the security and privacy of sensitive account information. It is not necessary to change the organization-wide default to update sales territories and account owners.
Option C, "The team can defer sharing calculations to decrease the risk of lock errors during the data update," suggests deferring the sharing calculations. This approach can be helpful in reducing potential lock errors that may occur when updating a large number of account records simultaneously. By deferring the sharing calculations, the update process can be performed more smoothly and minimize any potential conflicts or errors.
Option D, "The Salesforce Platform can update up to 200 accounts at a time," provides information about the batch size limitation for updates. This means that Salesforce can process updates for a maximum of 200 accounts in a single batch. If you are updating ownership for 400,000 accounts, you will need to divide the updates into multiple batches to ensure successful processing. This ensures that the updates are performed efficiently and avoid hitting any limitations or performance issues.
In summary, when updating sales territories and account owners, it is important to consider the impact on sharing recalculations, schedule the update during off-peak hours, determine the appropriate ownership and sharing settings, defer sharing calculations to minimize errors, and manage the batch size limitations to ensure successful updates. Therefore, options A and C are the correct choices.