Salesforce Certified Platform Sharing and Visibility Architect Practice Questions

Salesforce Certified Platform Sharing and Visibility Architect exam preparation

Salesforce Certified Platform Sharing and Visibility Architect practice questions in English: 180 questions with explanations. The mock exam has 60 questions and 120 minutes.

Salesforce Certified Platform Sharing and Visibility Architect free question 9 / 10 · Domain 4: Implications of Security Model Choice

A company parks its unassigned leads under a single catch-all user, U, and plans to keep doing so. U will own hundreds of thousands of leads. Which placement of U best limits the performance impact, according to Designing Record Access for Enterprise Scale (Winter ’23)?

  1. Give U no role, so that U sits outside the role hierarchy altogether
  2. Put U in a dedicated role that is created at the bottom of the role hierarchy
  3. Put U in the role of the department that handles the leads, so its managers can see them
  4. Add U to a public group that is the source group of a sharing rule, so that everyone is reached
Show the answer and explanation

Answer: A

Why this is correct
The page defines ownership data skew as the condition in which a single user owns more than 10,000 records of an object. If there is a compelling reason to concentrate ownership in a small number of users, the page says you can minimize the possible performance impact by not assigning those users to a role. The reason is what happens when a skewed user is moved around the hierarchy, or moved into or out of a role or group that is the source group for a sharing rule: Salesforce must adjust a very large number of entries in the sharing tables, which can lead to a long-running recalculation of access rights. A user who has no role cannot be affected by hierarchy moves of that kind.

Why the other options are wrong
"Put U in a dedicated role that is created at the bottom of the role hierarchy" … The page’s advice for a skewed user who must have a role is to place that user in a separate role at the top of the hierarchy, not at the bottom. A role of any kind still leaves the user exposed to hierarchy changes, so the page puts leaving the user without a role first.
"Put U in the role of the department that handles the leads, so its managers can see them" … A departmental role is exactly the kind of position that gets moved when departments are reorganized. The page names moving skewed users around the hierarchy as one of the two situations in which Salesforce must adjust a very large number of sharing-table entries.
"Add U to a public group that is the source group of a sharing rule, so that everyone is reached" … The page tells you to keep these users out of public groups that could be used as the source for sharing rules. Moving a skewed user into or out of a source group is the second situation the page describes as forcing a long-running recalculation.

If a role is unavoidable
If the user must have a role in order to share data, the page gives three recommendations: place the user in a separate role at the top of the hierarchy, do not move the user out of that top-level role, and keep the user out of public groups that could be used as the source for sharing rules. The page also notes that distributing ownership across a greater number of users decreases the chance of long-running updates.

Go to the Salesforce Certified Platform Sharing and Visibility Architect practice app (10 free questions; purchase unlocks all questions)

See the full practice set