You are customizing an app for a client. The app displays customer data, including an annual revenue figure column for each customer. All users need to have access to the customer records, but the…

Question

Options

• AHierarchy security
• BField-security profiles
• CSecurity roles
• DOrganization setting

• A
  7% (2)
• B
  86% (24)
• C
  4% (1)
• D
  4% (1)

Explanation

You should use field-security profiles to restrict access to a specific column. Field-security profiles provide functionality around restricting access to specified columns. You can either restrict who can view a column on a record, or who can modify the data held in the column. Field-security profiles are set up by system customizers. When you set up a profile, you need to add users to it in order to give them access to the column. You do this through the field-security profile. You should not use hierarchy security. Hierarchy security extends the standard security models to allow traversing records to user managers. It can be used alongside the existing security items such as roles, teams, and sharing. It provides more granular access to records for companies and helps with reducing the time needed for administration of security requirements. It cannot be used to control who can see or edit a specific column on a record. You should not use a security role. This controls access to the entire record rather than to a specific column on the record. You should not use an organization setting. This controls general security permissions rather than specific column permissions on records.

No community discussion yet for this question.