Sharing-and-Visibility-Architect Practice Test

Explanation: The territory with the highest territory type priority is automatically assigned to the opportunity when an account meets criteria for multiple territories4. Option A is incorrect, since creating a process builder process to update the territory field on the opportunity would be unnecessary and complex. Option C is incorrect, since creating an Apex class that implements Filter-Based Opportunity Territory Assignment would be an advanced and custom solution that is not required in this scenario. Option D is incorrect, since creating a criteria-based sharing rule on the opportunity to assign it to a territory would not work, as sharing rules do not assign territories5.

Explanation: The two actions that are required to achieve the requirement are setting up External Object to use OAuth to connect to the Accounting system and restricting access to data in the accounting system. OAuth is an authentication protocol that allows Salesforce to securely access data from an external system without storing the username and password of the external system user3. Restricting access to data in the accounting system is a way to ensure that only authorized users can view the invoice records from the external source. Creating an owner based sharing rule to grant visibility to the Invoice object and granting access to the External Object to only the Account Manager profile are not actions that can ensure that a user only accesses invoice records the user is authorized to see.

Explanation: There is an Account ownership data skew problem,which could be the reason for this problem. Data skew occurs when a large number of records (more than 10,000) are owned by a single user or belong to a single role. This can cause performance issues when accessing or updating those records, as well as when recalculating sharing rules or changing ownership. In this scenario, since each donation rep owns over 50,000 donor accounts, there is a significant data skew that affects the system performance. Option A is incorrect, since the donation reps access to the assigned accounts is not a problem by itself, but rather a consequence of data skew. Option B is incorrect, since Salesforce sharing recalculation kicked off is not a problem by itself, but rather a consequence of data skew. Option D is incorrect, sincethe Account (donor) object OWD being Private is not a problem by itself, but rather a consequence of data skew.

Explanation: By default, three roles are created when the first external user is created on a partner account. These roles are Executive, Manager, and User. They form a role hierarchy that determines the level of access to data for the partner users.

Explanation: Creating a Permission Set that grants “View All” permission for Opportunity is the best approach to meet the requirements. This will allow the Sales Reporting team to view all Opportunity records without changing their profile or OWD settings. Creating a Permission Set that grants “View All Data” permission would give them access to all data in the org, which is not necessary. Making Opportunity OWD read-only would affect all users in the org, which may not be desirable. Giving “View All Data” permission to the Sales Reporting Profile would also give them access to all data in the org, which is not necessary.