SHARING-AND-VISIBILITY-ARCHITECT practice question 14 of 15
A banking company uses a VIP Flag in the Contact Object that they want only Private Banking Reps to see. Which approach is recommended to meet this requirement?
Full set: 78 questionsDomain Declarative Sharing
Field-Level Security (FLS) is the most direct and appropriate mechanism for controlling user access to view or edit specific fields. By setting the FLS for the "VIP Flag" field to be visible only for the "Private Banking Rep Profile" (or an equivalent permission set), access is restricted at the data layer. This ensures that only authorized users can see the field's data, regardless of whether they are viewing it on a page layout, in a report, a list view, or through an API call. This method enforces the principle of least privilege securely and efficiently.
A. Record types are designed to control business processes, page layouts, and picklist values. They do not provide a direct security control for field visibility.
B. Page layouts only control the visibility of a field on a record's detail and edit pages. Users could still see the field's data in reports, list views, or via the API.
1. Salesforce Help, "Field-Level Security": "Field-level security settings let you restrict what fields users can view and edit based on their profiles and permission sets... Field-level security is the simplest way to control user access to a particular field." This document establishes FLS as the primary control for field visibility.
2. Salesforce Help, "Control Access to Fields": "You can control which fields users can access in profiles and permission sets. Field permissions control the visibility of fields in any part of the app, including related lists, list views, reports, and search results." This explicitly contrasts FLS with page layouts, which only control UI on record pages.
3. Salesforce Architects, "Record Access: Under the Hood": In the "Salesforce Security" section, the guide outlines the layers of data access. It clearly places Field-Level Security as the control for "Which fields can a user see on a record?", distinct from page layouts which are described as a UI-level control.
4. Salesforce Security Guide, PDF: In the chapter "Controlling Access to Your Data," this guide details the hierarchy of security controls. It specifies that "Field-level security settings control whether a user can see, edit, and delete the value for a particular field on an object... These settings override field properties set in page layouts." (See section: "Object, Field, and Record-Level Security").
Keep practicing
Take the free SHARING-AND-VISIBILITY-ARCHITECT practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other SHARING-AND-VISIBILITY-ARCHITECT practice questions
- Question 1Universal Containers (UC) would like to store an encryption key within Salesforce for use…
- Question 2Users at Universal Containers are complaining that a field has disappeared from the Accou…
- Question 3Universal Containers (UC) operates worldwide, with offices in more than 100 regions in 10…
- Question 4Universal Containers has expanded to sell virtual containers for data storage. Virtual co…
- Question 5The sales managers at Universal Containers requested their teams to define each user's ro…
- Question 6A user posts a file to the Chatter feed for a record of an object that has a Private orga…
