SHARING-AND-VISIBILITY-DESIGNER practice question 16 of 30

Universal Containers has created a custom Sales Operations profile with read and edit access to the Category field on a custom object. There is a new requirement that 3 of the 100 users assigned to the Sales Operations Profile should have read-only access to the Category field. How can the Architect support this request? Choose one

Full set: 212 questions
Answer options
A:

A. Create a permission set in the Category field to read-only and assign it to the users.

B:

B. Create a new profile without edit access to Category and assign it to the users.

Correct answer
C:

C. Create a new page layout with the Category Field set to read-only for these users.

D:

D. Create a custom permission to grant read-only access to Category and assign it to the users.

Correct Answer:
B. B. Create a new profile without edit access to Category and assign it to the users.
Explanation

The requirement is to restrict access for a small subset of users who currently share a profile. Permission sets can only grant permissions; they cannot be used to restrict permissions already granted by a user's profile. Creating a new page layout only controls the user interface visibility and editability, not the underlying Field-Level Security (FLS), leaving the data vulnerable to edits via the API. Therefore, the most secure and appropriate solution is to create a new profile with read-only FLS for the 'Category' field and assign the three users to this new, more restrictive profile.

Why Incorrect

A. Permission sets are additive. They cannot revoke or restrict permissions, such as field edit access, that are already granted by a user's base profile.
C. A page layout only controls the UI. Users with edit permission from their profile could still modify the field through other means like reports or the API.
D. Custom permissions are used to grant access to custom processes or Apex code; they do not control Field-Level Security for object fields.

References

1. Salesforce Help, Control Access to Objects, "Object Permissions". This document clarifies that profiles and permission sets grant access, and for a given permission, the most permissive setting applies. It does not provide a mechanism for restriction via permission sets.

2. Salesforce Help, Control Access to Fields, "Set Field-Level Security for a Single Field on a Permission Set or Profile". This documentation shows that both profiles and permission sets define FLS, but it reinforces the principle that permission sets add, not subtract, permissions.

3. Salesforce Architects, Salesforce Security Guide, page 21, "Profiles and Permission Sets". The guide states, "A permission set is a collection of settings and permissions that gives users access to various tools and functions... without changing their profiles." This highlights their role in extending, not restricting, access.

Scroll to Top