An Agentforce configured Data Masking within the Einstein Trust Layer. How should the Agentforce Specialist begin validating that the correct fields are being masked?

The correct answer is C. Enable the collection and storage of Einstein Generative AI Audit Data on the Einstein Feedback. To validate data masking behavior, you must first enable the collection and storage of Einstein Generative AI Audit Data via the Einstein Feedback settings. Only once this is turned on will Salesforce begin capturing audit records that show what data was sent to and received from

AI Features for Service (e.g., Einstein Bots, Next Best Action)

Question

Options

AUse a Flow-based resource in Prompt Builder to debug the fields' merge values using Flow
BRequest the Einstein Generative AI Audit Data from the Security section of the Setup menu.
CEnable the collection and storage of Einstein Generative AI Audit Data on the Einstein Feedback

How the community answered

(26 responses)

A
8% (2)
B
15% (4)
C
77% (20)

Explanation

To validate data masking behavior, you must first enable the collection and storage of Einstein Generative AI Audit Data via the Einstein Feedback settings. Only once this is turned on will Salesforce begin capturing audit records that show what data was sent to and received from the LLM-including which fields were masked. Without enabling storage (C), there is no audit trail to inspect. Option B describes where you retrieve already-collected audit data, but that step comes after enabling collection. Option A (Flow-based debugging in Prompt Builder) helps test merge field resolution but does not verify masking behavior at the Trust Layer level.

Topics

#Data Masking#Einstein Trust Layer#Generative AI Auditing#Security Validation

Community Discussion

No community discussion yet for this question.

Full AI-201 Practice