In the Einstein Trust Layer, the Salesforce Agentforce Specialist can configure privacy data entities to be masked (Option C). This ensures sensitive or personally identifiable information (PII) is obfuscated when processed by AI models.
Data Masking Configuration:
The Agentforce Specialist defines which fields or data types (e.g., email, phone number, Social Security Number) should be masked. For example, masking the Email field in a prompt response to protect user privacy.
This is done through declarative settings in Salesforce, where entities (standard or custom fields) are flagged for masking.
Why Other Options Are Incorrect:
A. Profiles exempt from masking: Exemptions are typically managed via permissions (e.g., field-level security), not directly within Einstein Trust Layer’s Data Masking settings.
B. Encryption keys for masking: Encryption is separate from masking. Masking involves obfuscation (e.g., replacing "john@example.com" with "@"), not encryption, which uses keys to secure data.
Einstein Trust Layer Documentation: States that Data Masking allows admins to "define which fields should be masked to protect sensitive data."
Trailhead Module: "Einstein Trust Layer Basics" explains configuring privacy entities for masking.
Salesforce Help Article: "Secure AI with Einstein Trust Layer" details masking configurations for privacy compliance.
