A company wants to use Einstein Article Recommendations to surface relevant knowledge articles to its support agents. What two data components are required to set up this feature?
Article views show which articles were read; Cases provide context for recommendations.
Why this answer
Einstein Article Recommendations uses historical Knowledge Article View event data to understand which articles agents have found useful in the past, and Case records to provide context about the current issue. By analyzing patterns between case attributes and article views, the AI can predict and surface the most relevant articles for a given case. Without both data components, the recommendation engine cannot learn the association between case details and article usefulness.
Exam trap
Salesforce often tests the distinction between optional enhancement data (like ratings or categories) and the mandatory data sources (view events and case records) required to train the recommendation model.
How to eliminate wrong answers
Option A is wrong because Email-to-case logs are used for email-to-case routing and parsing, not for training article recommendations, and Knowledge Article feedback is a secondary signal, not a required data component. Option C is wrong because Knowledge Article categories and Case priority are metadata fields that can influence recommendations but are not the two required data components; the feature specifically needs view event data and case records. Option D is wrong because Community user activity is unrelated to agent-facing article recommendations, and Knowledge Article ratings are optional feedback, not a core requirement.