ADVANCED-ADMINISTRATOR practice question 4 of 30

Administrator has been tasked with creating a new custom field on the Account object called Government Der. The compliance department has determined that this field contains sensitive Information and needs to be encrypted using Classic Encryption. How will this impact users when reading, editing, or reporting on Accounts?

Full set: 222 questions
Answer options
A: Encrypted fields are unable to be used the report criteria or list views filters. Correct answer
B: Users will need the View Encrypted Data permission to edit the field.
C: Encrypted fields can be added to a list view and rule filters.
D: Users with the View Encrypted Data permission can see the field, regardless of Field-Level Security.
Correct Answer:
A. Encrypted fields are unable to be used the report criteria or list views filters.
Explanation

Classic Encryption protects data at rest but imposes significant functional limitations. When a field is encrypted using this method, the database cannot perform operations directly on the encrypted value. Consequently, these fields cannot be used in the WHERE clause of a query. This restriction prevents their use in report criteria, list view filters, workflow rule criteria, formula fields, and validation rules. Users can still view the encrypted field as a column in reports and list views if they have the appropriate permissions, but they cannot filter records based on its value.

Why Incorrect

B. Users will need the View Encrypted Data permission to edit the field. This is incorrect. The "View Encrypted Data" permission allows a user to see the unmasked value. The ability to edit the field is controlled by object permissions and Field-Level Security (FLS).
C. Encrypted fields can be added to a list view and rule filters. This is incorrect. While encrypted fields can be added as display columns to a list view, they cannot be used in list view filters or any type of rule filter (e.g., workflow, validation).
D. Users with the View Encrypted Data permission can see the field, regardless of Field-Level Security. This is incorrect. Salesforce security is layered. A user must first have access to the field via Field-Level Security (FLS). The "View Encrypted Data" permission only determines if an accessible field's value is masked or unmasked.

References

1. Salesforce Help Documentation, "Considerations for Encrypting Custom Fields":

This document explicitly lists the limitations of Classic Encryption. Under the "Encrypted custom fields have the following limitations" section, it states: "You can’t use encrypted fields in: ... Report filters, list view filters, workflow rule criteria or formulas, formula fields, approval processes, validation rules." This directly supports the correct answer (A) and refutes option (C).

2. Salesforce Help Documentation, "Set Up Classic Encryption for Custom Fields":

Under the "Give Users Permission to View Encrypted Data" section, it details the purpose of the "View Encrypted Data" permission. It clarifies that this permission is for viewing unmasked data, while standard profile settings and permission sets control the fundamental access (read/edit) to the field itself. This refutes options (B) and (D).

3. Salesforce Trust and Compliance Documentation, "Platform Encryption":

While primarily focused on Shield Platform Encryption, this documentation often contrasts it with Classic Encryption, highlighting the latter's limitations. It reinforces that Classic Encryption prevents filtering, sorting, and use in most declarative automation, which aligns with the reasoning for answer A. (Note: Specific page numbers are not applicable to dynamic web documentation; the sections are key).

Scroll to Top