ADVANCED-ADMINISTRATOR practice question 7 of 30
Cloud Kicks has Service end Soles Manager roles that need to be able to see a I Accounts. Currently, they each have their own custom profile. The organization-wide defaults are set to Private and a sharing rule share access to Accounts to the sales and service teams based on criteria. What should the administrator do to allow the service and sales Manager to sec all Accounts?
Full set: 222 questionsThe most appropriate and scalable solution is to use a permission set. A permission set containing the "View All" object permission for Accounts will override the organization-wide default (OWD) and any other sharing settings for the users to whom it is assigned. This allows the administrator to grant access to all Accounts specifically to the Service and Sales Managers without altering their base profiles or affecting the security for any other users in the organization. This method adheres to the principle of least privilege and is a Salesforce best practice for assigning special permissions to a subset of users.
A. While functional, modifying multiple custom profiles is less efficient and scalable than using a single permission set. Best practice is to use profiles for baseline permissions and permission sets for exceptions.
B. Setting the OWD to Public Read Only would grant all users access to all Accounts, which is not the requirement and violates the principle of least privilege.
D. The role hierarchy grants vertical access to records owned by or shared with subordinates. It does not guarantee access to all records across the organization, such as those in different hierarchy branches.
1. Salesforce Help Documentation, "Permission Sets": "A permission set is a collection of settings and permissions that gives users access to various tools and functions. Permission sets extend users’ functional access without changing their profiles... Use permission sets to grant additional permissions and access settings to users." This supports using a permission set to grant extended access beyond a user's profile.
2. Salesforce Help Documentation, "Object Permissions": In the table for Standard Object Permissions, the "View All" permission is defined as: "User can view all records associated with this object, regardless of sharing settings." This confirms that "View All" is the specific permission required to bypass the Private OWD.
3. Trailhead, "Data Security" Module, "Control Access to Objects" Unit: "The best practice is to use profiles to grant the minimum permissions and settings that all users of a particular type need, then use permission sets to grant more permissions as needed." This directly endorses the use of a permission set (Option C) over modifying profiles (Option A).
4. Salesforce Security Guide, Section: "A Look at the Salesforce Sharing Model": This guide illustrates that object permissions (controlled by profiles and permission sets) are evaluated before record-level sharing rules. The "View All" and "Modify All" permissions specifically bypass the record-level sharing architecture (OWD, Role Hierarchy, Sharing Rules).
Keep practicing
Take the free ADVANCED-ADMINISTRATOR practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other ADVANCED-ADMINISTRATOR practice questions
- Question 1An administrator is using the Dev Console Log Inspector to troubleshoot a Process Builder…
- Question 2The sales agents at DreamHouse Realty have a profile that allows them to import records f…
- Question 3An administrator needs to Import a large amount of historical data (more than 100,000 rec…
- Question 4Administrator has been tasked with creating a new custom field on the Account object call…
- Question 5Cloud Kicks (CK) wants the forecast numbers to be shown by territory regardless of who ow…
- Question 6The administrator at Cloud Kicks created a flow in a sandbox that walks service agents th…
