Salesforce-Platform-Sharing-and-Visibility-Architect Practice Test
Salesforce Spring 25 Release 77 Questions
An architect has a requirement to create a criteria-based sharing rule based on the
customer Social Security Number. However, when setting up the rule in Contact Sharing,
the field is not shown on the list of available fields.
What is causing this issue?
A. The field hasbeen configured for encryption.
B. The architect's profile docs not have Field Level Security for this field.
C. The architect does not have permission to Compliance fields.
A. The field hasbeen configured for encryption.
Explanation:
Encrypted fields—whether through Classic Encryption or Shield Platform Encryption—are ineligible for use in criteria-based sharing rules. Salesforce removes them from the available list when you build the rule, because matching on an encrypted value violates security principles.
→ Field-Level Security (B) would still allow the architect to see the field when building a sharing rule, even if they can’t edit data.
→ “Compliance fields” (C) refers to a managed-package concept, not standard sharing behavior.
Since Social Security Numbers must be protected, admins often enable encryption for PII. When that happens, you can’t filter sharing by that field, so it simply isn’t listed.