A multi-national company wants to use Einstein Activity Capture to automatically log emails from Outlook to Salesforce. They have a requirement that emails to certain external domains (e.g., competitors) must never be logged. How should they configure this?
Activity Capture allows setting excluded addresses/domains to prevent emails from being logged to Salesforce.
Why this answer
Option B is correct because Einstein Activity Capture provides a native configuration to exclude specific email addresses or domains from being logged. By adding competitor domains to the 'Excluded Email Addresses' list in the Activity Capture settings, the system prevents those emails from ever being captured, ensuring compliance without post-processing workarounds.
Exam trap
The trap here is that candidates may confuse post-capture automation (like Process Builder or validation rules) with pre-capture configuration, assuming any Salesforce tool can prevent logging, when only the native exclusion list in Activity Capture settings works at the sync layer.
How to eliminate wrong answers
Option A is wrong because Process Builder runs after the email is already logged, meaning the data has been captured and stored, which violates the requirement to never log such emails; deletion is reactive and inefficient. Option C is wrong because Einstein Email Insights analyzes email content after logging, not preventing capture, and is designed for sentiment analysis, not exclusion. Option D is wrong because validation rules on the Email Message object cannot prevent the initial capture by Einstein Activity Capture, as the capture occurs before the record is created in Salesforce.